Nagios Support Forum

Hi

I discovered a problem with check_http 2.21 yesterday:

When using check_http on a specific page, we got a critical on one Installation, where all other machines whowed the service using the same parameters as OK.

/usr/lib64/nagios/plugins/check_http -I 217.110.44.176 -H wertpapiere.ing-diba.de -w 3 -c 4 -t 5 -S -u "/Investieren/Aktie/DE0005140008" -s "C988D76946AF9CAB3E5F750DAE35B6D1"
HTTP CRITICAL: HTTP/1.1 200 OK - string 'C988D76946AF9CAB3E5F750DAE...' not found on 'https://wertpapiere.ing-diba.de:443/Inv ... 0005140008' - 54069 bytes in 0.047 second response time |time=0.047288s;3.000000;4.000000;0.000000 size=54069B;;;0

Checking things, I found out, that on that machine we are running the Nagios Pluins Version 2.21, while the other site still uses Nagios Plugins 2.14.

After that I copied the check_http from Plugins 2.14 to the machine with Plugins 2.21 as check_http_214, and running the command again, got the following result:

/usr/lib64/nagios/plugins/check_http_214 -I 217.110.44.176 -H wertpapiere.ing-diba.de -w 3 -c 4 -t 5 -S -u "/Investieren/Aktie/DE0005140008" -s "C988D76946AF9CAB3E5F750DAE35B6D1"
HTTP OK: HTTP/1.1 200 OK - 54069 bytes in 0.053 second response time |time=0.052689s;3.000000;4.000000;0.000000 size=54069B;;;0

We are using several hundred different check_hhtp calls, but that URL is the only one which causes this problem.

Looking at the plugin location did you install the rpm package? I'm testing on a manually installed version of nagios-plugins 2.2.1 and it is working for the check command you provided. If installed via rpm, where is the rpm from?

The verion of 2.21 we are using is installed on a Centos 7 machine. The repository for the plugins is EPEL and I guess even if 2.21 is the newest major release, the is a newer version I can update to.

I will get back to you if that solves the problem.

Hello,

I will get back to you if that solves the problem.

Sounds good. We'll wait for you reply.

The update solved the problem, thanks for your help, the question leaded me in the right direction (I had only checked for the major release, where 2.21 is the newest one).

Hi,

The update solved the problem, thanks for your help, the question leaded me in the right direction (I had only checked for the major release, where 2.21 is the newest one).

Great. We'll mark this post as resolved, but if you have any new questions, please feel free to open another.