On Nov 11, 2010, at 9:09 PM, Morris, Patrick wrote:
On 11/11/2010 11:46 AM, Jonathan Wiggins wrote:
'No Route To Host' is not a nagios error message but is coming from
your operating system. Based on that and the above information, I'd
say that the 'Home Page' check is being told to
On Nov 10, 2010, at 7:36 PM, Jonathan Wiggins wrote:
I see this in the messages files:
Nov 9 00:00:00 nagiosbox nagios: CURRENT SERVICE STATE: monitorednode;Home
Page;CRITICAL;HARD;1;No route to host
Nov 10 00:00:00 nagiosbox nagios: CURRENT HOST STATE:
monitorednode;UP;HARD;1;PING OK
On Nov 11, 2010, at 5:26 AM, Marc Powell wrote:
On Nov 10, 2010, at 7:36 PM, Jonathan Wiggins wrote:
I see this in the messages files:
Nov 9 00:00:00 nagiosbox nagios: CURRENT SERVICE STATE: monitorednode;Home
Page;CRITICAL;HARD;1;No route to host
Nov 10 00:00:00 nagiosbox nagios:
On 11/11/2010 11:46 AM, Jonathan Wiggins wrote:
'No Route To Host' is not a nagios error message but is coming from
your operating system. Based on that and the above information, I'd
say that the 'Home Page' check is being told to check a different,
invalid, host name or address than the
I'm stuck troubleshooting an error message in the Service Status Details, where
a monitored host is being reported as No Route to Host.
I can do remote plugin tests from the Nagios server to the monitored node
without any problems, but referencing this page:
On Nov 10, 2010, at 12:13 PM, Jonathan Wiggins wrote:
I'm stuck troubleshooting an error message in the Service Status Details,
where a monitored host is being reported as No Route to Host.
I can do remote plugin tests from the Nagios server to the monitored node
without any problems,
