Core dump :(

[Dmitry Chorine]

-bash-2.05b$ ~nagios/libexec/check_tcp -V
check_tcp (nagios-plugins 1.4.0alpha1) 1.37
The nagios plugins come with ABSOLUTELY NO WARRANTY. You may
redistribute
copies of the plugins under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.
-bash-2.05b$

Machine w/ Port 8080 is on local and I cant take it outside due to
security issues, I run tomcat on that port.

-----Original Message-----
From: Karl DeBisschop [mailto:karl at debisschop.net] 
Sent: Wednesday, March 03, 2004 9:29 PM
To: Dmitry Chorine
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Core dump :(


On Wed, 3 Mar 2004 17:53:55 -0500
"Dmitry Chorine" <dmitryc at drumbeatdigital.com> wrote:

> Any solutions on this
> 
> tama# ./check_http -H 192.168.3.17
> HTTP OK HTTP/1.1 200 OK - 1268 bytes in 0.004 seconds |time=4077us;;;0

> size=1268B;;;0 tama# ./check_http -H 192.168.3.17 -p 8080
> Segmentation fault (core dumped)
> tama# ./check_tcp -H 192.168.3.17 
> Segmentation fault (core dumped)
> tama# ./check_tcp -H 192.168.3.17 -p 8080
> Segmentation fault (core dumped)
> tama# 
> 
> I'm runnin nagios-1.2 on FreeBSD 4.9-RELEASE-p2

What plugin release (run both check_tcp and check_http with --version)?

I assume that there is content on 8080 and there should be a 200 HTTP
status code - is that true?

Can you reporduce this on any publically accesible URLs so others could
verify and debug?

--
Karl


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
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