asked on

How do I start Nagios Remote Plugin after IP address has been changed?

After changing IP address and rebooting our Windows 2003 server, the Nagios Remote Plugin will not start. Getting error: "Services: Could not start the Nagios Remote Plugin Executor for NT/W2k service on Local Computer. Error 10049: The requested address is not valid in its context."

Nagios is listening on port 5666 on the Windows 2003 server and noticed that this port is not showing when issuing command: netstat -an. How do I manually add this port so that Nagios will start? Or how do we restart Nagios without adding this port. I believe 5666 is a dynamic port so it should kick in when it is being called, but at this point, it is not..

thefaza

1. Check nrpe.cfg file if everything is ok
2. try to uninstall nrpe service: nrpe_nt.exe -u and install it again nrpe_nt -c nrpe.cfg -i
3. You can also try ssl version as well as non-ssl version (switches -i -n)

thefaza

I made mistake: dont use -c together with -i
for installing service (ssl version) use: nrpe_nt.exe -i
or non-ssl version: nrpe_nt.exe -i -n
for starting nrpe use: nrpe_nt.exe -c nrpe.cfg

IT-Reactrix

ASKER

Still getting "CHECK_NRPE: Socket timeout after 10 seconds. " for all the services it is monitoring on Nagios. This may just take time to refresh. I found that the ip address on nrpe.cfg was incorrect. Changing that enabled the NRPE_NT service. Now if Nagios can only see it as OK we should be good to go. Or should I reboot the client to reflect the change??

thefaza

There can few causes of this error:
1. firewall settings on client
2.nrpe_nt.exe service is not started
3. pure network connection so the timeout 10 seconds is not enaugh: try to run check_nrpe command with switch: -t 30 (it will increase the timeout to 30 seconds)

IT-Reactrix

ASKER

thefaza:
1) firewall is not enabled.
2) nrpe_nt is running now after correcting ip address on nrpe.cfg.
3) I don't see check_nrpe command available on the bin folder.

I tried starting service on your previous suggestion with command: nrpe_nt.exe -c nrpe.cfg I got a list about nrpe and year it was made followed by the proper syntax to run nrpe. I'm thinking the command did not enable the service. So I manually started nrpe via services.msc. Checking nrpe.log shows the following: Looks promising but Nagios still shows "CHECK_NRPE: Socket timeout after 10 seconds."

2008-05-26 19:17:13; 2620; 7;Loaded config from: C:\Program Files\nrpe_nt.0.8-bin\bin\nrpe.cfg
2008-05-26 19:17:13; 2620; 7;Starting server thread...
2008-05-26 19:17:13; 5304; 7;Binding to 10.5.12.30
2008-05-26 19:17:13; 5304; 6;Listening on port 5666

thefaza

check_nrpe should be on Nagios server (default location is /usr/local/nagios/libexec/check_nrpe), this error: "CHECK_NRPE: Socket timeout after 10 seconds."
is just from check_nrpe command. Check_nrpe try to contact nrpe_nt service on monitored machine
Try to manually start check_nrpe command on Nagios server: check_nrpe -H MONITORED_HOST -t 30
read this document, it should help you: http://nagios.sourceforge.net/docs/nrpe/NRPE.pdf

ASKER CERTIFIED SOLUTION

thefaza

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

IT-Reactrix

ASKER

Thank you thefaza. It is both nrpe.cfg you mentioned above and the ip on the client need updated in our Nagios server to fix this issue.