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:
Auto start mongodb windows using service protector install#
Consult the Service Protector FAQ for answers to commonly asked questions and troubleshooting tips.To protect MongoDB with Service Protector:Ĭonfigure MongoDB as a Windows Service, if necessary.ĭownload and install Service Protector, if necessary.Trouble protecting the VNC Windows Service? We encourage you to edit VNC in Service Protector and check out the many other settings that may be appropriate for your environment.įor example, send an email when the service stops for any reason, restart the service at a safe time every day, and much more. That's it! Next time your computer boots, RealVNC will start automatically and Service Protector will constantly watch the service to quickly restart it if it stops for any reason. Click on the shield to see details on protection: In a few seconds the shield icon in the "Protection" column will go to green to indicate that VNC is being monitored by Service Protector.
To start protection, choose Protector > Start "VNC Server" (or click on the shield-play toolbar button). The service is probably already running but it is not yet being protected by Service Protector, as shown below.Ĭlick on the green circle to see some technical details on the VNC service (which has been up for more than 4 days on our server): In a few seconds, an entry for VNC Server will appear in the Service Protector window. You will notice a green circle on the left if the service is already running, as was the case on our server.Ĭlick the Save button. On the General tab, in the Service to protect field, choose the VNC windows service, called VNC Server.
To protect the RealVNC Windows Service with Service Protector:ĭownload install, and configure RealVNC, if necessary.
0 kommentar(er)
