What I do is have the primary SA output an HTML page containing just enough code to be 
included in an ASP page with the lastcyclestart time (and other variables) after each 
cycle. Then I have an ASP page that calculates the datediff between the SA output and 
Now(). If good, then the ASP page writes "OK" to the browser in HTML, and "ERROR" if 
the datediff is too old. Then the secondary SA does a HTML check looking for the 
contents of my asp page. If it contains "ERROR" then I know that the primary SA hasn't 
updated recently. Because SA writes the HTML output as a last step, this is a 
reasonably good check that all is well. This is also extremely good for checking for 
horrendously long cycles, that while technically ARE running, they are just taking too 
long.

If you're interested, I can zip up the files and send them to you offlist.

Michael Shook
Technical Analyst
Saddle Creek Corporation
723 Joe Tamplin Industrial Blvd
Macon GA  31217
478 742 8740 ext. 105 (work)
478 256 9318 (mobile)
478 742 7917 (fax)
[EMAIL PROTECTED] 
http://www.saddlecrk.com

>>> [EMAIL PROTECTED] 06/03/04 11:15AM >>>
I am looking for a way to have one SA box check another SA box to ensure
that SA is running. I looked at SAIsAlive but I really want something to
send an Alarm to show that SA is down. I thought about checking the
service but thought that if it was hung it may show as running. I was
wondering if there was a way to have SA look at the log file and note
that the date/time has changed or really any creative idea anyone has
would be appreciated.

---

[This E-mail scanned for viruses by Declude Virus]

To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive

Reply via email to