The entry in SA shows it as being up when I check it after getting an alert. About 3 minutes later I get a message saying that it is up even though it never showed that it was down. It doesn’t require me to do anything to get it back up.
From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of Dirk Bulinckx Sent: Friday, March 18, 2011 3:16 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Error invalid username or password When you get the "error", you mean that SA does show the entry in the interface as being UP, and still sends a mail for a down? When you get the problem, does it solve itself or do you need to do "something" in order to get it fixed? dirk From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of Riki Oshita Sent: Friday, March 18, 2011 10:46 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Error invalid username or password I am assisting Courtney Kibbe with this. The version of SA is Enterprise 6.2.2279 and the OS that the remote agent is running on is Windows Server 2008 Standard. From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of Dirk Bulinckx Sent: Friday, March 18, 2011 2:31 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Error invalid username or password What version of SA are you using? On what OS is the remote Agent running? From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of Courtney Kibbe Sent: Friday, March 18, 2011 10:16 PM To: Servers Alive Discussion List Subject: [SA-list] Error invalid username or password We installed the remote agent on a server and it will check about three other servers. Occasionally it will send out an e-mail with an error for each server it is checking. The error is “ERROR: Invalid username or password reported by server, or bad private key.” The SA console does not show the servers are down. If the username or password were really invalid wouldn’t the console show the serves are down? What can be done to resolve this error? 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.
