Nagios Support Forum

So I guess the next question really is, why is Nagios only checking it twice, instead of all 5 times that it's supposed to?

Over the course of that day, the router had gone down several times; There were some recoveries, but at one point, it was pretty hard down for some time--each time the pfsense OS kernel would panic due to some flaky hardware (long story ;) ), but when it started panicking only minutes after it reboo...

For the purposes of this discussion, yes, it's just the ones behind the router. I did discover some custom entries monitoring our esxi server complaining, but I discovered that when I created the commands for those checks, that I accidentally told it to use $HOSTNAME$ instead of $HOSTADDRESS$. And s...

Sure thing. Here's the router config: define host{ name generic-host; The name of this host template check_period 24x7 ; By default, hosts are checked round the clock check_command check-host-alive; Default command to check if servers are "alive" check_interval 1 ; Actively check the host ...

That does makes sense to me, however, once it determined that the router was in fact down, wouldn't it change the child hosts to unreachable? In my recent experience with the downed router, it did determine that the router was down, but never changed the others to unreachable, and continued sending ...

So I have a question. I have two Nagios setups that are up and configured, and well to my liking, save for one point--parent/child relationships. I went ahead and added the parents field to all of my hosts, disabled unknown notifications, and now the map reflects fairly accurately our network, as na...