[SERVER-5681] unable to start mongod give exception in initAndListen: 10079 bad .ns file length, cannot open database, terminating Created: 22/Apr/12  Updated: 15/Aug/12  Resolved: 10/Jul/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: jitendra Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

oracle linux


Issue Links:
Related
is related to SERVER-5380 unable to start mongod give exception... Closed
is related to SERVER-5437 mongod config server go in hang state Closed
is related to SERVER-5598 Run command on mongos> db.stats() g... Closed
is related to SERVER-5630 mongos unable to start give error "di... Closed
Operating System: Linux
Participants:

 Description   

we setup mongo servers on two machine.All mongod run with journal option.

machine_1 : 4 mongod, 2 config server, mongos.
machine_2 : 4 mongod, 1 config server.

Unable to start some monogds error logs are below:

Fri Apr 13 19:05:03 [initandlisten] bad .ns file: /u01/shard7/00090412.ns
Fri Apr 13 19:05:03 [initandlisten] User Assertion: 10079:bad .ns file length, cannot open database
Fri Apr 13 19:05:03 [initandlisten] exception in initAndListen: 10079 bad .ns file length, cannot open database, terminating

kindly help me how to start mongod.
Thanks in Advance,
Jitendra Verma



 Comments   
Comment by Ian Whalen (Inactive) [ 10/Jul/12 ]

@jitendra I'm closing this now, but please reopen if you continue to see this issue or if you have any further answers for Scott's questions above.

Comment by Scott Hernandez (Inactive) [ 22/Apr/12 ]

Does this happen on more than one server? Can you run with verbose logging, -vvvvv, and attach the logs? Please include the full logs.

What does "ls -laht" show run from the dbpath directory (where those files are)?

Have you had any disk issues on the system where those files are stored?

Generated at Thu Feb 08 03:09:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.