Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
-
Linux DB-SH-06 2.6.32-279.el6.x86_64
*Location*: http://docs.mongodb.org/manual/
*User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
*Referrer*: http://try.mongodb.org/
*Screen Resolution*: 1600 x 900
*repo*: docs
*source*: index
Linux DB-SH-06 2.6.32-279.el6.x86_64 *Location*: http://docs.mongodb.org/manual/ *User-Agent*: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 *Referrer*: http://try.mongodb.org/ *Screen Resolution*: 1600 x 900 *repo*: docs *source*: index
Description
hi all
I was faced with a very difficult problem when we use the "Replica Sets".
Mongodb is always in do not know the reasons for service termination condition.I very worry, every time the abnormal termination of service just print out the following log content without any other valuable information.
the following logs:
2014-07-14T15:15:02.385+0800 [signalProcessingThread] shutdown: closing all files...
2014-07-14T15:15:02.442+0800 [signalProcessingThread] closeAllFiles() finished
2014-07-14T15:15:02.442+0800 [signalProcessingThread] journalCleanup...
2014-07-14T15:15:02.442+0800 [signalProcessingThread] removeJournalFiles
2014-07-14T15:15:02.506+0800 [signalProcessingThread] shutdown: removing fs lock...
2014-07-14T15:15:02.507+0800 [signalProcessingThread] dbexit: really exiting now
Other information:
When the mongodb is down.The system has enough memory,The machine is not running any additional procedures.Mongodb not pressure.
my version:2.6.0
When I use the "inumactl --interleave=all",As it happened
I don't know why.please help me
Looking forward to your reply:864302419@qq.com