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

MongoDB cannot start after repair

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Storage NYC 2018-11-19

      Description

      Hello.

      I installed a MongoDB 4.0.4 standalone server in order to perform a migration from Windows to CentOS. After of an unexpected shutdown of the server (virtualization issue) I cannot start a MongoDB server. I perform a repair procedure as described in an documentation: mongod --repair --directoryperdb --dbpath /opt/mongodb/data and assign permissions to mongod again after that by chown.

      I added a repair log here.

      Any way MOngoDB cannot start and write the following output in the log:

      2018-11-12T09:39:47.043+0000 I CONTROL [main] ***** SERVER RESTARTED *****
      2018-11-12T09:39:47.069+0000 I NETWORK [main] --maxConns too high, can only handle 51200
      2018-11-12T09:39:47.069+0000 I CONTROL [initandlisten] MongoDB starting : pid=2443 port=27017 dbpath=/opt/mongodb/data 64-bit host=uk1lv8818
      2018-11-12T09:39:47.069+0000 I CONTROL [initandlisten] db version v4.0.4
      2018-11-12T09:39:47.069+0000 I CONTROL [initandlisten] git version: f288a3bdf201007f3693c58e140056adf8b04839
      2018-11-12T09:39:47.069+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
      2018-11-12T09:39:47.069+0000 I CONTROL [initandlisten] allocator: tcmalloc
      2018-11-12T09:39:47.069+0000 I CONTROL [initandlisten] modules: none
      2018-11-12T09:39:47.069+0000 I CONTROL [initandlisten] build environment:
      2018-11-12T09:39:47.070+0000 I CONTROL [initandlisten] distmod: rhel70
      2018-11-12T09:39:47.070+0000 I CONTROL [initandlisten] distarch: x86_64
      2018-11-12T09:39:47.070+0000 I CONTROL [initandlisten] target_arch: x86_64
      2018-11-12T09:39:47.070+0000 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net:

      { bindIp: "0.0.0.0", maxIncomingConnections: 65536, port: 27017 }

      , processManagement: { fork: true, pidFilePath: "/var/run/mongodb/mongod.pid", timeZoneInfo: "/usr/share/zoneinfo" }, storage: { dbPath: "/opt/mongodb/data", directoryPerDB: true, engine: "wiredTiger", journal:

      { enabled: true }

      }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
      2018-11-12T09:39:47.070+0000 I NETWORK [initandlisten] --maxConns too high, can only handle 51200
      2018-11-12T09:39:47.070+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=31620M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
      2018-11-12T09:39:48.453+0000 I STORAGE [initandlisten] WiredTiger message [1542015588:453710][2443:0x7fbedb4a3b80], txn-recover: Main recovery loop: starting at 9590/132608 to 9591/256
      2018-11-12T09:39:48.455+0000 I STORAGE [initandlisten] WiredTiger message [1542015588:455315][2443:0x7fbedb4a3b80], txn-recover: Recovering log 9590 through 9591
      2018-11-12T09:39:48.613+0000 I STORAGE [initandlisten] WiredTiger message [1542015588:613087][2443:0x7fbedb4a3b80], file:sizeStorer.wt, txn-recover: Recovering log 9591 through 9591
      2018-11-12T09:39:48.680+0000 I STORAGE [initandlisten] WiredTiger message [1542015588:680738][2443:0x7fbedb4a3b80], file:sizeStorer.wt, txn-recover: Set global recovery timestamp: 0
      2018-11-12T09:39:49.027+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
      2018-11-12T09:41:17.094+0000 I CONTROL [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
      2018-11-12T09:41:17.094+0000 I NETWORK [signalProcessingThread] shutdown: going to close listening sockets...
      2018-11-12T09:41:17.094+0000 I NETWORK [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
      2018-11-12T09:41:17.094+0000 I CONTROL [signalProcessingThread] now exiting
      2018-11-12T09:41:17.094+0000 I CONTROL [signalProcessingThread] shutting down with code:0

      Need your help ASAP.

      Regards,

      Pavel

        Attachments

        1. mongod_15112018.log
          13.26 MB
        2. mongodb_repair_log.txt
          75.27 MB

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: