Details
-
Bug
-
Resolution: Incomplete
-
Major - P3
-
None
-
None
-
None
-
ALL
Description
Hello support Team. I need help, mongo DB can't start after stop on cloud server . I can't start mongo after space on the server was the end. Now I added few GB, but the MongoDB can't start. I'm try offline on windows (download all data from cloud), same problem. Error showing like this:
$ mongod --repair --storageEngine wiredTiger --dbpath "D:\data\db" |
2019-08-07T18:03:30.013+0700 I CONTROL [initandlisten] MongoDB starting : pid=5672 port=27017 dbpath=D:\data\db 64-bit host=localhost |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2 |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] db version v3.2.22 |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] git version: 105acca0d443f9a47c1a5bd608fd7133840a58dd |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2o-fips 27 Mar 2018 |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] allocator: tcmalloc |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] modules: none |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] build environment: |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] distmod: 2008plus-ssl |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] distarch: x86_64 |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] target_arch: x86_64 |
2019-08-07T18:03:30.014+0700 I CONTROL [initandlisten] options: { repair: true, storage: { dbPath: "D:\data\db", engine: "wiredTiger" } } |
2019-08-07T18:03:30.015+0700 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint. |
2019-08-07T18:03:30.015+0700 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=1G,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),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress), |
2019-08-07T18:03:30.023+0700 E STORAGE [initandlisten] WiredTiger (-31802) [1565175810:23586][5672:140707856520016], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error |
2019-08-07T18:03:30.023+0700 E STORAGE [initandlisten] WiredTiger (0) [1565175810:23586][5672:140707856520016], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata |
2019-08-07T18:03:30.023+0700 E STORAGE [initandlisten] WiredTiger (0) [1565175810:23586][5672:140707856520016], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk |
2019-08-07T18:03:30.023+0700 E STORAGE [initandlisten] WiredTiger (0) [1565175810:23586][5672:140707856520016], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options |
2019-08-07T18:03:30.024+0700 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error |
2019-08-07T18:03:30.024+0700 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating |
2019-08-07T18:03:30.024+0700 I CONTROL [initandlisten] dbexit: rc: 100 |
|
Please help me, thank you