MongoDB service failed to start: The service did not respond to the start or control request in a timely fashion

Ops and Admin
1

This is the third time in a few months that I have had a Dell WMS crash which is using MongoDB.

Each time it is a problem getting the MongoDB service up and running. I’m getting an error 1053: The service did not respond to the start or control request in a timely fashion.

Mongod.cfg:

dbpath=C:\Program Files\DELL\WMS\Database\Mongo
logpath=C:\Program Files\DELL\WMS\MongoDb\mongod.log
bind_ip=localhost
auth=true
port=27017

Nothing is using port 27017, event viewer is only informing about timely fashion - no resonable info.

Mongo log:

2024-01-18T20:19:59.237+0100 I  CONTROL  [serviceShutdown] got SERVICE_CONTROL_PRESHUTDOWN request from Windows Service Control Manager, will terminate after current cmd ends
2024-01-18T20:19:59.348+0100 I  REPL     [serviceShutdown] Stepping down the ReplicationCoordinator for shutdown, waitTime: 10000ms
2024-01-18T20:19:59.523+0100 I  SHARDING [serviceShutdown] Shutting down the WaitForMajorityService
2024-01-18T20:19:59.696+0100 I  CONTROL  [serviceShutdown] Shutting down the LogicalSessionCache
2024-01-18T20:19:59.756+0100 I  NETWORK  [serviceShutdown] shutdown: going to close listening sockets...
2024-01-18T20:19:59.845+0100 I  NETWORK  [serviceShutdown] Shutting down the global connection pool
2024-01-18T20:19:59.845+0100 I  STORAGE  [serviceShutdown] Shutting down the FlowControlTicketholder
2024-01-18T20:19:59.860+0100 I  -        [serviceShutdown] Stopping further Flow Control ticket acquisitions.
2024-01-18T20:19:59.860+0100 I  STORAGE  [serviceShutdown] Shutting down the PeriodicThreadToAbortExpiredTransactions
2024-01-18T20:19:59.873+0100 I  STORAGE  [serviceShutdown] Shutting down the PeriodicThreadToDecreaseSnapshotHistoryIfNotNeeded
2024-01-18T20:19:59.881+0100 I  REPL     [serviceShutdown] Shutting down the ReplicationCoordinator
2024-01-18T20:19:59.881+0100 I  SHARDING [serviceShutdown] Shutting down the ShardingInitializationMongoD
2024-01-18T20:19:59.900+0100 I  REPL     [serviceShutdown] Enqueuing the ReplicationStateTransitionLock for shutdown
2024-01-18T20:19:59.900+0100 I  -        [serviceShutdown] Killing all operations for shutdown
2024-01-18T20:19:59.900+0100 I  COMMAND  [serviceShutdown] Shutting down all open transactions
2024-01-18T20:19:59.900+0100 I  REPL     [serviceShutdown] Acquiring the ReplicationStateTransitionLock for shutdown
2024-01-18T20:19:59.900+0100 I  INDEX    [serviceShutdown] Shutting down the IndexBuildsCoordinator
2024-01-18T20:19:59.952+0100 I  NETWORK  [serviceShutdown] Shutting down the ReplicaSetMonitor
2024-01-18T20:19:59.977+0100 I  CONTROL  [serviceShutdown] Shutting down free monitoring
2024-01-18T20:19:59.988+0100 I  CONTROL  [serviceShutdown] Shutting down free monitoring
2024-01-18T20:19:59.997+0100 I  FTDC     [serviceShutdown] Shutting down full-time data capture
2024-01-18T20:19:59.997+0100 I  FTDC     [serviceShutdown] Shutting down full-time diagnostic data capture
2024-01-18T20:20:00.018+0100 I  STORAGE  [serviceShutdown] Shutting down the HealthLog
2024-01-18T20:20:00.018+0100 I  STORAGE  [serviceShutdown] Shutting down the storage engine
2024-01-18T20:20:00.032+0100 I  STORAGE  [serviceShutdown] Deregistering all the collections
2024-01-18T20:20:01.511+0100 I  STORAGE  [serviceShutdown] Timestamp monitor shutting down
2024-01-18T20:20:01.511+0100 I  STORAGE  [serviceShutdown] WiredTigerKVEngine shutting down
2024-01-18T20:20:01.514+0100 I  STORAGE  [serviceShutdown] Shutting down session sweeper thread
2024-01-18T20:20:01.530+0100 I  STORAGE  [serviceShutdown] Finished shutting down session sweeper thread
2024-01-18T20:20:01.530+0100 I  STORAGE  [serviceShutdown] Shutting down journal flusher thread
2024-01-18T20:20:01.596+0100 I  STORAGE  [serviceShutdown] Finished shutting down journal flusher thread
2024-01-18T20:20:01.597+0100 I  STORAGE  [serviceShutdown] Shutting down checkpoint thread
2024-01-18T20:20:01.597+0100 I  STORAGE  [serviceShutdown] Finished shutting down checkpoint thread
2024-01-18T20:20:10.020+0100 I  STORAGE  [serviceShutdown] shutdown: removing fs lock...
2024-01-18T20:20:10.021+0100 I  -        [serviceShutdown] Dropping the scope cache for shutdown
2024-01-18T20:20:10.030+0100 I  CONTROL  [serviceShutdown] now exiting

Tried to fix a database with:
mongod --dbpath “C:\Program Files\DELL\WMS\Database\Mongo” --repair
no success.

If I restore a backup copy of this machine - mongodb service will start and will work for a month or two.
Can you help me troubleshot is issue?

Thank you and I apologise if picked wrong category.

2

Check if any invalid entry in your config file
What is the version of your WMS
For the latest versions you have to use YAML format config files
Is auth:true a valid param?

3

Hi Ramachandra,

This machine is using WMS 3.7.0.458.
I cannot perform an update when MongoDB service is not working.

Using:
mongod.exe --config <config file>
Did not help - CMD was running indefinitely.

I guess auth: true is a valid param - if I restore machine backup the config file will be the same and the service will start.

4

I just restored virtual machine once again… Close this topic.

5

Hello,
We have also encountered this issue while restoring a snapshot of a station.
It doesn’t happen systematically, but it can occur.
Unfortunately, we don’t have a solution for this yet, and it is quite frustrating.
This problem started appearing after we upgraded our MongoDB version from 4.4 to 7.0.11 and 7.0.16.
We never experienced it while using MongoDB 4.x (4.0, 4.2, 4.4, etc.).
Our configuration file is correct, and the issue only arises after performing a snapshot and restoration (Problem reproduced on Linux Redhat 8 and MS Windows 2019).
It also seems more likely to occur when the station is running slower than usual.

Error 12/7/2024 7:09:30 PM Service Control Manager 7000 None The SafeX3MongoDB-NODE0 service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error 12/7/2024 7:09:30 PM Service Control Manager 7009 None A timeout was reached (45000 milliseconds) while waiting for the SafeX3MongoDB-NODE0 service to connect.
Error 12/7/2024 7:09:30 PM Service Control Manager 7000 None The SafeX3MongoDB-MONGO01 service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error 12/7/2024 7:09:30 PM Service Control Manager 7009 None A timeout was reached (45000 milliseconds) while waiting for the SafeX3MongoDB-MONGO01 service to connect.
Error 12/7/2024 7:09:30 PM Service Control Manager 7000 None The SafeX3MongoDB-MONGO03 service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Error 12/7/2024 7:09:30 PM Service Control Manager 7009 None A timeout was reached (45000 milliseconds) while waiting for the SafeX3MongoDB-MONGO03 service to connect.
Error 12/7/2024 7:08:44 PM Service Control Manager 7000 None The luafv service failed to start due to the following error:
This driver has been blocked from loading