Cheshire Cat Computing

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

This means that the NagEvLog agent is not able to contact the NSCA daemon on your Nagios server, which is why it cannot send the alerts.

Check that nsca is running on your Nagios server. Check it can write to the command pipe. Check that Nagios is actually processing the command pipe (nagios.cfg). Check you dont have a firewall in the way. Make sure you have the latest version of nagevlog.

Since your test works it may be that the nsca daemon is running, but subsequently fails for some reason (command pipe permissions?). Check the nagios logs and the nsca daemon logs. Maybe run nsca daemon in the foreground to see any activity.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

_________________
JonMikel,
|| Ubuntu 6.06 LTS || Nagios 2.9 || Cacti 0.8.6h || PHP 5.1.2 || MySQL 5.0.22 || RRDTools 1.2.12-13 || NSCA 2.4 || SNMP Informant || NagEventLog 1.8.3 ||

I still have the same problem, and i don't know how to fix it... :S any ideas??

_________________
JonMikel,
|| Ubuntu 6.06 LTS || Nagios 2.9 || Cacti 0.8.6h || PHP 5.1.2 || MySQL 5.0.22 || RRDTools 1.2.12-13 || NSCA 2.4 || SNMP Informant || NagEventLog 1.8.3 ||

Your error logs are telling you the problem.

First of all, you have the latest version. The control app latest version is 1.8.0, the daemon is 1.8.3.

The NagEventLog is trying to send the NSCA message, but gets the error because the NSCA daemon hangs up on it. This could be because of an error in the NSCA, or problems with the SSL libraries, or your configuration.

Your NSCA log tells you 'is not allowed to talk to us'. This is because you have configured NSCA to reject connections from this IP! You have either done this in the nsca.cfg allowed_hosts definition, or else in you Xinetd or tcpwrappers configuration. Since you are using inetd, I suspect you also have tcpwrappers set and it is rejecting the connection. Look in /etc/hosts.allow and make sure you have a 'nrpe: x.x.x.' line or similar for your subnet x.x.x.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11