Indeed all NT related checks (diskspace/service/process/perfmon) will act differently when running as service or as application, and this due to the authentication. Also the fact that a real users is logged on localy to the system and have active connection will also influence the checking. Not due to Servers Alive but due to how the OS reacts to that. Most of the time the logfile will show an errorcode and this will explain the WHY of the problem.
As for the URL checks, you're right about the proxy and the authentication. The caching of the proxy can also be an issue. Within the request send by Servers Alive towards the remote webserver (via proxy or not) we request not to use caching. Unfortunatly not all proxy's are reacting correctly to this request and just ignore that request. dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Deadman, Phil Sent: Thu Mar 20 2:16 PM To: '[EMAIL PROTECTED]' Subject: RE: [SA-list] SA isn't reliable Hi David, Just a couple of thoughts on this... They might not help! Testing NT services in my experience can be a bit hit or miss, depending on the service in question. I tried checking the apache service, but it would frequently fail to serve pages without actually stopping the service. As for URL checks, make sure your connection is not going through a proxy server or anything else that might cache pages. I've always found that SA itself is consistent - the only real difference between running as a service or interactively is the "user" SA is actually logged on as. Things that happen differently when SA is running as a service are usually because of the rights or settings for the respective "user". Cheers, Phil. -----Original Message----- From: David Lewis-Waller [mailto:[EMAIL PROTECTED] Sent: 20 March 2003 09:10 To: [EMAIL PROTECTED] Subject: RE: [SA-list] SA isn't reliable Further to my last. We have two SA's running, one on a remote server and one locally. The local machine does URL checks whilst the server machine installation performs service checks. Neither machine detected this stoppage we had which lasted at least 8 hours. Both running as a service only when run manually did they detect the failure. Why? Also, the logging to SQL data is now recording NULLS in all fields except 'host'. David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Lewis-Waller Sent: 20 March 2003 08:59 To: [EMAIL PROTECTED] Subject: [SA-list] SA isn't reliable Why is SA unreliable? We have found that SA doesn't perform checks reliably when running as a servive. We had the w3svc service stop this morning and SA didn't perform an IIS restart as part of its routine. However, when SA is launched after logging on then it restarted the service correctly. We've had this happen quite a few times and we feel that SA isn't the tool for the job if we can't rely on it. David To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive **************************************************************************** ******************* This E-mail and any files transmitted with it is intended for the use of the addressee only and may contain confidential information. If you are not the intended recipient you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately and delete this e-mail. The views and opinions expressed in this e-mail message are the author's own and may not reflect the views and opinions of Signet Group plc or any of its subsidiaries. **************************************************************************** ******************* To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
