[SERVER-36236] "Unable to read the storage engine metadata file" error after upgrading Mongo binaries Created: 23/Jul/18 Updated: 04/Sep/18 Resolved: 30/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tedi Roca | Assignee: | Nick Brewer |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Initial setup - works OK -------------------------------
Attempt to upgrade Mongo binaries - it does not work ------------------------------------------------------------------------
2018-07-23T13:02:56.017+0000 E STORAGE [initandlisten] Unable to read the storage engine metadata file: FileStreamFailed: Unable to read BSON data from /mongodb/storage.bson {{ 0x2b4a9043f271 0x2b4a8faed1de 0x2b4a8fb0cecb 0x2b4a93497c05 0x2b4a8fb6c2df}}
Permissions of the storage.bson file: mongodb@c675kgrlyncs:/appserver/mongo> ls -la /mongodb/storage.bson |
| Participants: |
| Description |
|
The error appears after replacing the Mongo binaries from 3.2 with those from release 3.4 and the server is started again via a service. The server starts successfully when calling directly the binaries (without a service). |
| Comments |
| Comment by Nick Brewer [ 30/Jul/18 ] |
|
tedi That's certainly a possibility. I'm going to close this ticket for now - but feel free to report back with your findings here, and we can re-open if there's any underlying mongod issues. -Nick |
| Comment by Tedi Roca [ 30/Jul/18 ] |
|
I've tried with these binaries but it's still showing the same error. We're investigating whether the issue could be related to the encryption software that is running on these instances. |
| Comment by Nick Brewer [ 24/Jul/18 ] |
|
tedi I'm still having trouble recreating this in my duplicated environment - I suggest trying again with the 3.4 binaries available here, and including the ls -ltrha output of the updated bin directory if you run into this again. Thanks, |
| Comment by Tedi Roca [ 24/Jul/18 ] |
|
I've just uploaded the additional information to the secure portal. Thanks, Tedi |
| Comment by Nick Brewer [ 23/Jul/18 ] |
|
Thanks. I reproduced a basic version of your setup, but I wasn't able to recreate the error you're seeing upgrading from 3.2 to 3.4. A few more things I'd like to confirm:
Thanks, |
| Comment by Tedi Roca [ 23/Jul/18 ] |
|
Hi Nick, I've uploaded all the details to your secure portal. Please let me know if you need further information. Thanks, Tedi |
| Comment by Nick Brewer [ 23/Jul/18 ] |
|
Thanks for your report. I'd like to get some additional information:
Since this is a public ticket, you can upload this information to our secure portal if you'd prefer - information provided there is only available to MongoDB employees, and is automatically removed after a period of time. -Nick |