NagiosXI Distributed monitoring with outbound transfer

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
Andreas_c_Schmidt
Posts: 23
Joined: Mon Sep 24, 2012 10:03 am

NagiosXI Distributed monitoring with outbound transfer

Post by Andreas_c_Schmidt »

Were using 2 NagiosXI Servers (Centos) where a slave server is reporting its monitored services via nsca to our master which has all the services as passive.

On the slave all services (131) are checked every 5 minutes and reported as OK. I configured the outbound / inbound via nsca and opened the firewall.

However when I go to the master-server it seems that I receive a status only for about 40 of them.

I run a test and created a new host with 30 services (snmp). Waiting on the Master for the unconfigured objects I get only 7 new objects (waiting for at least 24 hours).

I enabled debug on the master and had a look into the messages where I see only those 7 services in the messages log.

There seems to be no real documentation and troubleshooting for the outbound transfer. How can I log what is going out from the Slave and or trigger all services to go out.
I can reach the port with telnet and I can manually send a service check.
yancy
Posts: 523
Joined: Thu Oct 06, 2011 10:12 am

Re: NagiosXI Distributed monitoring with outbound transfer

Post by yancy »

Andreas,

Here's some basic information on outbound transfers
http://assets.nagios.com/downloads/nagi ... ith_XI.pdf

Further NSCA documentation
http://nagios.sourceforge.net/download/ ... _Setup.pdf

The NSCA deamon logs to /var/log/messages. You can increase the verbosity of the log messages by enabling debug (debug=1) as described in the NCSA documentation.


Hopefully that helps.

-Yancy
Andreas_c_Schmidt
Posts: 23
Joined: Mon Sep 24, 2012 10:03 am

Re: NagiosXI Distributed monitoring with outbound transfer

Post by Andreas_c_Schmidt »

The logs were not really helpful since all they did was telling me that the nsca is not sending messages.

We fixed the issue by downgrading the build in NSCA server and client Version 2.9.1 to 2.7.2 on both servers.

Seems like a major bug /feature in 2.9.1 since I was able to reproduce it in my lab.
Locked