-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: WiredTiger
-
None
-
Fully Compatible
-
ALL
-
Storage 2017-04-17, Storage 2017-05-08
Hello, i'm running mongodb on VPS, here is the version:
MongoDB shell version v3.4.1
git version: 5e103c4f5583e2566a45d740225dc250baacfbd7
OpenSSL version: OpenSSL 1.0.1 14 Mar 2012
allocator: tcmalloc
modules: none
build environment:
distmod: ubuntu1204
distarch: x86_64
target_arch: x86_64
I had an unexpected shutdown, i looked up the log and i can see following:
2017-03-02T01:44:58.205+0200 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1", port: 27017 }, storage: { dbPath: "/var/lib/mongodb", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
2017-03-02T01:44:58.205+0200 W - [initandlisten] Detected unclean shutdown - /var/lib/mongodb/mongod.lock is not empty.
2017-03-02T01:44:58.224+0200 I - [initandlisten] Detected data files in /var/lib/mongodb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2017-03-02T01:44:58.224+0200 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2017-03-02T01:44:58.224+0200 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=2560M,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),
2017-03-02T01:44:58.235+0200 I - [initandlisten] Assertion: 28595:2: No such file or directory src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 267
2017-03-02T01:44:58.236+0200 I STORAGE [initandlisten] exception in initAndListen: 28595 2: No such file or directory, terminating
2017-03-02T01:44:58.236+0200 I NETWORK [initandlisten] shutdown: going to close listening sockets...
2017-03-02T01:44:58.236+0200 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2017-03-02T01:44:58.236+0200 I NETWORK [initandlisten] shutdown: going to flush diaglog...
2017-03-02T01:44:58.236+0200 I CONTROL [initandlisten] now exiting
2017-03-02T01:44:58.236+0200 I CONTROL [initandlisten] shutting down with code:100
I get exactly same message when i try to do mongod --repair --dbpath /var/lib/mongodb
Someone please help!!! I will be thrown out from work...
- related to
-
SERVER-27820 Improve storage engine logging at startup to include additional failure information
-
- Closed
-
- links to