I don't get that OpenSCManager error during the check configuration. Authentication problem: I am not sure because it works fine some times. In reference to authentication issues I am running SA as a Service using an account that belongs to the administrators group in all the monitored servers but I was thinking that there could be a delay problem when that account is validated against the domain controller.
SAlive Beta installation download: I will install this version as advised by Dirk in order to get more details in the error log. Jose. -----Original Message----- From: Kevin Stone [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 8:52 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Monitoring NT service: w3svc Usually when you attempt the open the service listing when setting up a check you will get an OpenSCManager error if the authentication credentials are not correct. That's what led to me guess that there was an authentication problem. -Kevin > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx > Sent: Wednesday, April 02, 2003 11:57 PM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > Problem is that the > Wednesday, March 05, 2003 8:55:30 PM ERR: Getservice status - > > OpenSCManager > isn't showing any errorcode :-( > And that's a "problem" of SA. > If you retest with > http://www.woodstone.nu/soft/beta/salive4.exe you'll get an > errorcode (and description with it), this will show more info > on why it fails > > dirk. > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Kevin Stone > Sent: Thu Apr 03 4:08 AM > To: [EMAIL PROTECTED] > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > I'm a little confused, you seem to be mixing issues. The > original problem was false alarms from the w3svc service > check. From the log entry that was included it looks like an > authentication problem is causing the check to fail(Dirk may > have more detail or tell me I'm way off base). Correcting > this is the first step. > > In the last message you talked about dependency issues, to > resolve those you can take a couple of routes. The way it is > set up now as long as the URL is running it assumes the w3svc > service(s) is running. Since this is a load-balanced > environment this may not accurately show when an individual > w3svc service is down. > > I would probably then remove the dependency of the w3c > services from the URL check and have them checked > independently. The reality is they are not dependent on one > another in your situation. > > You can also change the dependency from "Down" to "Up" so > that it always checks all three w3c services. Basically if > the URL is up check all three w3svc services to make sure > they are running. > > The last way you could try to resolve this would be to start at the > bottom(ping) and test up the stack - ping, services, url, in > the reverse of what you do now. Since a check can only be > dependent on one other you might want to make the service > checks AND URL check dependent on the ping check. > > It all depends on your environment and what your alerting > requirements are. With some testing you should be able to > find a combo that meets you needs. > > > -Kevin > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > > Behalf Of Navarrete, Jose > > Sent: Wednesday, April 02, 2003 4:04 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > > > I was advice on the list to check primarily the web page then the > > w3svc. The problem is that the web page is load balanced > between three > > DMZ servers; the page is always up no matter one of the > three servers > > is down. > > > > This is the log I sent that time > > > > Wednesday, March 05, 2003 8:54:45 PM NTService check of w3svc on > > SERVER18 failed Wednesday, March 05, 2003 8:54:45 PM Sending email > > message (SERVER18(DMZ) is > > DOWN) > > Wednesday, March 05, 2003 8:55:30 PM ERR: Getservice status - > > OpenSCManager > > - 0 > > > > > > > > > > -----Original Message----- > > From: Kevin Stone [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, April 02, 2003 1:47 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > When Servers Alive is running as a service it runs as the system > > account by default and this has been reliable in my experience. > > > > When checking services you can have it authenticate with > any account > > you choose for local or remote systems., this is specified in the > > check itself. Normally for local services you do not need > to specify > > an account. In my case I use the format domain\account because my > > Servers Alive system is not a domain member and I check 60 remote > > servers. > > > > -Kevin > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > On Behalf Of Navarrete, Jose > > > Sent: Wednesday, April 02, 2003 3:36 PM > > > To: '[EMAIL PROTECTED]' > > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > > > > > > Which account is used to get the Services information > connecting to > > > the Remote Service Manager...is it the SYSTEM account Will it > > > improve if I run Servers Alive with an account that has the same > > > username and password as the local administrator account > in all the > > > monitored servers. Some days these false alerts are a > true pain. The > > > > alert e-mail sent to the Data center generates page calls > to several > > > > admin people who started to complain that the product is not > > > consistent. > > > > > > Jose. > > > > > > > > > > > > -----Original Message----- > > > From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] > > > Sent: Friday, March 07, 2003 9:28 AM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > > > The service is not down, it's just not possible to check > it at that > > > time, and that is already a problem. So no you should not stop > > > monitoring services. > > > > > > > > > dirk. > > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > > Behalf Of Navarrete, Jose > > > Sent: Fri Mar 07 4:43 PM > > > To: '[EMAIL PROTECTED]' > > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > > > > > > That's true Dirk, I have verified older logs and they are > about the > > > same with any Service that was monitored (of course it doesn't > > > happen all times). So the problem is not necessarily > that a Service > > > > is DOWN, as a matter of fact all the alerts pertaining a Service > > > were "false" in my case. Should I just stop checking services? Is > > > there any further advice? > > > > > > > > > > > > -----Original Message----- > > > From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] > > > Sent: Friday, March 07, 2003 12:01 AM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > > > Most likely the problem is that it can't connect to the remote > > > service manager to get the list of services. Increasing > the timeout > > > won't help. Most Nebios calls (those are part of the OS > and used for > > > service/diskspace/... checks) don't accept timeout's and will > > > timeout when they want to timeout. Personaly I find this a big > > > issues within the Netbios calls that MS "provides" to > programmers. > > > (and apparently they realy don't think timeout's are usefull since > > > in the WMI interface (also programmer calls provided by the > > > OS) they again didn't provide any timeouts). > > > > > > > > > > > > dirk. > > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > > Behalf Of Navarrete, Jose > > > Sent: Fri Mar 07 3:53 AM > > > To: '[EMAIL PROTECTED]' > > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > > > > > > Thanks to all of you for your support; this is the Log: > > > > > > Wednesday, March 05, 2003 8:54:45 PM NTService check of w3svc on > > > SERVER18 failed Wednesday, March 05, 2003 8:54:45 PM > Sending email > > > message (SERVER18(DMZ) is > > > DOWN) > > > Wednesday, March 05, 2003 8:55:30 PM ERR: Getservice status - > > > OpenSCManager > > > - 0 > > > > > > Jose. > > > > > > -----Original Message----- > > > From: Dirk Bulinckx [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, March 06, 2003 4:37 PM > > > To: [EMAIL PROTECTED] > > > Subject: RE: [SA-list] Monitoring NT service: w3svc > > > > > > When you get the false downs, what is in the log (same > question as > > > always, please check the logfile and give the messages > that are in > > > the log) > > > > > > > > > dirk. > > > > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > > Behalf Of Navarrete, Jose > > > Sent: Thu Mar 06 11:36 PM > > > To: Salive (E-mail) > > > Subject: [SA-list] Monitoring NT service: w3svc > > > > > > > > > Hello, > > > I am having problems monitoring the W3SVC service in > three very busy > > > > IIS servers. Several times the Alert generates DOWN messages even > > > thou the Server is running fine. I had increased the > timeout value > > > to 4 seconds to prevent the "false" alerts but I am not > sure if it > > > is a good value (maybe it is too > > > high) to have a true reading for the W3SVC service. > > > > > > Any help is appreciated, > > > Jose. > > > > > > To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
