Nagios not accepting regex in command

nagiosregex

I have this command defined:

define command{
command_name check_http_sane
command_line $USER1$/check_http -H $HOSTNAME$ -r "HTTP/1.1 (200|301|302|303|304|307|401|418|426)"
}

When I run it manually on command line, it works fine, but nagios (2.6) reports a "pattern not found" error. Do I need to escape something?

Edit: As stated below, I solved it by replacing check_http with my own script which works (good enough for our use case, anyway). Script: http://pastebin.com/hNmz6Wa1

Best Answer

The source code for check_http.c says the -r option checks the headers and the page contents. The problem you are seeing is probably the Nagios command macro interpreter trying to replace something in your regex string.

You should try escaping all of your (,| and ) characters. If that doesn't work, try just the parentheses and just the pipes. You might also try using single quotes instead of double quotes.

Related Solutions

Debian – Nagios command not transmitting all arguments

You're mixing up the arguments which are defined on monitoring host with the arguments on the remote host. The $ARGx$ macro cannot be used on the NRPE host.

Be default, the check_nrpe command is defined as belows:

define command{
    command_name    check_nrpe
    command_line    $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ -t 120
}

On the remote host you must use the 'real' value, something like this:

command[check_pgsql]=/usr/lib/nagios/plugins/check_pgsql -d test -l test -p test

and this command can be called from the Nagios host with:

define service{
    use                     test-service         
    host_name               DEMOCGN002
    service_description     Postgres State
    check_command           check_nrpe!check_pgsql
    notifications_enabled   1
    }

No need to pass the IP address because it get the value of host_name.

Complex nagios command

From comments discussion:

Nagios is apparently eating up anything after the semicolon in the "command" definition. The easiest way to manage this is to wrap up the complex command into a shell script that will be called by Nagios.

As part of debugging, the running Nagios configuration can be viewed using the CGI from the web interface, specifically the config.cgi (e.g., https://nagios.example.com/cgi-bin/nagios3/config.cgi). This will show the current set of commands, hosts, etc.

Best Answer

Related Solutions

Debian – Nagios command not transmitting all arguments

Complex nagios command

Related Topic