For the process check we have to "listen" to the api call and if that says "timeout", then it's timeout. However if you set a lower timeout then the one that the api 'thinks' it should use, then we do respect the time and can give a timeout before the api does.
Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow Sent: Tuesday, April 03, 2007 3:06 PM To: Servers Alive Discussion List Subject: Re: [SA-list] Windows NT Process Error One note and maybe Dirk can confirm but I believe that in V6 it repects the timeout value set in SA and prior to that for some reason it didn't. Increasing the timeout in SA may help. However you may be getting a timeout from the API call which was discussed earlier in this thread. There is not much Dirk can do there (or at least that is what he says :-). Jason Passow Mississippi Welders Supply [EMAIL PROTECTED] ph: (507) 494-5178 fax: (507) 454-8104 "If you do everything right, nobody will realize you've done anything at all." Neira, Jose wrote: > I've 2 SA servers (1 for QA and 1 for Prod) the QA one is able to get the status of the processes and the Prod one is timing out (different results while monitoring the same server). My guess is that there should be something different between the QA and Prod SA servers, that is causing the problem. > > Any ideas where to look at (other than the API)? > > Note..* I upgraded QA from version 4 to 6 one week ago and everything worked fine. Last weekend Prod was upgraded. Same rule was working fine for years in v4. > > Thanks in advance, > > José A. Neira > Bechtel Corporation > (602) 368-0141 > > > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Dirk Bulinckx > Sent: Thursday, March 15, 2007 8:00 AM > To: Servers Alive Discussion List > Subject: RE: [SA-list] Windows NT Process Error > > 1) We use an api on the system running Servers Alive and that one > gives us that timeout. > 2) don't think that there is currently a possible work around - once > the windows agents is released then that could be a > solution/workaround > > > Dirk Bulinckx. > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Chris Mang > Sent: Thursday, March 15, 2007 3:36 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] Windows NT Process Error > > Two more questions: > > 1) Is that the API on the Servers Alive server reporting the timeout, > or the API on the server being checked? > > 2) Is there a workaround? I ask, because I have two servers where I > can't check any processes, because I can never see a list of > processes, and another that will occasionally report the 1460 error on the store.exe process. > > Thanks, > > Chris Mang>> > JDA Software Group, Inc. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Dirk Bulinckx > Sent: Wednesday, March 14, 2007 4:50 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] Windows NT Process Error > > In some cases the api call returns quicker then the given timeout and > says "timeout", in that case we do show a timeout (even if that > happens before the given timeout). > > > Dirk Bulinckx. > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Chris Mang > Sent: Wednesday, March 14, 2007 10:46 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] Windows NT Process Error > > I've regularly had a similar situation with checking STORE.EXE on > various Exchange servers. > > How do you increase the timeout? Changing the timeout on the check > itself has no effect. If I go to the Check tab, and click the button > to list the available processes, it times out after 8 seconds or so and returns with the ERR: > 1460 > dialog. However, the timeout setting on the check is set to 100 seconds. > > Thanks, > > Chris Mang>> > JDA Software Group, Inc. > > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Dirk Bulinckx > Sent: Monday, March 12, 2007 12:15 PM > To: Servers Alive Discussion List > Subject: RE: [SA-list] Windows NT Process Error > > The 1460 error is a timeout error, so if the system isn't responding > correctly within the given timeout then you get that error. > > > Dirk Bulinckx. > -----Original Message----- > From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Neil Hayes-Webster > Sent: Monday, March 12, 2007 5:26 PM > To: Servers Alive Discussion List > Subject: [SA-list] Windows NT Process Error > > Hiya > We have an application called Guinevere (NT Process : guinevere) > which is regularly being reported as DOWN with ERR: 1460 - its set to > alert if there is less than one instance running. I have extended the > timeout but we are still getting the errors. The process is still > running without fault and is not restarting which we can see from the application stats. > > Do you have any ideas? > > There is nothing in either application or system event logs around the > time of the failure. > > Win Server 2003 SP1 > 2GB RAM > Dual core Dual Xeon 3.2GHz > > > Neil Hayes-Webster > IS Network Support > 01935 404567 > Ex 4569 > www.ssh.co.uk > > . Gold Award for Excellence Winner - Housing Corporation . > 'Demonstration > status' gas servicing partnering contract from > the Housing Forum Constructing Excellence Programme . First RSL to > use > Space4 > . Worcester Bosch Environment 2010 Award Winner . Excellence Award by > EROSH, National Consortium for Sheltered Housing . 'Code of Practice' > Award - Centre for Sheltered Housing Studies . Commended by National > Change Agent for Innovation in Procurement of Capital Works > > Visit our website at www.ssh.co.uk > ______________________________________________________________________ > _ > Disclaimer: This email is intended for the use of the addressee only > and may contain confidential information. If you receive this message > in error please let us know by using the reply facility immediately. > Attachments to this email may contain software viruses, we have taken > every reasonable precaution to minimise this risk but we advise that > any attachments are virus checked before they are opened. > Any views or opinions expressed in this email are not necessarily > those of the company. > ______________________________________________________________________ > _ > > South Somerset Homes Limited is registered in England No. 3488535 Charity No: > 1108793 > Registered Office: South Somerset House, Alvington, Yeovil Somerset BA22 8WN. > > Thank you for your cooperation. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] If you use auto-responders (like out-of-the-office > messages), then make sure that they are not send to the list nor to > the individual members of the list that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] If you use auto-responders (like out-of-the-office > messages), then make sure that they are not send to the list nor to > the individual members of the list that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] If you use auto-responders (like out-of-the-office > messages), then make sure that they are not send to the list nor to > the individual members of the list that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] If you use auto-responders (like out-of-the-office > messages), then make sure that they are not send to the list nor to > the individual members of the list that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] If you use auto-responders (like out-of-the-office > messages), then make sure that they are not send to the list nor to > the individual members of the list that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. > > To unsubscribe send a message with UNSUBSCRIBE as subject to > [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. > > > To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
