![]() ![]() ![]() The work around for this issue to simply to install the config file in a path without spaces, such as "c:\mongo\nf". Note that the -config value is NOT quoted even though it was quoted on the command line when the service was installed. "c:\mongo\bin\mongod.exe" -config c:\program files\mongo\nf -service Inspecting the ImagePath key in the registry at HKLM/System/CurrentControlSet/services/MongoDB/ImagePath reveals the following value: Add replica set configurations to the configuration file on each server and restart after that: replication. Errors in System log from the Service Control Manager include "A timeout was reached (30000 milliseconds) while waiting for the Mongo DB service to connect" and "The Mongo DB service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Before starting check connectivity between servers: ping, telnet and open ports (2700 for arbiter). You'll receive "The service is not responding to the control function". The MongoDB service’s launching command path is stored in Windows Registry at the following path: HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\services\MongoDB\ImagePath The configuration path is set as the -config argument of the launching command, e.g.: C:\server\mongodb\bin\mongod.exe -config 'C:\server\mongodb\cfg\mongod.cfg' -service. > mongod.exe -config "c:\Program Files\mongo\nf" -installĢ) Attempt the start the MongoDB service using net start Inspecting the ImagePath in the registry reveals that the -config path is not quoted correctly.ġ) Install MongoDB as a service using the following command When installing MongoDB as a Windows Service, if the nf file is located in a path with spaces the service will not start correctly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |