Nagios Support Forum

Posted: **Wed Jun 29, 2016 7:12 am**

This is the scenario.

I have two web servers (serverA and serverB) behind a load balanced address serverLB. If you try to connect to the individual servers by hostname you get redirected. One page only (for monitoring) is accesible directly via IP address on each web server.

From the command line I can run the command:

Code: Select all

./check_http -I 10.10.8.64 -f follow -s "Results check:" or ./check_http -I 10.10.8.65 -f follow -s "Results check:"

and if I enable verbose I can see that I'm on the respective servers.

So I've assumed that if I set this in my services.cfg file, everything would be OK.

Code: Select all

define service{
        use                                  generic-service         ; Name of service template to use
        host_name                       serverA
        service_description           Homepage
	check_command		check_http! -I 10.10.8.64 -f follow -s "Results check:"
        }

define service{
        use                                  generic-service         ; Name of service template to use
        host_name                       serverB
        service_description           Homepage
	check_command		check_http! -I 10.10.8.65 -f follow -s "Results check:"
        }

Well it's not OK. Nagios ignores the 'I' option and still uses the hostname, which means I'm not getting the result I wanted or expected.

This looks like a bug to me, unless someone can tell me otherwise?

Posted: **Wed Jun 29, 2016 9:36 am**

Can you show us your command definition for check_http? Typically this can be found in the /usr/local/nagios/etc/commands.cfg file.

By default I think it is always trying to use the hostname:

Code: Select all

define command {
       command_name                             check_http
       command_line                             $USER1$/check_http -I $HOSTADDRESS$ $ARG1$
}

In the above case, you would modify the command_line parameter and remove the -I $HOSTADDRESS$ section.

Posted: **Tue Mar 28, 2017 6:59 am**

mcapra wrote:Can you show us your command definition for check_http? Typically this can be found in the /usr/local/nagios/etc/commands.cfg file.

By default I think it is always trying to use the hostname:
Code: Select all
define command {
       command_name                             check_http
       command_line                             $USER1$/check_http -I $HOSTADDRESS$ $ARG1$
}
In the above case, you would modify the command_line parameter and remove the -I $HOSTADDRESS$ section.

Yes that's what was doing it. Many thanks for pointing this out, and sorry it took me so long to thank you. I thought I'd already replied and was horrified when I discovered I hadn't.

Posted: **Tue Mar 28, 2017 10:48 am**

Has everything been sorted? Is it okay to lock this thread or did you have any further questions related to this?

Posted: **Wed Mar 29, 2017 4:44 am**

I'm happy for this one to be closed now. Thanks.

Nagios Support Forum

Is this a bug in Nagios core or by design?

Is this a bug in Nagios core or by design?

Re: Is this a bug in Nagios core or by design?

Re: Is this a bug in Nagios core or by design?

Re: Is this a bug in Nagios core or by design?

Re: Is this a bug in Nagios core or by design?