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

[Noah Leaman]

Was wondering if anyone had any acknowledgment concerning my problem 
with NSCA and if so could you shoot me an email? I'm sweatin' it 'cause 
I'm on a deadline and right now I have to report that nagios doesn't 
work on a fundamental level in our environment. I was hoping to replace 
a HP OpenView installation of about 1500 hosts but if the distributed 
nagios setup functionality has such problems, then looks like nagios is 
out.

BTW, I cross posted to the devel list because of that "allowed_hosts" 
quirkiness...

-- 
Noah

On Jan 21, 2004, at 11:42 PM, Noah Leaman wrote:

> A little more info... I get the same problem even when doing a 
> send_nsca on the same host that has the nsca daemon running on it:
>
> (from syslog)
>
> Jan 21 23:21:01 bell nsca[22499]: Handling the connection...
> Jan 21 23:21:02 bell nsca[22499]: End of connection...
> Jan 21 23:22:01 bell nsca[22499]: Handling the connection...
> Jan 21 23:22:01 bell nsca[22499]: End of connection...
>
> ... is this a bug with nsca on OS X 10.3? Any one else running nsca 
> 2.4 on 10.3 or seen this problem on any platform? I saw one other 
> person post this same issue but there was no response then. I am not 
> sure what platform he was on.
>
> My nsca.cfg:
>
> server_port=5667
> allowed_hosts=<my_ip_address_list_here>
> nsca_user=nagios
> nsca_group=nagios
> debug=1
> command_file=/Users/nagios/var/rw/nagios.cmd
> alternate_dump_file=/Users/nagios/var/rw/nsca.dump
> password=<my_password_here>
> aggregate_writes=0
> append_to_file=0
> max_packet_age=30
> decryption_method=1
>
>
> I tried sending using Jason Lancaster's perl version of send_nsca but 
> I just get the same thing... nothing ever written out from the nsca 
> daemon. Seems the problem is the daemon itself, not the send_nsca. I 
> also tried the current CVS 
> (http://nagios.sourceforge.net/download/cvs/nsca-cvs.tar.gz) but same 
> thing.
>
> Incidentally, with the CVS snapshot (version 2.5?) I kept getting this 
> error in syslog when trying to start nsca:
>
> Jan 21 23:09:47 bell nsca[22258]: Unknown option specified in config 
> file '/Users/nagios/nsca/nsca.cfg' - Line 2
>
> Line 2 is my allowed_hosts declaration. I tried both hostnames, and IP 
> addresses as the changlog mentioned that it supported hostnames now. I 
> had to comment line 2 out and it was able to start the 2.5 version.
>
> -- 
> Noah
>
>
> On Jan 21, 2004, at 4:07 PM, Noah Leaman wrote:
>
>> 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
>>
>
>
>
> -------------------------------------------------------
> 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



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