Page 1 of 1

check_http not parsing content after update

Posted: Tue Mar 10, 2020 8:16 am
by ehumphries
We were running 2.2.1 of the nagios plugins yesterday. Updated Nagios XI, then updated the plugins.
[root@localhost ~]# /usr/local/nagios/libexec/check_http -V
check_http v2.3.2 (nagios-plugins 2.3.2)
Existing nagios check we had configured doesn't seem to be finding "SOMESTRING" in the page content any longer:
[root@localhost ~]# /usr/local/nagios/libexec/check_http -I 10.2.3.26 -s "SOMESTRING" -m 8195 -f ok -u "/users/sign_in" -w 5 -p 8080
HTTP CRITICAL: HTTP/1.1 200 OK - string 'SOMESTRING' not found on 'http://10.2.3.26:8080/users/sign_in', page size 8194 too small - 8194 bytes in 0.032 second response time |time=0.031728s;5.000000;;0.000000 size=8194B;8195;0;0
If i do the same thing with CURL, clearly SOMESTRING still exists in the page content:
[root@localhost ~]# curl http://10.2.3.26:8080/users/sign_in | grep "SOMESTRING"
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 29764 100 29764 0 0 985k 0 --:--:-- --:--:-- --:--:-- 1002k
SOMESTRING Phone
I've dug through the different available flags, and I haven't yet figured out any magic incantation that appears to fix this issue. What am I doing wrong? What else can I check?

Re: check_http not parsing content after update

Posted: Tue Mar 10, 2020 9:47 am
by scottwilkerson
This was an issue identified in nagios-plugins 2.3.2 and will be resolved in the next release.
https://github.com/nagios-plugins/nagio ... issues/535

As a word of caution, we do not recommend upgrading to the latest and "greatest" nagios-plugins open-source project for Nagios XI customers as issues like this can arise. When we deem the plugins version is fully stable it will be included in a Nagios XI release.