[Nagiosplug-help] check_tcp bug in nagios v1.4.11
Fontanilla, John (Gexpro, consultant)
John.Fontanilla at Gexpro.com
Thu Oct 23 22:56:02 CEST 2008
Thanks for replying. I was checking "check_tcp" from the client side
instead of the server side. I didn't think of checking the exit code.
I contacted our Nagios (Groundwork) admin and he said he can make a
"server-side plugin" (not sure if this is the correct term) that
does "check_tcp -H 220.127.116.11 -p 1234" and if 18.104.22.168 doesn't listen at
port 1234, we get a "CRITICAL" alert on the Nagios server.
From: Matthias Eble [mailto:PsychoTrahe at gmx.de]
Sent: Thursday, October 23, 2008 4:51 PM
To: Fontanilla, John (Gexpro, consultant)
Cc: nagiosplug-help at lists.sourceforge.net
Subject: Re: [Nagiosplug-help] check_tcp bug in nagios v1.4.11
On Thu, 2008-10-23 at 13:00 -0400, Fontanilla, John (Gexpro, consultant)
> We use check_tcp v.1.4.11 and it appears to still have a bug...
# check_tcp -H 127.0.0.1 -p 4444; echo $?
Why should this be a bug? The plugin returns critical, it simply doesn't
print the status to stdout. The statustext in the output can be
considered as noise anyway, since , nagios has appropriate macros, if
you want a severity string in your notifications, etc.
More information about the Help