Core returns HTTP 400, where XI returns 302 or 200
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Core returns HTTP 400, where XI returns 302 or 200
please send the command definition for the command on each
Re: Core returns HTTP 400, where XI returns 302 or 200
Here you go (attached)scottwilkerson wrote:please send the command definition for the command on each
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Core returns HTTP 400, where XI returns 302 or 200
your commands do not match
check_http2 should be
but you have
check_http2 should be
Code: Select all
$USER1$/check_http -H $HOSTADDRESS$ $ARG1$Code: Select all
$USER1$/check_http -t 120 -I $HOSTADDRESS$ $ARG1$Re: Core returns HTTP 400, where XI returns 302 or 200
1. It does not matter: check_http CORE command produces WARNING in CORE GUI and OK in CORE CLIscottwilkerson wrote:your commands do not match
check_http2 should bebut you haveCode: Select all
$USER1$/check_http -H $HOSTADDRESS$ $ARG1$Code: Select all
$USER1$/check_http -t 120 -I $HOSTADDRESS$ $ARG1$
2. CORE having difficulty with some portals, so we have to extend the delay (30 sec normally) in CORE / use of -H makes no difference
So why CORE check_http produces OK in CLI and WARNING in GUI ?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Core returns HTTP 400, where XI returns 302 or 200
It does matter, this is the command that is going to be executed, have you tested it in the CLI?
Code: Select all
/usr/local/nagios/libexec/check_http -t 120 -I 185.15.212.41 -f follow -I 185.15.212.41 -u "/" -S -p 443-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Core returns HTTP 400, where XI returns 302 or 200
It does matter when you are doing a certificate checkdlukinski wrote: 2. CORE having difficulty with some portals, so we have to extend the delay (30 sec normally) in CORE / use of -H makes no difference
Re: Core returns HTTP 400, where XI returns 302 or 200
change from -I to -H for check_http2 (copied from XI) just made a difference, irrespective of the delay set.scottwilkerson wrote:It does matter, this is the command that is going to be executed, have you tested it in the CLI?
Code: Select all
/usr/local/nagios/libexec/check_http -t 120 -I 185.15.212.41 -f follow -I 185.15.212.41 -u "/" -S -p 443
the problem is that when i execute check_http (stock CORE 4.3.4) in CLI, i get an OK
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.129 second response time |time=0.128775s;;;0.000000 size=7426B;;;0
[root@fikc-hvk-nagcore01 objects]#
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Core returns HTTP 400, where XI returns 302 or 200
in your Core your check_http service you showed is using
Code: Select all
$USER1$/check_http -t 55 -I $HOSTADDRESS$ $ARG1$Re: Core returns HTTP 400, where XI returns 302 or 200
scottwilkerson wrote:in your Core your check_http service you showed is using
Code: Select all
$USER1$/check_http -t 55 -I $HOSTADDRESS$ $ARG1$
True :-\
Did not realize while Copy & Pasting command from XI
So -H vs -I must be the difference for the CORE itself?
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Core returns HTTP 400, where XI returns 302 or 200
I would believe this is your only problemdlukinski wrote:So -H vs -I must be the difference for the CORE itself?