Tuesday, May 21st 2013, 6:41pm UTC+2
You are not logged in.
Dear visitor, welcome to Monitoring-Portal.
Although this is a german monitoring forum, please don't hesitate to post in
English. Nearly everybody here understands you and will answer in English as well.
If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form to register here or read more information about the registration process. If you are already registered, please login here.
Beginner
Number of monitoring servers: 1
Nagios Version: 3.3.1
Distributed monitoring: Nein
Redundant monitoring: Nein
Number of hosts: 187
Number of services: 143
OS: CentOS
Plugin Version: ?
NDO Version: 1
Number of monitoring servers: 2-5
Nagios Version: 3.x
Distributed monitoring: Nein
Redundant monitoring: Nein
Number of hosts: 80-200
Number of services: 1400-2000
OS: Linux
Plugin Version: Whatever I can download, patch, or cobble together myself :-)
Other Addons: n2rrd, PNP, livestatus
Beginner
Number of monitoring servers: 1
Nagios Version: 3.3.1
Distributed monitoring: Nein
Redundant monitoring: Nein
Number of hosts: 187
Number of services: 143
OS: CentOS
Plugin Version: ?
NDO Version: 1
I'm having a bit of trouble to imagine how problems with a service check command could lead to hosts being erroneously pronounced DOWN, and only that. Since you seem to have traced it (to latency effects?), could you elaborate on that? Otherwise, what host check command do you use, and what is it's (textual) output in the error state?
Gender: male
Location: Linz
Number of monitoring servers: 1
Nagios Version: 0.0
Icinga Version: 1.7.0
Distributed monitoring: Ja
Redundant monitoring: Nein
Number of hosts: -
Number of services: -
OS: SLES11
Plugin Version: -
NDO Version: -
Number of monitoring servers: 2-5
Nagios Version: 3.x
Distributed monitoring: Nein
Redundant monitoring: Nein
Number of hosts: 80-200
Number of services: 1400-2000
OS: Linux
Plugin Version: Whatever I can download, patch, or cobble together myself :-)
Other Addons: n2rrd, PNP, livestatus
Which, I presume, is ultimately a "ping" command (read: a mechanism completely different from the SNMP used to gather interface statistics). There are no services being erroneously reported as down?I'm using the check_host_alive check command.
Beginner
Number of monitoring servers: 1
Nagios Version: 3.3.1
Distributed monitoring: Nein
Redundant monitoring: Nein
Number of hosts: 187
Number of services: 143
OS: CentOS
Plugin Version: ?
NDO Version: 1
It's only hosts being erroneously reported as down.Which, I presume, is ultimately a "ping" command (read: a mechanism completely different from the SNMP used to gather interface statistics). There are no services being erroneously reported as down?I'm using the check_host_alive check command.
Number of monitoring servers: 2-5
Nagios Version: 3.x
Distributed monitoring: Nein
Redundant monitoring: Nein
Number of hosts: 80-200
Number of services: 1400-2000
OS: Linux
Plugin Version: Whatever I can download, patch, or cobble together myself :-)
Other Addons: n2rrd, PNP, livestatus
As far as the mechanism connecting (probable) cause and effect is concerned - I'm stumped, sorry.It's only hosts being erroneously reported as down.Which, I presume, is ultimately a "ping" command (read: a mechanism completely different from the SNMP used to gather interface statistics). There are no services being erroneously reported as down?I'm using the check_host_alive check command.
Something FAN specific, possibly.