NRDS not syncing/updating on hosts

[jbennett]

I have recently noticed that my NRDS configs aren't updating on my clients after I make changes to the NRDS config files from within Nagios.

I've also noticed that I haven't been getting the updated check results on the time frame I have requested.

I manually went back and installed and configured the updated NRDS configs on a set of clients which then they started reporting within the time frame I had set the cront for.

I have two questions here:

A) Why wouldn't Nagios be pushing the updated configs out to my clients? (Nagios NRDS config was on version 2.4, while nrds.cfg on the client showed version 2.1.
B) Why wouldn't Nagios be getting the check results on the time frame I set them up for? Is it because there's a mismatch int eh config versions?
C) How can I monitor this in the future to make sure we are using the correct configs and are getting the check results in the time frame I'm requesting them in?

[lmiltchev]

A) Why wouldn't Nagios be pushing the updated configs out to my clients? (Nagios NRDS config was on version 2.4, while nrds.cfg on the client showed version 2.1.

Have you made any changes on the server or on the client machine?

B) Why wouldn't Nagios be getting the check results on the time frame I set them up for? Is it because there's a mismatch int eh config versions?

It is possible.

C) How can I monitor this in the future to make sure we are using the correct configs and are getting the check results in the time frame I'm requesting them in?

We need to find out what is causing this first in order to prevent it from happening in the future.

Run the following commands:

on the server:

Code: Select all

tar zcvf server-configs.tar.gz /usr/local/nrdp/configs

on the client:

Code: Select all

tar zcvf client-nrds.tar.gz /usr/local/nrdp/clients/nrds

Email us both, the "server-configs.tar.gz" and the "client-nrds.tar.gz" files that were generated by the above commands at [email protected]. Put "NRDS not syncing/updating on hosts" in the subject line.

[scottwilkerson]

A & B) This comes down to understanding how NRDS works. NRDS doesn't "push" configs, what actually happens is the agent installed on the client "requests" newer versions of the config when it runs. If it is a *nix system NRDS should be running on cron. If it is a Windows system, it should have a task scheduled. So this makes sense that you were not getting results at the same time you were not getting updates.

C) What most people do is is setup freshness checking on the passive checks alerting if a check hasn't been received since XXX seconds

[jbennett]

Email us both, the "server-configs.tar.gz" and the "client-nrds.tar.gz" files that were generated by the above commands at [email protected]. Put "NRDS not syncing/updating on hosts" in the subject line.

Done.

C) What most people do is is setup freshness checking on the passive checks alerting if a check hasn't been received since XXX seconds

With the number of service checks and hosts on our system, using the bulk update tool is my only real option here. I have enabled freshness checking on all of them, but without going into each one manually and setting a time, I can only hope that the system will determine this value automatically, as the documentation states. Is this the case?

[lmiltchev]

A new ticket has been open in our ticketing system. We will continue communicating via email. I am lock this thread.