The only up alerts I generate are for back up after down conditions, but yes, it was failing to send an up notice via SMTP or SMS for any check that went down and came back up. I applied the current beta (6.1.2223) this morning and this is what my log shows since I restarted: "Tuesday, March 11, 2008 7:49:41 AM Woodstone Servers Alive version 6.1.2223.3 Tuesday, March 11, 2008 7:49:41 AM Running on Microsoft Windows XP Professional (2600) Service Pack 2 (32 bits) Tuesday, March 11, 2008 7:49:41 AM Oracle Core40.dll library available Tuesday, March 11, 2008 7:49:41 AM No SQL libs found! Tuesday, March 11, 2008 7:49:41 AM Netware library's not available Tuesday, March 11, 2008 7:49:41 AM DUN installed and available for SA Tuesday, March 11, 2008 7:50:03 AM Check cycle starts ( 1- 1) Tuesday, March 11, 2008 7:53:49 AM TELNET server: connection from 10.10.62.31 logged on with FULL rights Tuesday, March 11, 2008 7:55:53 AM Check cycle starts ( 2- 2) Tuesday, March 11, 2008 7:57:01 AM TELNET server: connection from 10.10.62.218 logged on with FULL rights Tuesday, March 11, 2008 8:00:36 AM Check cycle starts ( 3- 3) Tuesday, March 11, 2008 8:03:19 AM Check cycle starts ( 4- 4) Tuesday, March 11, 2008 8:06:02 AM C! heck cycle starts ( 5- 5) Tuesday, March 11, 2008 8:08:45 AM Check cycle starts ( 6- 6)"
I have not tested a down/up yet but will do so soon. I also run the machine with SA with an external monitor and the display console up. Since the update I notice that it does not flash orange at the end of the check list - it would do that since the last update, but then reset to normal green/up display when the second knock check was complete. I noticed in the logs prior to this update I was getting "...failed due to a successrate of only 0%" on ping checks, even though the devices where up, and would never alert down on the screen or via SMTP, assumably because second knock caught em. I will keep you posted, thanks for the replies on all this Dirk! Chad >>> "Dirk Bulinckx" <[EMAIL PROTECTED]> 3/10/2008 11:25 PM >>> Are you not getting the up alerts on the entries that got a down with the below mentioned error or on all? As for the problem with the below mentioned error, as said in my previous answer we addd extra logging (requested by the developper of the ping component) in order to understand why this error happens and in order to fix it. UNtil now we did not get any reports back of the error WITH the extra logging. Once we have that we should be able to get a step further. Dirk Bulinckx. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu 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.
