NAGIOS NSCA problem solved but still don

[Stephan Janosch]

jdragone at pictage.com.ar wrote:
> Hi

Hi too!

> 
> Dec 30 17:41:12 monitor2 nsca[662]: Handling the connection...
> Dec 30 17:41:13 monitor2 nsca[662]: SERVICE CHECK -> Host Name: 'Host',
> Service Description: 'Service', Return Code: '0', Output: 'PerformanceData'
> Dec 30 17:41:13 monitor2 nsca[662]: End of connection...
> 
> Now my new question is: where this data is going to?

In regular case, the data is written into the COMMAND FILE of nagios. 
nagios checks this file regulary for entries and these entries are added 
to the general result queue.

> 
>    ls -la /usr/local/nagios/etc/nsca.cfg
>    -rw-r--r--    1 nagios   nagios       5199 Dec 29 21:02
> /usr/local/nagios/etc/nsca.cfg
> 
>    lsof | grep nagios.cmd
>    nagios    24899     root    6r  FIFO        3,2             1844163
> /usr/local/nagios/var/rw/nagios.cmd
> 
> I've reading into nsca.c source file, but could not find for any clues to 
> where nsca is sending its received data.
> 
> vi /usr/local/nagios/etc/nsca.cfg:
> 
> command_file=/usr/local/nagios/var/status.log

There seems to be an error. Why you configure nsca to write into the log 
file instead writing into the command file. Try this line:
command_file=/usr/local/nagios/var/nagios.cmd (or adjust the path to 
nagios.cmd).

> alternate_dump_file=/usr/local/nagios/var/rw/nsca.dump
> debug=1
> aggregate_writes=1
> append_to_file=1
> 
> 
> 
> Regards
> 
> 
>     Jose Dragone
> 

Stephan



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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