-
Type:
Bug
-
Resolution: Incomplete
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: WiredTiger
-
None
-
ALL
Few days back my mongod crashed. It's a single node machine storing about 1 TB of data. The machine is ubuntu 16.04 and mongodb version is 3.4.2. The directory has all files intact.
When I try to start mongod again, I see these log entries:
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] MongoDB starting : pid=6017 port=28018 dbpath=/data-raid/mongo/data 64-bit host=mongo-vm08
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] db version v3.4.2
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] git version: 3f76e40c105fc223b3e5aac3e20dcd026b83b38b
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] allocator: tcmalloc
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] modules: none
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] build environment:
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] distmod: ubuntu1604
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] distarch: x86_64
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] target_arch: x86_64
2017-06-12T12:36:21.649+0000 I CONTROL [initandlisten] options: { net: { port: 28018 }, storage: { dbPath: "/data-raid/mongo/data", directoryPerDB: true }, systemLog: { destination: "file", path: "/data-raid/mongo/logs/mongodb.log" } }
2017-06-12T12:36:21.707+0000 I - [initandlisten] Detected data files in /data-raid/mongo/data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2017-06-12T12:36:21.707+0000 I STORAGE [initandlisten]
2017-06-12T12:36:21.707+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2017-06-12T12:36:21.707+0000 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem
2017-06-12T12:36:21.707+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=7507M,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
- This is it. Nothing else happens. The mongod stays like this for hours. When I use --repair option, this behavior persists.
- The reason I'm using different port other than 27017 is because another mongod is running.