Does it do this always? 

Is the alert set to STOP first and then start? 

 

(from a code point of view the service alert is exactly the same in v6 as it's 
in v6.1) 

 

Dirk Bulinckx. 

From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of 
Smith, Michael
Sent: Sunday, June 08, 2008 3:41 AM
To: Servers Alive Discussion List
Subject: [SA-list] ServersAlive Hanging on Service Restart Process 

 

I recently upgraded to 6.1.2204 and have run into some problems. I've noticed 
that some of my checks that attempt to restart a Service if it detects the 
service is non-functional are not working properly. When ServersAlive tries to 
restart the service on the remote machine, it hangs. Strangely, the service on 
the remote machine does Stop however ServersAlive doesn't Restart it. The 
Status bar indicates that it is still Checking the entry, but it's just stopped 
there. The last check was at 8:37pm even though the cycle is set for every 5 
minutes. The security is clearly correct because it's able to stop the service 
on the remote box, just not restart it. 


 


Once this happens I've tried manually stopping the ServersAlive service to get 
it moving, but the ServersAlive Service itself will not stop properly. The 
Services manager shows the status as "Stopping". I then have no choice but to 
reboot the server running ServersAlive. 


 


The last entry in the log file is: 

Saturday, June 07, 2008 9:33:29 PM Check cycle starts ( 29- 5)
Saturday, June 07, 2008 9:33:29 PM KT-HRIS1 Service Activity
Saturday, June 07, 2008 9:33:29 PM External COM check started (C00000003,2,-1)
Saturday, June 07, 2008 9:33:29 PM External COM check (C00000003,2): 
Saturday, June 07, 2008 9:33:29 PM EXTERNALCOM took 102 ms(2)
Saturday, June 07, 2008 9:33:29 PM INFO: alerting COMD
Saturday, June 07, 2008 9:33:29 PM vbStopService ktsvcprocess:  1
Saturday, June 07, 2008 9:33:29 PM GetServiceStat 

I am positive that this used to work prior to the upgrade to 6.1. 


 


Mike 



To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected]
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 

To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
[email protected]
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 

Reply via email to