You were correct. My check command showed:
# 'check_http' command definition
define command{
command_namecheck_http
command_line$USER1$/check_http -I $HOSTADDRESS$ $ARG1$
}
But my test was passing two arguments (-p and -u). Once I updated the
test to use
I'm seeing the following:
HTTP WARNING: HTTP/1.1 400 No Host matches server name seth.my.int.domain
This is what the test looks like in Nagios:
## HTTP - alternate port
define service {
host_name seth
service_description HTTP
check_command
On Fri, 15 May 2009 16:17:50 -0400, Andrew Davis ncc...@gmail.com
wrote:
Oddly enough, low-level tests show an HTTP 302, which I expect. But
Nagios is offering up a 400 error and a warning:
From my workstation, confirming the server is configured correctly:
gentoo:~ adavis$ telnet seth
