I don't see a difference between the command I'm issuing and the config file, which I call with sudo mongod -config /etc/nf. When I run this command, I can then run mongo to enter the mongo shell and successfully use the database. Sudo mongod -replSet rs0 -logpath /var/log/mongodb/mongod.log -dbpath /data/db -storageEngine wiredTiger -fork I can launch mongod by issuing the command myself, but I can't get it to work with the config file. I created this issue again, because that issue has been closed, but it still happening with a later version.I am trying to start mongod with a config file on MongoDB 3.2 on Ubuntu 14.04. 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: 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." You'll receive "The service is not responding to the control function". > 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. Archives
December 2022
Categories |