Mark suggestion was to add that as a new feature….
Dirk Bulinckx. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Ray VanVelsen Sent: Friday, May 01, 2009 2:16 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check This is helpful. It seems like in normal conditions the remote system would respond within 300 seconds. That is 5 minutes. Therefore it seems like your second cases might be what is happening. The remote OS is busy and discards the request. Mark Perry had a suggestion: set the number of retries and the percentage of checks that have to be successful, just like on a Ping check. I don't see those options on the process check; I am running SA version 6.1.2204. Are those fields available in a newer version for the Process Check? If so, I could set it to something like: Timeout: 10 s Retries: 10 Percentage: 10% I think when this remote system is processing received phone call data, it might be discarding Servers' Alive's check request. If I could give it 10 chances to get one response instead of 1 chance to get one, we might have better success. Thanks Dirk. Ray VanVelsen Manager of Information Technology Services Porter Hills Retirement Communities & Services -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Sent: Thursday, April 30, 2009 7:36 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check No Servers Alive sends a request to the remote system with a timeout value of 300 seconds. You can get 2 cases: * within those 300 seconds you do not get the result from the remote system * the OS decides before this timeout that it's no use to wait longer Dirk Bulinckx. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Ray VanVelsen Sent: Thursday, April 30, 2009 9:31 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check So if I understand correctly, Servers Alive checked for 300 seconds and during that whole time it never once retrieved a list of running processes? Ray VanVelsen Manager of Information Technology Services Porter Hills Retirement Communities & Services -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Sent: Thursday, April 30, 2009 1:01 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check No it means that it didn't get a list of running processes during the timeout. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Ray VanVelsen Sent: Wednesday, April 29, 2009 11:21 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check If you are referring to the Timeout field on the Check page, I have set that time out to the maximum - 300. I also have Second Knock enabled. Even with these settings, Servers Alive sees the process as down quite often. Does the 1460 error mean that it did not see the process as up during the length of the timeout? Ray VanVelsen Manager of Information Technology Services Porter Hills Retirement Communities & Services -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Sent: Tuesday, April 28, 2009 5:06 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check You can set you own timeout when you create/edit the entry. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Ray VanVelsen Sent: Tuesday, April 28, 2009 10:51 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check How long is the timeout? Is it adjustable? Ray VanVelsen Manager of Information Technology Services Porter Hills Retirement Communities & Services -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Sent: Tuesday, April 28, 2009 4:41 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check 1460 is a timeout error Dirk Bulinckx. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Ray VanVelsen Sent: Tuesday, April 28, 2009 7:46 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check Dirk Here is the log entries regarding the process check failing. I stripped the date and time info off each line. Call Accounting ERR process check: ERR: 1460 PROCESS took 3000 ms(38) Call Accounting NT Process check of UCServer on viwks-callbox2 failed Thanks. Ray VanVelsen Manager of Information Technology Services Porter Hills Retirement Communities & Services -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Sent: Saturday, April 25, 2009 10:45 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Using SA NT process check And when it tells you it's not running (while it's actualy running) what does it give as reason for the down? Dirk Bulinckx. From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Ray VanVelsen Sent: Saturday, April 25, 2009 3:34 PM To: Servers Alive Discussion List Subject: [SA-list] Using SA NT process check Hi We are using Server Alive's NT process check against a third party NT process that runs on an XP SP3 box. SA often reports that the process is not running. However, when we check the process, it is up. What suggestions do people have regarding checking a process? Our SA box is remote from the box running the process. What timeouts come into play when SA checks a process? We are running SA 6.1.2204 on XP SP3. Thanks for your help. Ray VanVelsen Manager of Information Technology Services Porter Hills Retirement Communities & Services To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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 salive@woodstone.nu 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.
