problem with nsca daemon

Marc Powell marc at ena.com
Thu Aug 18 20:29:50 CEST 2005



> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Frederik Vanhee
> Sent: Thursday, August 18, 2005 2:22 AM
> To: Nagios User
> Subject: [Nagios-users] problem with nsca daemon
> 
> 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'
> 

What do you see in your messages file when you enable debug in nsca.cfg?

--
Marc


-------------------------------------------------------
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