Core returns HTTP 400, where xi returns 302 or 200

dlukinski · Post by **dlukinski** » Wed Feb 21, 2018 4:26 pm

Hello Nagios Support

I get CORE HTTP checks returning HTTP 400, where xi returns 302 for the same check command

CORE:
FI-HVK-NRDP-HTTP-Login-tracker.konecranes.com

WARNING 02-21-2018 23:24:02 0d 0h 48m 51s 5/5 HTTP WARNING: HTTP/1.1 400 Bad Request - 581 bytes in 0.005 second response time

xi:

HTTP OK: HTTP/1.1 200 200 - 40883 bytes in 0.035 second response time

Command:
check_xi_service_http! -f follow -I 10.102.74.221 -u "/" -S -p 443!!!!!!!

check_http in CORE case

How to fix this?

Post by **tacolover101** » Thu Feb 22, 2018 3:53 am

check_xi_service_http is likely defined different than your check_http. i would compare your check commands.

if that's not the case, chase down all the differences and you'll eventually find one. running check_http / curl in verbose will help.

scottwilkerson · Post by **scottwilkerson** » Thu Feb 22, 2018 9:56 am

I agree with @tacolover101, you will need to compare the commands as will as the check_command in the config for each of them and compare side by side.

dlukinski · Post by **dlukinski** » Tue Feb 27, 2018 4:34 pm

scottwilkerson wrote:I agree with @tacolover101, you will need to compare the commands as will as the check_command in the config for each of them and compare side by side.

Could we transfer check_xi to CORE, rename and use it as check_http2 ?

Both xi and CORE http are the stock ones (never edited)

scottwilkerson · Post by **scottwilkerson** » Tue Feb 27, 2018 4:39 pm

I am not sure what you mean by check_xi

dlukinski · Post by **dlukinski** » Tue Feb 27, 2018 4:44 pm

scottwilkerson wrote:I am not sure what you mean by check_xi

Either copy check_xi_service_http and rename to check_http2 or copy check_http from xi machine to CORE?

scottwilkerson · Post by **scottwilkerson** » Tue Feb 27, 2018 4:47 pm

sure that would work

dlukinski · Post by **dlukinski** » Thu Mar 01, 2018 2:35 pm

scottwilkerson wrote:sure that would work

Copied check_http from xi to CORE (called check_http2, configured in commands)

Tried using with 3 portals checks
- same commands used as in xi
- same check_http used as in xi

WARNING in CORE and OK in xi

So this is not check_http problem, but a CORE server problem. We;ve got 8 of them checking portals remotely and we want to see this problem fixed.

What we do now?

scottwilkerson · Post by **scottwilkerson** » Fri Mar 02, 2018 9:54 am

can you show the command line output and the command, running the command from the CLI?

I also need you to share the command, service and host config both on a working systen and a non-working system

If it

dlukinski · Post by **dlukinski** » Fri Mar 02, 2018 10:41 am

scottwilkerson wrote:can you show the command line output and the command, running the command from the CLI?

I also need you to share the command, service and host config both on a working systen and a non-working system

If it

---------------------------------------------------------------------------------------------------------------------------------------
Case of 3 VPN Portal checks (same command, different IPs)

Code: Select all

 -f follow -I 185.15.212.41 -u "/" -S -p 443

OK in xi CLI

Code: Select all

[nagios@fikc-nagxiprod01.konecranes.com ~]$ /usr/local/nagios/libexec/check_http -H vpneur.konecranes.com -f follow -I 185.15.212.41 -u "/" -S -p 443
HTTP OK: HTTP/1.1 200 OK - 7426 bytes in 0.113 second response time |time=0.112642s;;;0.000000 size=7426B;;;0

OK in CORE CLI

Code: Select all

[root@fikc-hvk-nagcore01 objects]# /usr/local/nagios/libexec/check_http -H vpneur.konecranes.com -f follow -I 185.15.212.41 -u "/" -S -p 443
HTTP OK: HTTP/1.1 200 OK - 7426 bytes in 0.131 second response time |time=0.130780s;;;0.000000 size=7426B;;;0

- Tried both "core" check_http and "xi" check_http on the CORE with the same command.

BUT WARNING in CORE GUI as attached

Nagios Support Forum

Core returns HTTP 400, where xi returns 302 or 200

Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200

Re: Core returns HTTP 400, where xi returns 302 or 200