(No output!) Errors in Nagios 2.4

[Andy Shellam]

Hi,

I've been using Nagios for around 5 months now with no problems.  I've 
recently added a new server onto my network, which has added somewhere 
in the region of another 3 hosts and 12 services onto Nagios.

Since then I now keep getting random errors in the "Status Information" 
for services only.

For example I've got a HTTP monitor which monitors 
http://photos.andyshellam.eu:80, and this has started saying "Name or 
service not known" or "(No output!)" and labelled with either an OK or 
CRITICAL state (when the site is actually OK.)

I've also got an SMTP check which should be CRITICAL as the server's not 
yet up and running - Nagios labelled this as OK with an "(No output!)" 
message.

An SSH connection has also started failing, saying "Server returned:" in 
the Status Information box with a CRITICAL status, even though the 
server was up and running (as it's on the same machine as Nagios.)

Lastly, an NRPE check started failing, saying "Cannot resolve 'tcp' as 
service name".

In all the above cases, if I force an active check, all the problems 
return to the status they should be, but within 30 minutes or so 
(services are checked every 5 minutes) they start spewing these random 
errors again.

Any ideas?

This is Nagios 2.4 with plugins 1.4.3, NRPE 2.5.2 on a Fedora Core 5 
machine.

Thanks

Andy.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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