We encourage you to edit MongoDB in Service Protector and check out the many other settings that may be appropriate for your environment.įor example, send email alerts when the service fails, restart MongoDB nightly to cure memory leaks, and much more. That's it! Next time your computer boots, MongoDB will start and Service Protector will begin monitoring the service to promptly restart it if it fails. The shield icon will go to green to indicate that the MongoDB service is being protected: To start protection, choose Protector > Start "Mongo DB". The MongoDB service is probably already running but it's not yet being monitored by Service Protector (hence the red shield). In a second or two, an entry for MongoDB will show up in the Service Protector window. If you find that the MongoDB windows service occasionally gets stuck in the "Stopping" or "Starting" state, click over to the Extras tab and check the corresponding options.Ĭlick the Save button. This will ensure that MongoDB comes up "clean" if it ever crashes and inadvertently leaves the lock file behind. Run this command prior to restarting the service section at the bottom of the window. To protect yourself against those situations, create a batch file that removes the mongodb.lock file from the Occasionally MongoDB doesn't restart properly after a power failure, system crash or other unexpected shutdown (see bug SERVER-4373 for the details). You will notice a green circle on the left if the MongoDB service is already running, as was the case on our server. In the Service to protect field, choose the MongoDB windows service, called Mongo DB. Select Protector > Add to open the Add Protector window:
#HOW TO AUTOMATICALLY START MONGODB WINDOWS INSTALL#
To protect MongoDB with Service Protector:Ĭonfigure MongoDB as a Windows Service, if necessary.ĭownload and install Service Protector, if necessary.
0 kommentar(er)
