Page 1 of 1

Issues regarding Nagios configuration update

Posted: Fri May 25, 2018 3:30 am
by AHugon
Hello all,
I'm a beginner regarding Nagios and i'm encoutenring an issue on a Nagios installation i'm maintaining.
I hadn't encountered this issue before.

My nagios is as follows.
I have an "Hypervisor" whose is recieveing checks from two remote nagios servers.
These two remotes nagios servers send their checks via NSCA to my Hypervisor.

After updating and checking my config files i have to reload Nagios to update the configuration in the system.

And this is what happens :
Image

NSCA is running, my Nagios process is running, everything should be fine.
And i don't know where to start.

Re: Issues regarding Nagios configuration update

Posted: Fri May 25, 2018 11:02 am
by mcapra
Which version of NSCA is being used? That's not an error message I recognize from either NSCA or Nagios Core.

Are there special scripts/binaries being used to handle the NSCA transmission? Something other than the official send_nsca client?

Re: Issues regarding Nagios configuration update

Posted: Fri May 25, 2018 12:36 pm
by scottwilkerson
thanks @mcapra

Re: Issues regarding Nagios configuration update

Posted: Mon Jun 04, 2018 7:05 am
by AHugon
Regarding the NSCA versions :
Serverside and clientside : 2.7.2

On the server we use xinetd with NSCA.
On our clients we use the standard NSCA client.

Re: Issues regarding Nagios configuration update

Posted: Mon Jun 04, 2018 10:18 am
by scottwilkerson
What is the error you are getting?

Re: Issues regarding Nagios configuration update

Posted: Mon Jun 04, 2018 12:32 pm
by mcapra
Here's a more forum-friendly version of the image:
2d12486b8ee5ebfaa018517e3ea78339.png
2d12486b8ee5ebfaa018517e3ea78339.png (3.93 KiB) Viewed 2024 times

Re: Issues regarding Nagios configuration update

Posted: Mon Jun 04, 2018 1:57 pm
by scottwilkerson
If I had to guess the data isn't getting passed to the Nagios server and freshness checking is enabled reporting this.

In order for us to be of assist we would need to see what is kicking off the NSCA command from the remote machine and what the result of running that command is.