[Nagiosplug-devel] check_udp doesn't work on nagios 1.1

[Jeremy T. Bouse]

Paraic,

	If you would take a look at the bug report #731467 (when the
SourceForge site comes back from maintenance) you would find that the
check_udp and check_udp2 are both reported as having problems and appear
to need a possible total re-write to get them functioning properly as
UDP packets and services do not respond in the same manner as TCP
packets due to the nature of UDP packets not using the handshaking to
establish a connection as TCP does...

	Regards,
	Jeremy

On Wed, Jul 09, 2003 at 01:50:01PM +0100, Paraic OCeallaigh wrote:
> Hi
> it looks like check_udp is broken in particular for the port I'm checking -
> syslog, port 514.
> Here's the output regardless of what host info or port number I use:
> 
> nagios:/usr/local/nagios/etc# ../libexec/check_udp -H 172.16.3.10 -p 514
> Host name was not supplied
> Usage: check_udp -H <host_address> [-p port] [-w warn_time] [-c crit_time]
>          [-e expect] [-s send] [-t to_sec] [-v]
> 
> nagios:/usr/local/nagios/etc# ../libexec/check_udp -H 172.16.1.10 -p 37 -v
> Host name was not supplied
> Usage: check_udp -H <host_address> [-p port] [-w warn_time] [-c crit_time]
>          [-e expect] [-s send] [-t to_sec] [-v]
> 
> This seems to be the only feedback I can generate from the check_udp command
> regardless what I put into it.
> 
> Let me know if theres a fix or if its scheduled for the next release.
> 
> Great job with Nagios in general though...cracking app - esp the SSL
> implementation in nrpe 2.0. Nice one.
> 
> Rgds,
> Paraic
> www.host.ie
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps
> _______________________________________________
> Nagiosplug-devel mailing list
> Nagiosplug-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null