NSCA Install/Config

[joerg.helmert at aracomp.de]

Hi David,

Are you sure nsca is running?

To daemonize you should run: ./nsca -c nsca.cfg --single
                         or: ./nsca -c nsca.cfg --daemon

Or you should use inetd or xinetd if you don't like running nsca in daemon
mode.
Read README which comes with nsca. Contains further info on this.

I just installed nsca today. I use the init-script, which comes with nsca.

Works very well.

Bye,

Joerg




-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of David Barnett
Sent: Thursday, February 26, 2004 4:58 PM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] NSCA Install/Config


Can someone please help walk me through the steps of installing NSCA on both
the client and the nagios server?  Here is what I have done so far:

On client:
I've downloaded the nsca add-on and try to run the following command:
send_nsca -H 10.0.10.124 -c send_nsca.cfg, but I get the error:
Error: Server closed connection before init packet was received
Error: Could not read init packet from server

On server:
I downloaded the nsca daemon and ran ./nsca -c nsca.cfg.  I changed the
nsca.cfg file's allowed hosts to the host's ip address.  I also created a
service to listen for passive checks and with no check command.

How can I get the client to send the passive checks to the daemon running on
the server?  Thanks for any help.

David



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=click
_______________________________________________
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