check_http errors after update

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.
Locked
SnakeMind
Posts: 2
Joined: Tue Jul 04, 2017 4:05 am

check_http errors after update

Post by SnakeMind »

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

Code: Select all

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?
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: check_http errors after update

Post by cdienger »

Can you post the complete check_http command that you're using? Something about the request being made is upsetting the destination.

Verify the check_http version from the cli with:

Code: Select all

/usr/local/nagios/libexec/check_http --version
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.
SnakeMind
Posts: 2
Joined: Tue Jul 04, 2017 4:05 am

Re: check_http errors after update

Post by SnakeMind »

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 :)
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: check_http errors after update

Post by dwhitfield »

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:

Code: Select all

HTTP CRITICAL - Invalid HTTP response received from host on port 8443: HTTP/1.1 400 Bad Request
If the timeout commands look different, please also show us that.
whereisaaron
Posts: 1
Joined: Sun Jul 16, 2017 12:17 pm

Re: check_http errors after update

Post by whereisaaron »

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.
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: check_http errors after update

Post by tgriep »

Thanks @whereisaaron for the help.
@SnakeMind let us know if you have any further questions.
Be sure to check out our Knowledgebase for helpful articles and solutions!
cincia
Posts: 1
Joined: Thu Sep 07, 2017 12:05 pm
Location: Wood Green, London

Re: check_http errors after update

Post by cincia »

Where do you plan to release the new update?
To want to, is to be able to.
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: check_http errors after update

Post by dwhitfield »

All new versions are released at https://github.com/nagios-plugins/nagios-plugins

Compile instructions available at https://support.nagios.com/kb/article.php?id=569
Locked