CRITICAL - Socket timeout http URL

[rtsupport]

I found something strange --

Currently we are running on Nagios XI 2014 R2.7 where we are getting error and in order to update Nagios we have migrated all existing data to new Nagios Version 5.5.5 in separate servers with same architect which is in testing mode, and we found that on that server this check is working fine and we are getting OK result using same plugin and same command.

so confusion here is what stopping in current environment due to which this URL monitoring is not working ( Only for this URL ) rest are working fine. where same URL in latest version which is in testing mode is working fine.. ( which indicating that there is no issue from URL end )

Output from XI 2014 --

/check_http -c 15 -t 15 -f follow -H 13.129.00.00 -p 9809 -e GIOP -u /FileNet/Engine
CRITICAL - Socket timeout

Output from 5.5.5

./check_http -c 15 -t 15 -f follow -H 13.129.00.00 -p 9809 -e GIOP -u /FileNet/Engine
HTTP OK: Status line output matched "GIOP" - 12 bytes in 0.054 second response time |time=0.053786s;;15.000000;0.000000 size=12B;;;0

[cdienger]

They're probably running two different versions of the plugin. You can check the versions with:

/usr/local/nagios/libexec/check_http -V

[rtsupport]

yes found different version -

Current server having --
/usr/local/nagios/libexec/check_http -V
check_http v2.2.1 (nagios-plugins 2.2.1)

New server having --
/usr/local/nagios/libexec/check_http -V
check_http v2.0.3 (nagios-plugins 2.0.3)

So only copy paste plugin will work on is there any other way to do it?

[cdienger]

Copying the plugin over _may_ work but you will likely need to compile the new version of the plugin(s) on the server:

https://nagios-plugins.org/downloads/
https://nagios-plugins.org/doc/faq/compilation.html

[rtsupport]

will try this in test environments and update you.

But again question is still there why suddenly it stopped working only for 1 url rest are working fine. if this is due to version then it should stop for all URL we are monitoring?

[cdienger]

I suspect the other URLs are responding in a more expected manner. Just responding with "GIOP" is not a normal response from a web server.

[rtsupport]

so is there something we can ask to check APP team from webserver end or we can show them our findings.

[rtsupport]

Also noticed that on server we are facing issue we are already having latest version of plugin. Please see my last response as well.

now this is something from Server 1 having installed Nagiox XI 2014 installed we are getting error and server 2 having installed Nagios XI 5.5.5 we are getting service OK output. using same plugin, same command, same client.

can we check something from restriction/firewall area comparing server 1 and server 2 output or any may something which should be enable to make it work..

yes found different version -

Current server having --
/usr/local/nagios/libexec/check_http -V
check_http v2.2.1 (nagios-plugins 2.2.1)

New server having --
/usr/local/nagios/libexec/check_http -V
check_http v2.0.3 (nagios-plugins 2.0.3)

So only copy paste plugin will work on is there any other way to do it?

[cdienger]

Gather another tcpdump - 1 from the working server and 1 from the non working. It would be good to run the check_http commands with the "-v" option at the end to get verbose output.

[rtsupport]

sorry for delay in response was stuck in something.

Please find attached both output file as asked.

CMD output Not working ...

./check_http -w 15 -c 20 -H 13.129.00.00 -p 9809 -e GIOP -u /FileNet/Engine -v
GET /FileNet/Engine HTTP/1.1
User-Agent: check_http/v2.2.1 (nagios-plugins 2.2.1)
Connection: close
Host: 13.129.00.00:9809
Accept: */*


http://13.129.00.00:9809/FileNet/Engine is 12 characters
STATUS: GIOP
CRITICAL - Socket timeout

CMD Output working one..

./check_http -w 5 -c 10 -H 13.129.00.00 -p 9809 -e GIOP -u /FileNet/Engine -v
GET /FileNet/Engine HTTP/1.1
User-Agent: check_http/v2.0.3 (nagios-plugins 2.0.3)
Connection: close
Host: 13.129.00.00:9809
Accept: */*


http://13.129.00.00:9809/FileNet/Engine is 12 characters
STATUS: GIOP
**** HEADER ****

**** CONTENT ****

Status line output matched "GIOP" -
HTTP OK: Status line output matched "GIOP" - 12 bytes in 0.032 second response time |time=0.031749s;5.000000;10.000000;0.000000 size=12B;;;0