Nagios Support Forum

Hi Team,

we configured Linux hosts and services with NRDS, now we are getting alert from client, but if client is totally shutdown, we are not getting any alert, even we are not getting system or services down on nagiosxi console.
Always it is showing OK stat.

Is there any way to see on nagiosxi, that (NRDS installed client) system is down.

Agents using NRDS send passive check results to Nagios, so Nagios has no control over when the checks come in. As a result, you have to enable Freshness Checks on that host. Freshness Checks allow you to force an active check on a host that should be sending passive results but is not. You can configure the check to be run and how long a host needs to go without sending a result before you force the active check.

Take a look at this document starting on page 3: http://assets.nagios.com/downloads/nagi ... ith_XI.pdf

Hi tmcdonald,

Thank you very much for your valuable reply.
We configured NRDS and set freshness value, on service template of xiwizard_passive_service.
We set freshness threshold 500 seconds, enable freshness, and set check attempts 3 times, then apply configuration, now we are getting passive checks along with active checks, if client is totally shutdown, we are getting "CRITICAL: client not responding......".

am i getting right what you told or something other configuration we need to do.

Will it work for long time?

If I understand you correctly, it sounds like you are getting passive checks while the host is alive, and when it goes down you get active checks which show it as down? If this is the case, that is what should be happening.

Hi tmcdonald,

sorry for late replying,

We configured NRDS on 2000 servers for passive checks, and 2500 hosts with active checks including 100 NRPE, we were facing issue with passive check alert when host down.
so that as you told we configured freshness checks.

please check the attached nagios.cfg file for freshness check, apart from this we configured host and service template for passive checks,
xiwizard_passive_host

xiwizard_passive_service

----------
My query is we are getting high latency and active checks are not shown monitoring engine statistics: Please let me know what i need to do.

You pose two statements here:

we were facing issue with passive check alert when host down.

My query is we are getting high latency and active checks are not shown monitoring engine statistics: Please let me know what i need to do.

Are they related? If not we will need to work on one at a time. First, we need more information on the alert problems, what is the actual issue?

Dear Sir,

Sorry, but yes both related,

1. "we were facing issue with passive check alert when host down".---->

due to this issue we configured freshness check, now we are getting high latency host and service latency is 4500 seconds.

if we removed freshness check from nagios.cfg file then we are getting host and service latency less than 60.

thanks in advanced.

Adding freshness is like adding additional active checks. You have a large setup, so you will need to use a large freshness threshold, otherwise you will have latency issues. It's a trade-off.

The latency issue is most likely because of the freshness checking being enabled globally. This is generally not a very good idea if you are running active checks along side your passive checks due to the drastic reduction in time between checks. Why did you enable freshness checking because of your critical alerts? It is generally used to run a dummy check which would output status information along the lines of "no passive results received" so that you know if your hosts are not returning up to date information.

Hi Sir,


I dont want to used globally freshness check, i want to enable freshness only for NRDS client which is sending passive result to nagiosxi server.

we have enabled in host and service templates, is it necessary to enable checks on nagios.cfg file globally?