A while ago I wrote a service monitor to watch for service crashes, it wasn’t the greatest as it just checked the service status at a defined interval and restarted it if it wasn’t running.
This was not the best method ans since I lost the source, I decided to find a better way.
Basically if a service is shut down cleanly it will go into a stopping state first.
If it jumped straight to stopped then it crashed.
This allows us to monitor the service and not interfere with things like updates or legitimate reasons for stopping the service.
4 Comments
Maybe a compiled (exe) version is available for download ?
Hi, there should be a compiled version in the bin\debug folder.
Hi Jake,
Just curious, this specifically excludes agents that have stopped for updates? Our most regular problem agents are exactly that. Agents that have stopped for updates and never started again. I'm wondering if we need to add an extra step in and have it detect when an agent has been stopped for more than X days as there is no reason it should stay stopped for any length of time.
LN support are aware of that one but I've had to manually start over 25 workstations for one site this morning hence revisiting it!
Hey Colin,
Yes, this would exclude if an update was applied.
It's important not to start it up again while the update is still in process as to not interfere.
To be honest, this shouldn't have to exist. If you're finding that you are wasting too much time fixing your RMM system then maybe you need to look at an alternative.
We should be servicing out clients, not dealing with other vendors issues.
Leave A Comment