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

Unexpected Shutdown Version 3.6

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.2
    • Component/s: None
    • None

      Hello,

      When I startup my mongod used as oplog store (Ops Manager), it dies.

      2018-01-22T11:44:55.664+0100 I CONTROL  [main] ***** SERVER RESTARTED *****
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] MongoDB starting : pid=90779 port=27018 dbpath=/data/bckdb 64-bit host=srv02535.cepsacorp.es
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] db version v3.6.2
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] git version: 489d177dbd0f0420a8ca04d39fd78d0a2c539420
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] allocator: tcmalloc
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] modules: enterprise
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] build environment:
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten]     distmod: rhel70
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten]     distarch: x86_64
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten]     target_arch: x86_64
      2018-01-22T11:44:55.728+0100 I CONTROL  [initandlisten] options: { config: "/etc/mongod-bck.conf", net: { bindIp: "0.0.0.0", port: 27018 }, processManagement: { fork: true, pidFilePath: "/var/run/mongodb-bck/mongod-bck.pid" }, replication: { replSetName: "bckdb" }, security: { authorization: "enabled", keyFile: "/etc/mongodb-keyfile" }, storage: { dbPath: "/data/bckdb", journal: { enabled: true }, wiredTiger: { engineConfig: { cacheSizeGB: 4.0 } } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/bckdb.log" } }
      2018-01-22T11:44:55.734+0100 I -        [initandlisten] Detected data files in /data/bckdb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
      2018-01-22T11:44:55.737+0100 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=4096M,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-01-22T11:44:55.932+0100 I STORAGE  [initandlisten] WiredTiger message [1516617895:932084][90779:0x7f2a00edeb00], txn-recover: Main recovery loop: starting at 3864/18950400
      2018-01-22T11:44:56.048+0100 I STORAGE  [initandlisten] WiredTiger message [1516617896:48658][90779:0x7f2a00edeb00], txn-recover: Recovering log 3864 through 3865
      2018-01-22T11:44:56.118+0100 I STORAGE  [initandlisten] WiredTiger message [1516617896:118749][90779:0x7f2a00edeb00], txn-recover: Recovering log 3865 through 3865
      2018-01-22T11:44:56.329+0100 I STORAGE  [initandlisten] Starting WiredTigerRecordStoreThread local.oplog.rs
      2018-01-22T11:44:56.329+0100 I STORAGE  [initandlisten] The size storer reports that the oplog contains 7389 records totaling to 9434369281 bytes
      2018-01-22T11:44:56.329+0100 I STORAGE  [initandlisten] Scanning the oplog to determine where to place markers for truncation
      2018-01-22T11:46:25.386+0100 I CONTROL  [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
      2018-01-22T11:46:25.386+0100 I NETWORK  [signalProcessingThread] shutdown: going to close listening sockets...
      2018-01-22T11:46:25.386+0100 I NETWORK  [signalProcessingThread] removing socket file: /tmp/mongodb-27018.sock
      2018-01-22T11:46:25.386+0100 I CONTROL  [signalProcessingThread] now exiting
      2018-01-22T11:46:25.386+0100 I CONTROL  [signalProcessingThread] shutting down with code:0
      

      Thanks
      Juan

            Assignee:
            mark.agarunov Mark Agarunov
            Reporter:
            juan.soto@mongodb.com Juan Soto (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: