problem with nsca daemon

Frederik Vanhee frederik.vanhee at perso.be
Thu Aug 18 09:21:55 CEST 2005


Hi,

in my distributed Nagios environment, I use the nsca-daemon to send the 
check_results from the distributed Nagios servers to the central Nagios 
server running the web-interface. Nagios 2.0b3 and NSCA 2.4

So far, so good. Everything runs fine, all check results arrive at the 
central server.

On my local network (where the central Nagios server is), I want to 
catch some SNMP traps and import them into Nagios.
I managed to do this using snmptrapd and snmptt. Snmptt sends the trap 
to Nagios via 'send_nsca'. The host that catches the traps is the same 
hosts that runs Nagios and the nsca-daemon

The only problem I have is : when I send the trap to the Nagios server 
(running nsca-daemon) with send_nsca, I always get the message '0 data 
packet(s) where sent succesfully', when I do the same from a another 
box, everything runs fine and I get the message '1 data packet(s) where 
sent succesfully'

So, for some reason, the send_nsca program doesn't send the check_result 
if it is sent from the same machine the nsca-daemon is running. Has 
anyone experienced this behaviour ? Yes, the local-machine's ip is in 
the allowed hosts section of the nsca.cfg, and 127.0.0.1 is too.

Of course I could send directly to the nagios-command pipe (I tried it 
and it works), but I prefer using nsca

Frederik


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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





More information about the Users mailing list