unable to monitor windows system through nagios server
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
unable to monitor windows system through nagios server
Hi, I am unable to monitor windows system through nagios server it's showing error that name or service not known.
THINGS THAT I HAVE DONE
CLIENT: Installed nsclient++ and edited .ini filea and started the service.
SERVER: Edited windows.cfg file,commands.cfg,nagios.cfg. In commands.cfg file I have metioned the hostaddress and password of the system in check_nt. Please help me in resolving the issue.
I've seen issues with this to a variety of reasons including misconfigured NSC.ini on the windows client, firewall blocking the port from Nagios master on the windows client, incorrect entries on the Nagios server etc...
For troubleshooting I'd suggest:
1) First verify your host is resolving the client IP correctly from Nagios master:
host <client>
Verify that the IP returned is the same one you defined for the client in hosts.cfg.
2) On the Nagios master from command line attempt to connect to the port on the windows client to verify you can. This will help you determine if issue is networking/firewall - often folks turn on the Windows firewall and forget to open up the port.
e.g. of you're using nsclient++ in NRPE mode and standard port then try "telnet <client> 5666".
3) From command line on the Nagios master attempt the command to the client.
e.g./usr/local/nagios/libexec/check_nrpe -H <client> -p 5666 -c CheckCPU -a warn=85 crit=90 time=30
This will help you see if the command you think is running is working and bypass all the the rest of the Nagios setup. If it works then you know your issue is the Nagios configuration - if it doesn't then it is likely something on the client side.
4) Review the NSClient++ log on the client. Usually it gives rather good indications as to where the issue is so long as networking/firewall allowed the master to talk to the client.
Failing all that you'd need to provide your NSC.ini, your hosts.cfg for this client, your services.cfg for this client and your commands.cfg for the commands used for this client for anyone to intelligently tell you what issues you might have.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.