[Nagiosplug-help] Problem with TCP-Sessions via check_smtp or check_ssh

[sp2148421]

Hallo Holger,
Thanks, the smtp-patch worked.

But in my opinion the source problem of the (tcp-based)-checks is, that they didn't wait for [FIN,ACK] from Server-Site after
sending themself a [FIN,ACK]. Maye they script is been killed before the Session was closed by the remote-site or the tcp-timeout
was reached.
See connection termination on http://en.wikipedia.org/wiki/Transmission_Control_Protocol

Thanks
Dieter

Holger Weiss wrote:
> * "Dieter Hendricks (web.de)" <dieter.hendricks at web.de> [2007-07-31 08:13]:
>> I have a problem with check_smtp and check_ssh from the Nagios-Plugins.
>> After the session was closed [FIN,ACK] by the NagiosMonitor it seems the
>> Machine didn´t wait for an [ACK] by the SMTPServer instead it responses
>> all packets from the SMTPServer with an [RST]. This [RST]s logged by the
>> Firewall as multiply Session-Resets and fill the LOG-File.
> 
> The problem is that check_smtp doesn't read the server's response to the
> SMTP QUIT command.  The attached patch against check_smtp.c should fix
> that; will be included with the next release.  For check_ssh, it's not
> that easy to fix, sorry.
> 
> Thanks for your report, Holger
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null