I am trying to run mongod --repair command. But It always fails

by Pragyan Tripathi   Last Updated July 11, 2019 21:06 PM - source

I am trying to run mongodb --repair command after running for a considerable amount of time it shutsdown with following logs.

t.oplogTruncateAfterPoint" }
2019-07-11T20:36:14.034+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.036+0000 I STORAGE  [initandlisten] Repairing collection local.startup_log
2019-07-11T20:36:14.038+0000 I STORAGE  [initandlisten] Verify succeeded on uri table:collection-2--6589857005450806687. Not salvaging.
2019-07-11T20:36:14.044+0000 I INDEX    [initandlisten] build index on: local.startup_log properties: { v: 2, key: { _id: 1 }, name: "_id_", ns: "local.startup_log" }
2019-07-11T20:36:14.044+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.047+0000 I STORAGE  [initandlisten] Repairing collection local.system.replset
2019-07-11T20:36:14.048+0000 I STORAGE  [initandlisten] Verify succeeded on uri table:collection-7-2924198575954508702. Not salvaging.
2019-07-11T20:36:14.054+0000 I INDEX    [initandlisten] build index on: local.system.replset properties: { v: 2, key: { _id: 1 }, name: "_id_", ns: "local.system.replset" }
2019-07-11T20:36:14.054+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.056+0000 I STORAGE  [initandlisten] Repairing collection local.system.rollback.id
2019-07-11T20:36:14.058+0000 I STORAGE  [initandlisten] Verify succeeded on uri table:collection-4-2924198575954508702. Not salvaging.
2019-07-11T20:36:14.065+0000 I INDEX    [initandlisten] build index on: local.system.rollback.id properties: { v: 2, key: { _id: 1 }, name: "_id_", ns: "local.system.rollback.id" }
2019-07-11T20:36:14.065+0000 I INDEX    [initandlisten]      building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-07-11T20:36:14.072+0000 W ASIO     [initandlisten] No TransportLayer configured during NetworkInterface startup
2019-07-11T20:36:14.072+0000 I STORAGE  [initandlisten] finished checking dbs
2019-07-11T20:36:14.072+0000 I REPL     [initandlisten] shutting down replication subsystems
2019-07-11T20:36:14.072+0000 W REPL     [initandlisten] ReplicationCoordinatorImpl::shutdown() called before startup() finished.  Shutting down without cleaning up the replication system
2019-07-11T20:36:14.073+0000 I STORAGE  [WTOplogJournalThread] oplog journal thread loop shutting down
2019-07-11T20:36:14.073+0000 I STORAGE  [initandlisten] WiredTigerKVEngine shutting down
2019-07-11T20:36:14.073+0000 I STORAGE  [initandlisten] Shutting down session sweeper thread
2019-07-11T20:36:14.073+0000 I STORAGE  [initandlisten] Finished shutting down session sweeper thread
2019-07-11T20:36:14.502+0000 I STORAGE  [initandlisten] shutdown: removing fs lock...
2019-07-11T20:36:14.502+0000 I CONTROL  [initandlisten] now exiting
2019-07-11T20:36:14.502+0000 I CONTROL  [initandlisten] shutting down with code:0

Please Help.



Related Questions



Benchmarking Mongodb Queries Without cache

Updated June 20, 2017 09:06 AM

Recover MongoDB data without WiredTiger.wt file

Updated August 11, 2017 15:06 PM

MongoDB document delete and fragmentation

Updated August 05, 2015 14:02 PM