"Unable to read the storage engine metadata file" error after upgrading Mongo binaries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • Hide

      Initial setup - works OK

      -------------------------------

      • 3.2 Mongo binaries deployed manually.
      • Mongo server is started via a service by executing:  "sleep 60 && /sbin/runuser mongodb -s /bin/bash -c "/path/to/mongo/binaries/mongod --config /path/to/mongo/conf/mongod.conf"

       

      Attempt to upgrade Mongo binaries - it does not work

      ------------------------------------------------------------------------

      • Mongo binaries are replaced with release 3.4.
      • The previous service nor its permissions are not modified.
      • Mongo is started successfully when calling the binary directly (without using the service) by running "/path/to/mongo/binaries/mongod --config /path/to/mongo/conf/mongod.conf"
      • When starting Mongo via the service, the following error appears:

      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
      2018-07-23T13:02:56.017+0000 I - [initandlisten] Fatal Assertion 28661 at src/mongo/db/storage/storage_engine_metadata.cpp 76
      2018-07-23T13:02:56.017+0000 I - [initandlisten]***aborting after fassert() failure
      2018-07-23T13:02:56.023+0000 F - [initandlisten] Got signal: 6 (Aborted).0x2b4a90866311 0x2b4a90865529 0x2b4a90865a0d 0x2b4a932695e0 0x2b4a934ab1f7 0x2b4a934ac8e8 0x2b4a8fb00f3f 0x2b4a9053adb0 0x2b4a9053af38

      {{ 0x2b4a9043f271 0x2b4a8faed1de 0x2b4a8fb0cecb 0x2b4a93497c05 0x2b4a8fb6c2df}}

       

      Permissions of the storage.bson file:

      mongodb@c675kgrlyncs:/appserver/mongo> ls -la /mongodb/storage.bson
      rw-r---- 1 mongodb mongodb 95 Aug 2 2016 /mongodb/storage.bson

      Show
      Initial setup - works OK ------------------------------- 3.2 Mongo binaries deployed manually. Mongo server is started via a service by executing:  "sleep 60 && /sbin/runuser mongodb -s /bin/bash -c "/path/to/mongo/binaries/mongod --config /path/to/mongo/conf/mongod.conf"   Attempt to upgrade Mongo binaries - it does not work ------------------------------------------------------------------------ Mongo binaries are replaced with release 3.4. The previous service nor its permissions are not modified. Mongo is started successfully when calling the binary directly (without using the service) by running "/path/to/mongo/binaries/mongod --config /path/to/mongo/conf/mongod.conf" When starting Mongo via the service, the following error appears: 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 2018-07-23T13:02:56.017+0000 I - [initandlisten] Fatal Assertion 28661 at src/mongo/db/storage/storage_engine_metadata.cpp 76 2018-07-23T13:02:56.017+0000 I - [initandlisten] ***aborting after fassert() failure 2018-07-23T13:02:56.023+0000 F - [initandlisten] Got signal: 6 (Aborted). 0x2b4a90866311 0x2b4a90865529 0x2b4a90865a0d 0x2b4a932695e0 0x2b4a934ab1f7 0x2b4a934ac8e8 0x2b4a8fb00f3f 0x2b4a9053adb0 0x2b4a9053af38 {{ 0x2b4a9043f271 0x2b4a8faed1de 0x2b4a8fb0cecb 0x2b4a93497c05 0x2b4a8fb6c2df}}   Permissions of the storage.bson file: mongodb@c675kgrlyncs:/appserver/mongo> ls -la /mongodb/storage.bson rw-r ---- 1 mongodb mongodb 95 Aug 2 2016 /mongodb/storage.bson
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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).

            Assignee:
            Nick Brewer (Inactive)
            Reporter:
            Tedi Roca
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: