Solved

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

Posted on 2008-06-24
8
2,763 Views
Last Modified: 2012-06-21
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..
0
Comment
Question by:IT-Reactrix
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 
LVL 2

Expert Comment

by:thefaza
ID: 21863751
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)
0
 
LVL 2

Expert Comment

by:thefaza
ID: 21863785
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
0
 

Author Comment

by:IT-Reactrix
ID: 21867630
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??
0
Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

 
LVL 2

Expert Comment

by:thefaza
ID: 21872163
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)
0
 

Author Comment

by:IT-Reactrix
ID: 21880607
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





0
 
LVL 2

Expert Comment

by:thefaza
ID: 21881469
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
0
 
LVL 2

Accepted Solution

by:
thefaza earned 125 total points
ID: 21895614
One more thing:
check if in nrpe.cfg in section Allowed_Hosts You have address of your Nagios server
allowed_hosts=IP_of_your_nagios_server
0
 

Author Closing Comment

by:IT-Reactrix
ID: 31470434
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.
0

Featured Post

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Every server (virtual or physical) needs a console: and the console can be provided through hardware directly connected, software for remote connections, local connections, through a KVM, etc. This document explains the different types of consol…
Learn about cloud computing and its benefits for small business owners.
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question