[cisco-voip] FW: [RTMT-ALERT-CMPUB-Cluster] SyslogSeverityMatchFound

[Paul]

You'll likely get a LOT more information trying to manually connect to the specified SSHd using 'ssh -v' to get a lot more diagnostic information from the client as well as the SSHd. Not sure it'll give you the information you need but more information in this case is much better than less.




________________________________
From: Ryan Ratliff <rratliff at cisco..com>
To: Paul <asobihoudai at yahoo.com>; "Voll, Scott" <Scott.Voll at wesd.org>; cisco-voip at puck.nether.net
Sent: Monday, April 13, 2009 12:01:28 PM
Subject: RE: [cisco-voip] FW: [RTMT-ALERT-CMPUB-Cluster] SyslogSeverityMatchFound

 
I believe that’s just an indication that an ssh session was shut
down by the client without propertly terminating the client.   I think Wes was
working on reproducing it here.
 
-Ryan
 
From:cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On
Behalf Of Paul
Sent: Monday, April 13, 2009 11:01 AM
To: Voll, Scott; Cisco VoIP <(cisco-voip at puck.nether.net)>
Subject: Re: [cisco-voip] FW: [RTMT-ALERT-CMPUB-Cluster]
SyslogSeverityMatchFound
 
It *sounds* like your ssh daemon is having authentication
issues. Since this is a locked down server, I'm not sure how you'd fix that
though.
 

________________________________
 
From:"Voll, Scott"
<Scott.Voll at wesd.org>
To: "Cisco VoIP (cisco-voip at puck.nether.net)"
<cisco-voip at puck.nether.net>
Sent: Monday, April 13, 2009 10:54:18 AM
Subject: [cisco-voip] FW: [RTMT-ALERT-CMPUB-Cluster]
SyslogSeverityMatchFound
What does this mean?  I couldn’t find anything on a
google search.  CM 6.1..2
 
Thanks
 
Scott
 

Subject: [RTMT-ALERT-CMPUB-Cluster] SyslogSeverityMatchFound
 
At
Sun Apr 12 20:10:43 PDT 2009 on node 10.x..y.z,
the following SyslogSeverityMatchFound events generated: SeverityMatch -
Critical sshd[23723]: fatal: Write failed: Broken pipe 


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090413/bf232e72/attachment.html>