NRDS Questions

[jbennett]

Since we have a new build going out soon, I'm working to implement a number of new service checks. It appears that NRDS is the smartest option here, but I'm still trying to wrap my head around it.

Currently, we have a number of checks being executed via NRPE on our old servers.

I have a server that I am testing on and I'm wondering if I can just copy and paste the current checks that are in the NRPE.cfg file into the config that I can create via the NRDS Config manager?

These checks are all currently located in the /usr/local/nagios/libexec folder and are called by NRPE.

Can someone please help me understand if I am approaching this in the correct manner?

I have created the config on the Nagios server and have followed the instructions to install it on the server I would like to monitor. In doing so, I get the following:

Code: Select all

 # ./installnrds xxx.xxx.xxx.xxx 1
nagios group already exists.
nagios user already exists.
Installing NRDS Client

Adding cron jobs for xxx.xxx.xxx.xxx at a 1 minute interval

no crontab for nagios
Crontabs installed OK
Updating config and plugins
curl exited with error 1536
Installation complete

Should I be concerned with the curl execution error?

[sreinhardt]

That curl error is from the client attempting to contact and update its configs from the remote server. 1536 means that curl was unable to complete an nslookup on that server name.

[jbennett]

That curl error is from the client attempting to contact and update its configs from the remote server. 1536 means that curl was unable to complete an nslookup on that server name.

Just so that I can make sure I understand - you're saying that curl couldn't get out to check for updates. Not that the server that i'm attempting to monitor can't communicate to the Nagios box, correct?

[sreinhardt]

Actually no I do believe this would be curl having issues resolving the name of the nagios box. Very similar to the issue last noted in your other thread.

[jbennett]

Actually no I do believe this would be curl having issues resolving the name of the nagios box. Very similar to the issue last noted in your other thread.

Many thanks! I've been able to get the checks to work successfully, now I just need to work on the lookup issue and I think it will solve the rest of the issues.

[scottwilkerson]

Yes, you will need to make sure that the machine can resolve the name of the XI server ser in the URL field of the NRDS Config Manager, either by adding an entry in /etc/hosts or via the DNS server they are using