check_ssh to find "corrupt" keys thatneedregeneration?

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Marc Powell
> Sent: Thursday, February 21, 2008 8:51 AM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] check_ssh to find "corrupt" keys
> thatneedregeneration?
> 
> 
> 
> > -----Original Message-----
> > From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-
> > bounces at lists.sourceforge.net] On Behalf Of Roger
> > Sent: Thursday, February 21, 2008 8:07 AM
> > To: nagios-users at lists.sourceforge.net
> > Subject: Re: [Nagios-users] check_ssh to find "corrupt" keys that
> > needregeneration?
> >
> > On 2/20/08, Roger <Roger at nagioswiki.com> wrote:
> >
> > 	I have ~300 Foundry routers, and periodically something (not
> sure
> > what) "happens" that resets some sort of key that prevents me from
> SSH'ing
> > in with a tool like PuTTY and Teraterm (have not tried this from a
> Linux
> > ssh box).
> 
> What is the specific error and symptoms that you're seeing? "resets
some
> sort of key" isn't very useful in helping you figure out how to check
> for it. I've never seen anything like what you're describing outside
of
> the host key changing. check_ssh should detect that and at least WARN.

Just a redaction. I was _really_ thinking of check_by_ssh here but that
wouldn't work in your case. check_ssh does not verify host keys.

More info about the problem is still useful though.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null