NSCA daemon never writes to nagios.cmd or nsca.dump

[Noah Leaman]

I forgot to provide platform/version stats...

NSCA 2.4
Nagios 1.1 on Mac OS X 10.3.2 (on both central and distributed Nagios 
servers)

If anyone has any indication of where my trouble could be it would be 
greatly appreciated.

-- 
Noah

On Jan 21, 2004, at 1:33 AM, Noah Leaman wrote:

> Help!
>
> I cannot get the NSCA daemon to write anything to either the 
> nagios.cmd or the nsca.dump files.
> They are both defined in the nsca.cfg like so:
>
> command_file=/Users/nagios/var/rw/nagios.cmd
> alternate_dump_file=/Users/nagios/var/rw/nsca.dump
>
> I turned on debug (debug=1) and all I get in the syslog is this:
>
> Jan 21 01:19:00 bell nsca[15791]: Handling the connection...
> Jan 21 01:19:00 bell nsca[15791]: End of connection...
> Jan 21 01:20:00 bell nsca[15791]: Handling the connection...
> Jan 21 01:20:00 bell nsca[15791]: End of connection...
> Jan 21 01:21:00 bell nsca[15791]: Handling the connection...
> Jan 21 01:21:00 bell nsca[15791]: End of connection...
>
> this is for each time the send_nsca is submitted on the remote 
> (distributed) nagios host. nothing ever gets written to nagios.cmd and 
> nsca.dump is never even created. The fact that nsca.dump never gets 
> created seems like a clue of some sort. I do have external commands 
> enabled and they work in all other respect. the nsca daemon is running 
> as the user nagios and can write to nagios.cmd and the directory itt's 
> in.
>
> Any ideas what could be wrong?
>



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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