Failing to start mongos (aborting after invariant() failure)

XMLWordPrintableJSON

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

      Good afternoon,

      We are experiencing an issue with the deployment of a MongoDB 3.6 Sharded Cluster. Following the tutorial procedure ( https://docs.mongodb.com/manual/tutorial/deploy-shard-cluster/), a single-member Config Server Replica Set and a single-member Shard Replica
      Set were successfully started and initiated. However, starting mongos failed (see below
      the log file errors).

      Thank you in advance,

      2018-03-07T13:11:07.960-0500 I ASIO     [NetworkInterfaceASIO-ShardRegistry-0] Successfully connected to xf03id1-mdb01:27019, took 0ms (4 connections now open to xf03id1-mdb01:27019)
2018-03-07T13:11:07.972-0500 W SHARDING [replSetDistLockPinger] pinging failed for distributed lock pinger :: caused by :: LockStateChangeFailed: findAndModify query predicate didn't match any lock document
2018-03-07T13:11:09.961-0500 I FTDC     [mongosMain] Initializing full-time diagnostic data capture with directory '/var/log/mongodb-1/mongos-conf.diagnostic.data'
2018-03-07T13:11:09.962-0500 F -        [mongosMain] Invariant failure globalInShutdownDeprecated() src/mongo/db/auth/user_cache_invalidator_job.cpp 116
2018-03-07T13:11:09.962-0500 F -        [mongosMain] 

***aborting after invariant() failure

2018-03-07T13:11:09.970-0500 F -        [mongosMain] Got signal: 6 (Aborted).

            Assignee:
            Ramon Fernandez Marina
            Reporter:
            Nikolay Malitsky
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: