we run one mongos , one config server and 10 mongod shards.
we kill all mongo possess and restart all server. but config server not start and give error "there are no journal files to recover."

after this run config server with --repair. and start mongos , insert one record it give socket exception.

logs when config server not start.

old lock file: /u01/shard1/configdb/mongod.lock. probably means unclean shutdown,
but there are no journal files to recover.
this is likely human error or filesystem corruption.
found 1 dbs.
see: http://dochub.mongodb.org/core/repair for more information
*************
Sun Jan 8 19:00:01 [initandlisten] User Assertion: 12596:old lock file
Sun Jan 8 19:00:01 [initandlisten] exception in initAndListen: 12596 old lock file, terminating
Sun Jan 8 19:00:01 dbexit:
Sun Jan 8 19:00:01 [initandlisten] shutdown: going to close listening sockets...
Sun Jan 8 19:00:01 [initandlisten] shutdown: going to flush diaglog...
Sun Jan 8 19:00:01 [initandlisten] shutdown: going to close sockets...
Sun Jan 8 19:00:01 [initandlisten] shutdown: waiting for fs preallocator...
Sun Jan 8 19:00:01 [initandlisten] shutdown: lock for final commit...
Sun Jan 8 19:00:01 [initandlisten] shutdown: final commit...
Sun Jan 8 19:00:01 [initandlisten] shutdown: closing all files...
Sun Jan 8 19:00:01 [initandlisten] closeAllFiles() finished
Sun Jan 8 19:00:01 dbexit: really exiting now

log when insert a record

Sun Jan 8 20:19:53 [conn2] creating new connection to:192.168.50.168:10000
Sun Jan 8 20:19:53 BackgroundJob starting: ConnectBG
Sun Jan 8 20:19:53 [conn2] DBException in process: socket exception
Sun Jan 8 20:19:58 [conn2] Socket recv() conn closed? 192.168.50.51:63406
Sun Jan 8 20:19:58 [conn2] SocketException: remote: 192.168.50.51:63406 error: 9001 socket exception [0] server [192.168.50.51:63406]
Sun Jan 8 20:20:20 [conn3] Request::process ns: 00080112.Database msg id:41 attempt: 0
Sun Jan 8 20:20:20 [conn3] write: 00080112.Database