NRDS Pushing updated Check Routines

[jbennett]

I'm curious to know what the paramaters are that push the updated check routines out to hosts once they are updated on the Nagios server.

We have noticed that even though a check will be updated on the nagios server (custom checks that we are running), many times they will not be automatically pushed out to the necessary hosts until I make a change to the check command in the NRDS config.

Is this functioning as normal or am I missing something?

[scottwilkerson]

It checks the Version number in the NRDS Config Manager.

If you need to force an update of the plugins to the remote machines you can open the config in the NRDS config manager, and just click Save on the bottom.

The config version # will change and the next check the remote machines will get the new config

[jbennett]

Ok. So even if the check script its self is updated (check_services for instance), it won't be pushed out unless the version on the nrds.cfg file is different? That explains it then.

[scottwilkerson]

That is correct.

The flow goes like this on the clients

When the cron or scheduled task runs, the client asks the server if there is a newer version of their config, and sends their current config version #
If their is a newer version, NRDS will download the new version and then parse the config to determine needed plugins, and then download them.

If there isn't a newer version, it will just process the existing checks in its config.