Currently my installation is configured to monitor the uptime of a WMI service. If the service is stopped it is configured to start it.
I've noticed prtg starts the service if it isn't when it notices that it is down. If it manages to poll it again to see that it's up before the service stops, it will restart it without a problem.
If the service stops, after prtg started it; prtg doesn't see that the service was running, it will not attempt to start it again. It will fall back on the notification settings configured and will send an email to the admins, etc.
Is there a way to configure the number of successive starts it attempts before signaling an error?
Article Comments
Thanks for the quick reply, Greg!
Are there any work-arounds that I can try using PRTG?
Nov, 2013 - Permalink
The best way to work around this would be to write another script that restarts the service and then use that for a notification.
You could have the batch script set up with a notification that executes a program then set up a state trigger that would continue to retry the service while the sensor is down.
Nov, 2013 - Permalink
Unfortunately this isn't possible with this sensor. Once PRTG sees that the service is down it will only try and restart it once since most services that will not start the first time will not start on the second attempt.
Nov, 2013 - Permalink