Home / server / Questions / 839589
In Process
greg0ire
Asked: 2017-03-22 01:12:35 +0800 CST

Troubleshooting shinken

  • 772

I have a Shinken setup which tests 2 domains that are behind an HTTP authentication. To do so, I use the following custom macro:

define command {
    command_name new_check_http
    command_line /opt/shinken/libexec/check_http $ARG1$ --warning $ARG2$ --critical $ARG3$
}

The command is called like this

check_command new_check_http!-I my_host -H my_website -p 80 -a "http_user:http_password"!10!30

When I try /opt/shinken/libexec/check_http -I my_host -H my_website -p 80 -a "http_user:http_password --warning 10 --critical 30, I get a 302, like I should. However, Shinken keeps reporting 401 every hour. What could be the problem? How can I see what is actually being done?

shinken

1 Answers

  1. I think this might be an issue with spaces and the quotes. Try to separate it with more variables, for example:

    define command {
    command_name new_check_http
    command_line /opt/shinken/libexec/check_http -I $ARG1$ -H $ARG2$ -p $ARG3$ -a $ARG4$ --warning $ARG5$ --critical $ARG6$
}

check_command new_check_http!my_host!my_website!80!http_user:http_password!10!30

    Or even better, use custom variables:

    define command {
    command_name new_check_http
    command_line /opt/shinken/libexec/check_http -I $_IP$ -H $_HOSTNAME$ -p $_PORT$ -a $_AUTH$ --warning $ARG1$ --critical $ARG2$
}

    Then, in your host definition:

    define host{
  host_name test
  address   127.0.0.1
  _IP       127.0.0.1
  _HOSTNAME test
  _PORT     80
  _AUTH     http_user:http_password
}
    • 1