Urgent Issue:MongoDb service auto stop after a few days

[ChCow]

 Dear Creator,
I am sorry to trouble you about a MongoDb uagent issue,Could you help to give a look.
Issue detail like following:
1.I have installed MongoDb V2.2 to Windows2003 64bit.
2.Run MongoDb service by use command "mongod --auth --logpath D:\MongoDB\2.2.0\bin\Logs\MongoDB.log  --logappend --dbpath D:\MongoDB\2.2.0\bin\Data --directoryperdb --serviceName 'MongoDb-Host-02'".
3.Running normally until after 8 days.MongoDb service auto stop.I have review the log,but I can't find any exception.
4.Restart MongoDb service,run succeed,but after a few days,MongoDb auto stop.

Note:
MongoDb stop log like following,maybe it can help you debug,Thanks for your focus.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
 Thu Oct 25 16:20:09 [consoleTerminate] shutdown: going to close listening sockets...
Thu Oct 25 16:20:09 [consoleTerminate] closing listening socket: 460
Thu Oct 25 16:20:09 [consoleTerminate] closing listening socket: 464
Thu Oct 25 16:20:09 [consoleTerminate] shutdown: going to flush diaglog...
Thu Oct 25 16:20:09 [consoleTerminate] shutdown: going to close sockets...
Thu Oct 25 16:20:09 [consoleTerminate] shutdown: waiting for fs preallocator...
Thu Oct 25 16:20:09 [consoleTerminate] shutdown: lock for final commit...
Thu Oct 25 16:20:09 [consoleTerminate] shutdown: final commit...
Thu Oct 25 16:20:09 [conn129] end connection 192.168.168.62:3849 (0 connections now open)
Thu Oct 25 16:20:09 [consoleTerminate] shutdown: closing all files...
Thu Oct 25 16:20:09 [consoleTerminate] closeAllFiles() finished
Thu Oct 25 16:20:09 [consoleTerminate] journalCleanup...
Thu Oct 25 16:20:09 [consoleTerminate] removeJournalFiles
Thu Oct 25 16:20:09 [consoleTerminate] shutdown: removing fs lock...
Thu Oct 25 16:20:09 dbexit: really exiting now
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 

[Andre de Frere]

Hi,

The log excerpt you have given is not showing what actually caused the process to shut down.  Could you attach more of the log file please?

Regards,

André

[ChCow]

 Thanks for your quickly reply.

I still can't find any exception after review the MongoDb log seriously again,The log only include record of data chang,so i can't provide more detail log to you.
I have talk with other MongoDb users,they said that they often meet this problem,they are found the root cause is Massive Data and Windows 2003 issue,because they have not meet this problem under linux.But sometimes my data size only 1.3G,so i think i meet a diffierent problem.
Today,I found following exception when MongoDb stop,maybe they are related with this issue.
>>>1.I found a system exception,the exception point the RockMongo problem,RockMongo is a visual manager,which manage the MongoDb.
>>>2.I start the Nginx service when I have installed MongoDb to Window2003 64bit,Nginx was running until MongoDb auto stop.System event record a Nginx process issue when MongoDb stop.
After debug more days,I guess that the root cause of MongoDb auto stop was occured by RockMongo and Nginx,Now,i stop more application and services for debug MongoDb,if the urgent issue still exist,i will migrate the project from Windows to Linux although waste too much resource.
I hope above description can help you to debug this urgent issue,Thanks for you focus again. 

[ChCow]

Thanks for your quickly reply.

Note:

MongoDb stop log like following,maybe it can help you debug,Thanks for your focus.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

 ***** SERVER RESTARTED *****

Wed Nov 07 08:46:33 Trying to start Windows service 'MongoDB'

Wed Nov 07 08:46:33 Service running

Wed Nov 07 08:46:33 [initandlisten] MongoDB starting : pid=5040 port=27017 dbpath=D:\WebApp\MongoDb\2.2.0-Master\bin\Data master=1 32-bit host=user-databackup

Wed Nov 07 08:46:33 [initandlisten] 

Wed Nov 07 08:46:33 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data

Wed Nov 07 08:46:33 [initandlisten] **       see http://blog.mongodb.org/post/137788967/32-bit-limitations

Wed Nov 07 08:46:33 [initandlisten] **       with --journal, the limit is lower

Wed Nov 07 08:46:33 [initandlisten] 

Wed Nov 07 08:46:33 [initandlisten] db version v2.2.0, pdfile version 4.5

Wed Nov 07 08:46:33 [initandlisten] git version: f5e83eae9cfbec7fb7a071321928f00d1b0c5207

Wed Nov 07 08:46:33 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=0, build=6002, platform=2, service_pack='Service Pack 2') BOOST_LIB_VERSION=1_49

Wed Nov 07 08:46:33 [initandlisten] options: { auth: true, dbpath: "D:\WebApp\MongoDb\2.2.0-Master\bin\Data", directoryperdb: true, logappend: true, logpath: "D:\WebApp\MongoDb\2.2.0-Master\bin\Logs\MongoDB.log", master: true, service: true }

Wed Nov 07 08:46:33 [initandlisten] Unable to check for journal files due to: boost::filesystem::basic_directory_iterator constructor: 系统找不到指定的路径。: "D:\WebApp\MongoDb\2.2.0-Master\bin\Data\journal"

Wed Nov 07 08:46:33 [initandlisten] waiting for connections on port 27017

Wed Nov 07 08:46:33 [websvr] admin web console waiting for connections on port 28017

Wed Nov 07 08:46:34 [initandlisten] connection accepted from 192.168.168.19:58907 #1 (1 connection now open)

Wed Nov 07 08:46:34 [conn1]  authenticate db: PF_ServiceMongoDb { authenticate: 1.0, user: "user", nonce: "3e69c1c10bc71b56", key: "a4fe43c8453115a410c3803bf42f0112" }

Wed Nov 07 08:46:50 [conn1] end connection 192.168.168.19:58907 (0 connections now open)

Wed Nov 07 08:46:51 [initandlisten] connection accepted from 192.168.168.19:58910 #2 (1 connection now open)

Wed Nov 07 08:46:51 [conn2]  authenticate db: PF_ServiceMongoDb { authenticate: 1.0, user: "user", nonce: "d56589e58aabe242", key: "299cecea0465238eb56b22f293af35bf" 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 

[Andre de Frere]

Hi,

The log excerpt shows when the mongod process is started, but not what happens before this - when the process is exiting.  Do you have any logs where it shows the process actually shutting down?  Do you use --logappend, or do you have log entries from a previous log?

Regards,

André