Replica not start on WT_SESSION.open_cursor

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Replica set not started after a crash with following error message:

       

      2018-08-27T09:18:59.132+0200 I STORAGE [initandlisten] WiredTiger message [1535354339:132850][29250:0x7efd697c89c0], txn-recover: Recovering log 5466 through 5466 2018-08-27T09:18:59.252+0200 I STORAGE [initandlisten] WiredTiger message [1535354339:252435][29250:0x7efd697c89c0], txn-recover: Set global recovery timestamp: 0 2018-08-27T09:18:59.371+0200 E STORAGE [initandlisten] WiredTiger error (1) [1535354339:371535][29250:0x7efd697c89c0], file:collection-20-4441079999684442033.wt, WT_SESSION.open_cursor: /data/mongodb/collection-20-4441079999684442033.wt: handle-open: open: Operation not permitted 2018-08-27T09:18:59.371+0200 F - [initandlisten] Invariant failure: ret resulted in status UnknownError: 1: Operation not permitted at src/mongo/db/storage/wiredtiger/wiredtiger_session_cache.cpp 115 2018-08-27T09:18:59.371+0200 F - [initandlisten] ***aborting after invariant() failure

            Assignee:
            Nick Brewer (Inactive)
            Reporter:
            Mathieu Migout
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: