OnDemand Users Group

Support Forums => CMOD for Multiplatforms => Topic started by: bbeach on September 10, 2020, 03:09:24 PM

Title: Monitoring CMOD Windows Service using PowerShell or other Scripting?
Post by: bbeach on September 10, 2020, 03:09:24 PM
I have a client with CMOD on Windows using a remote Clustered SQL Server.  For non-Prod environments, it is not unusual for the SQL server to be restarted without warning. Whenever this happens, the CMOD service stops working and requires a restart.  CMOD is unusual in that if the DB connection breaks the process shuts down, rather than managing it with an error at login time - until the DB is available again.  Has anyone devised a clever way to monitor for this occurrence and automatically restart using OOTB Windows capabilities, without requiring a purchased 3rd party monitoring tool that leverages SNMP alerts or something like that which would be overkill?

Thank you for any feedback.
Title: Re: Monitoring CMOD Windows Service using PowerShell or other Scripting?
Post by: Justin Derrick on September 10, 2020, 03:30:33 PM
I've never used it on windows, but maybe the CMOD arslog logging exit could be used to detect a database error, then check on CMOD after a short delay and restart it?

-JD.