False alerts on http service
francis picabia
fpicabia at gmail.com
Wed Sep 12 20:28:22 CEST 2012
On Wed, Sep 12, 2012 at 3:05 PM, Andreas Ericsson <ae at op5.se> wrote:
> Examine the *host* check, not the service check, if you want to figure
> out why the host appears to be down.
I wondered if it could be that, but usually if I messed up
the host, it would let me know on start up.
I have this:
# Unix host definition template
define host{
name unix-host
use generic-host
check_command check-host-alive
contact_groups unix-admins
register 0
}
# 'webwork' host definition
define host{
use unix-host
host_name webwork
alias (webwork) Webwork server
address WWW.XXX.YYY.ZZZ
max_check_attempts 10
notification_interval 480
notification_period 24x7
notification_options d,u,r
}
unix-host is used in many other hosts without a problem, and webwork
host entry was a copy/paste based on other working entries. I don't see what
could be wrong other than getting the IP right.
I can ping webwork from the nagios monitoring system.
I can't see the problem.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list