Page 1 of 1

there is some bug for check_http in the CCM

Posted: Thu Sep 10, 2020 1:05 pm
by Elena
Hello Support,

My Nagios XI version 5.7.2, there is some bug when I "Run Check Command" of check_http in the CCM, but the actual check result is OK, please help to check how to fix it, thank you.

For example,
======
CCM, shows "HTTP WARNING: HTTP/1.1 404 Not Found".
[nagios@sjprngsxi01 ~]$ /usr/local/nagios/libexec/check_http -H sjprplnhweb03 -u '/istore-client/partners/Gro21010/home/?allid=Gro21010' --ssl -p 443 -v -N
GET /istore-client/partners/Gro21010/home/\?allid=Gro21010 HTTP/1.1
User-Agent: check_http/v2.0.3 (nagios-plugins 2.0.3)
Connection: close
Host: sjprplnhweb03
Accept: */*
https://sjprplnhweb03:443/istore-client ... d=Gro21010 is 543 characters
STATUS: HTTP/1.1 404 Not Found
**** HEADER ****
Date: Thu, 10 Sep 2020 17:53:02 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubdomains
Content-Length: 315
Connection: close
Content-Type: text/html; charset=iso-8859-1
**** CONTENT ****
[[ skipped ]]
HTTP WARNING: HTTP/1.1 404 Not Found - 543 bytes in 0.011 second response time |time=0.011281s;;;0.000000 size=543B;;;0

====
The actual check result in NagiosXI WEB UI, shows "HTTP OK: HTTP/1.1 200 OK".


GET /istore-client/partners/Gro21010/home/?allid=Gro21010 HTTP/1.1
User-Agent: check_http/v2.0.3 (nagios-plugins 2.0.3)
Connection: close
Host: sjprplnhweb03
Accept: */*

https://sjprplnhweb03:443/istore-client ... d=Gro21010 is 322 characters
STATUS: HTTP/1.1 200 OK
**** HEADER ****
Date: Thu, 10 Sep 2020 17:55:31 GMT

Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubdomains
Last-Modified: Fri, 10 Jul 2020 22:34:48 GMT
Accept-Ranges: bytes
Content-Length: 2478
Vary: Accept-Encoding
X-Frame-Options: SAMEORIGIN
Connection: close

Content-Type: text/html
**** CONTENT ****
[[ skipped ]]
HTTP OK: HTTP/1.1 200 OK - 322 bytes in 0.013 second response time
======
Sincerely,
Elena Lin

Re: there is some bug for check_http in the CCM

Posted: Fri Sep 11, 2020 12:06 pm
by cdienger
It's trying to escape the question mark. Try encoding the question mark:

Code: Select all

-u '/istore-client/partners/Gro21010/home/%3Fallid=Gro21010'

Re: there is some bug for check_http in the CCM

Posted: Sat Sep 12, 2020 3:47 am
by Elena
Hello cdienger,

Thanks for your reply, but it doesn't work, still shows "HTTP WARNING: HTTP/1.1 404 Not Found" in CCM.
It is no bug previously, when my NagiosXI version updated to 5.7.2, the bug is appeared suddenly.

Sincerely,
Elena Lin
============
[nagios@sjprngsxi01 ~]$ /usr/local/nagios/libexec/check_http -H sjprplnhweb03 -u '/istore-client/partners/Gro21010/home/%3Fallid=Gro21010' --ssl -p 443 -v -N
GET /istore-client/partners/Gro21010/home/%3Fallid=Gro21010 HTTP/1.1
User-Agent: check_http/v2.0.3 (nagios-plugins 2.0.3)
Connection: close
Host: sjprplnhweb03
Accept: */*


https://sjprplnhweb03:443/istore-client ... d=Gro21010 is 543 characters
STATUS: HTTP/1.1 404 Not Found
**** HEADER ****
Date: Sat, 12 Sep 2020 08:39:24 GMT
Server: Apache
Strict-Transport-Security: max-age=63072000; includeSubdomains
Content-Length: 315
Connection: close
Content-Type: text/html; charset=iso-8859-1
**** CONTENT ****
[[ skipped ]]
HTTP WARNING: HTTP/1.1 404 Not Found - 543 bytes in 0.009 second response time |time=0.009247s;;;0.000000 size=543B;;;0

Re: there is some bug for check_http in the CCM

Posted: Mon Sep 14, 2020 12:07 pm
by cdienger
Thanks for bringing this to our attention. I will file a bug regarding this not working in the CCM.

Re: there is some bug for check_http in the CCM

Posted: Mon Sep 21, 2020 8:02 pm
by Elena
Hello cdienger,

Any update? The bug is still there, please help, thank you.

Sincerely,
Elena Lin

Re: there is some bug for check_http in the CCM

Posted: Tue Sep 22, 2020 4:29 pm
by ssax
There were some security fixes related to the CCM test button implemented in XI 5.7 that have made it highly restrictive, I have added this post to the bug report but there isn't a fix listed (the developer said to talk with him first) and the developer I need to talk to about this is currently out of the office. I am able to replicate it on my system as well.