Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Goodmorning,
After Nagios plugins got updated last night using epel-testing, the check_http seems to be broken.
Every device with a check_http is now in either socket timeout status or in a critical status like
HTTP CRITICAL - Invalid HTTP response received from host on port 8443: HTTP/1.1 400 Bad Request
This is the only plugin that is not working at this moment, and since it is a freshly updated plugin in the test phase, i thought I wanted to reach out. Anyone any idea what can be wrong?
The latest plugins(2.2.1) release can be found at https://nagios-plugins.org/ . I would recommend upgrading the plugins if they are not at this version.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Hi,
sorry for the late reply, this was with the 2.2.1-git2.el7 version, with just the --check-version command you'll only get 2.2.1
With version 2.2.1-1.el7 installed there is nothing wrong and it works like a charm, like said, when using the epel-testng branch that includes 2.2.1-git2.el7 it fails.
Hope this helps and gets it resolved
First of all, we have no control over what epel puts in their repo. You may want to file a bug with them (or compile from our source so we can fix the bug ourselves).
More to the point, we still need to see the actual command that is failing. Please show us what is generating the following:
Since upgraded in to check_http 2.2.1 there are a few problems with '--no-body'. E.g. it no longer works in combined with '--expect'. If you remove the '--no-body' option the test will work again.
So if you have any HTTP header tests using both '--expect' and '--no-body', remove the '--no-body' to work around this new bug.