Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38101

Secondary Crashing with "aborting after fassert() failure" error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      N/A

      Show
      N/A

      Description

      I upgraded this test mongodb replica set from 3.4.x to 3.6.7  about 2 weeks back.

       

      Today, i experienced a secondary mongod crashing with the following errors:

      Secondary Crashing with "aborting after fassert() failure" error

      Mongod Log extracts:

       

      2018-11-12T17:16:13.664-0800 I NETWORK [thread28] Successfully connected to 10.10.190.6:27017 (49250 connections now open to xxx with a 0 second timeout)
      2018-11-12T17:16:13.664-0800 I NETWORK [thread28] scoped connection to xxxx not being returned to the pool
      2018-11-12T17:16:41.838-0800 I NETWORK [listener] connection accepted from xxx #49461 (15 connections now open)
      2018-11-12T17:16:41.939-0800 I NETWORK [conn49461] received client metadata from xxxx:42908 conn49461: { driver:

      { name: "mongo-csharp-driver", version: "2.7.0.0" }

      , os: { type: "Linux", name: "Linux 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016", architecture: "x86_64", version: "4.2.0-42-generic" }, platform: ".NET Core 4.6.26328.01" }
      2018-11-12T17:17:09.062-0800 F REPL [repl writer worker 13] writer worker caught exception: NamespaceNotFound: Failed to apply operation due to missing collection (6e46dffd-9a3c-496c-81b9-3a7cfa4f1ac6): { ts: Timestamp(1542071829, 1), t: 27, h: -7111336552031876369, v: 2, op: "i", ns: "config.system.sessions", ui: UUID("6e46dffd-9a3c-496c-81b9-3a7cfa4f1ac6"), wall: new Date(1542071829042), o: { _id:

      { id: UUID("85cc8499-8b2c-4b4f-a871-5b4fc8358968"), uid: BinData(0, E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855) }

      , lastUse: new Date(1542071829043) } } on: { ts: Timestamp(1542071829, 1), t: 27, h: -7111336552031876369, v: 2, op: "i", ns: "config.system.sessions", ui: UUID("6e46dffd-9a3c-496c-81b9-3a7cfa4f1ac6"), wall: new Date(1542071829042), o: { _id:

      { id: UUID("85cc8499-8b2c-4b4f-a871-5b4fc8358968"), uid: BinData(0, E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855) }

      , lastUse: new Date(1542071829043) } }
      2018-11-12T17:17:09.062-0800 F - [repl writer worker 13] Fatal assertion 16359 NamespaceNotFound: Failed to apply operation due to missing collection (6e46dffd-9a3c-496c-81b9-3a7cfa4f1ac6): { ts: Timestamp(1542071829, 1), t: 27, h: -7111336552031876369, v: 2, op: "i", ns: "config.system.sessions", ui: UUID("6e46dffd-9a3c-496c-81b9-3a7cfa4f1ac6"), wall: new Date(1542071829042), o: { _id:

      { id: UUID("85cc8499-8b2c-4b4f-a871-5b4fc8358968"), uid: BinData(0, E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855) }

      , lastUse: new Date(1542071829043) } } at src/mongo/db/repl/sync_tail.cpp 1209
      2018-11-12T17:17:09.062-0800 F - [repl writer worker 13]

      ***aborting after fassert() failure

       

      I tried to restart and am getting the same error with the mongod crashing.

      Also, after the upgrade, i did modify the featureCompatibilityVersion to 3.6

      { "_id" : "featureCompatibilityVersion", "version" : "3.6" }

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: