NSClient++ Help (#1) - Multiple installs [SOLVED] (#509) - Message List
Hi there, I am looking to install NSClient++ for Nagios for Windows on my network which consists of about 200 Windows clients. I use RemoteExec? from ISDecisions normally for deployments like this. Unfortunately, I have not been abke to find a way to use the MSI options succesfully. Please could you help me to determine a way to do this - I also do not want to install the Firewall or documenttion on the clients. I appreciate any input. Jeff
-
Message #1573
Anyone?
Jeff02/18/10 08:16:15 (3 years ago)-
Message #1574
Jeff,
The firewall option in the installer does nothing more then adding an exception. If, like on most servers, the firewall/ICS service is not running, you will get an error telling you that the firewall exception could not be made. Clicking OK makes it go away and the installer will complete just fine...
For documentation, you would have to check, but my bet is that the installer just copies the files to the harddrive. When the installer completes, you can use a script to delete these files as well as copy the NSC.ini so that all servers have the correct settings.
PS. be sure to restart the service after editing/replacing/whatever the NSC.ini nsclient++.exe -stop nsclient++.exe -start
mike2k02/18/10 08:31:13 (3 years ago)-
Message #1575
Thanks for that. What I was hoping for was a script / batch file that I can run over 200 clients to silently install the nagios client. I have tried various permutations and none have worked. I have treid the .msi with all the options I think. I also tried according to the documentation, by copying the installation files, running the exe with /install etc. Unfortunately this worked, but my Nagios server did not recognise any client installed this way. Only when I manually installed the client using *.msi did the Nagios server recognise the client. I really don't want to go through 200+ servers and install Nagios manually. Is there another way?
Jeff02/18/10 08:38:43 (3 years ago)-
Message #1576
Have you looked at this: http://nsclient.org/nscp/wiki/doc/installation/manual You can create a script that: 1) copies the necessary files to the client 2) installs the service 3) possibly adds an exception to the firewall 4) starts the service
I think that's the way to go... Do not forget to create a proper NSC.ini
From the manual: The configuration file (NSC.ini) NEEDS to be configured as for security reasons all plug-ins are disabled by default. The reason for this is so no one will accidentally install this and get potential security issues, I believe that things should be "off" by default. Also notice that by default allowed_hosts are 127.0.0.1 so you need to modify this as well.
mike2k02/18/10 09:16:38 (3 years ago)-
Message #1577
Thanks Mike - and that is exactly what I tried. Unfortunately the Nagios Server did not recognise the clients I installed that way...
Jeff02/18/10 10:06:01 (3 years ago)-
Message #1578
Okay, could you try that method again and post your nsclient log after restarting the nsclient service?
mike2k02/18/10 12:27:05 (3 years ago)-
Message #1579
Where do I find that?
Jeff02/18/10 13:19:49 (3 years ago)-
Message #1580
It's in your nsclient folder. Typically: c:\Program Files\NSClient++\
mike2k02/18/10 13:24:25 (3 years ago)-
Message #1581
I thought so, but its not there. I am not going to be back until Sunday, so I will get back to you then. I really appreciate your help - have a good weekend.
Jeff02/18/10 13:49:12 (3 years ago)-
Message #1582
Wow... people actually helping out with support... wicked!! :) (and that means thanks!!!)
The firewall exception I apparently need to fix, I though it was fixed in the last release. You can (also) configure the MSI packade quite a lot telling it what to do so that is an option, but requires knowhow of how to do that (somthing I actually do not have).
I would (as previously suggested) suggest "nsclient++ /install" (or even possibly adding the service entry manual. Quick easy and works.
Michael Medin
mickem02/18/10 16:17:47 (3 years ago)-
Message #1586
Also, Jeff, if you are unable to locate you nsclient.log, make sure logging is enabled in you NSC.ini.
By default it looks like this:
[log] ;# LOG DEBUG ; Set to 1 if you want debug message printed in the log file (debug messages are always printed to stdout when run with -test) ;debug=1 ; ;# LOG FILE ; The file to print log statements to ;file=nsclient.log ; ;# LOG DATE MASK ; The format to for the date/time part of the log entry written to file. ;date_mask=%Y-%m-%d %H:%M:%S ; ;# LOG ROOT FOLDER ; The root folder to use for logging. ; exe = the folder where the executable is located ; local-app-data = local application data (probably a better choice then the old default) ;root_folder=exe
If you don't specify a root folder, nsclient will use it's install directory.mike2k02/19/10 13:37:14 (3 years ago)-
Message #1593
Hello to the NSClient team. Thanks for all the input. I have configured the log as you said and when I start the service (using nsclient++ /start) I cannot find the log file anywhere.
My config looks like this:
[log] ;# LOG DEBUG ; Set to 1 if you want debug message printed in the log file (debug messages are always printed to stdout when run with -test) debug=1 ; ;# LOG FILE ; The file to print log statements to file=nsclient.log ; ;# LOG DATE MASK ; The format to for the date/time part of the log entry written to file. date_mask=%Y-%m-%d %H:%M:%S ; ;# LOG ROOT FOLDER ; The root folder to use for logging. ; exe = the folder where the executable is located ; local-app-data = local application data (probably a better choice then the old default) root_folder=local-app-data
Looking forward to resolving this.
Jeff02/22/10 09:27:56 (3 years ago)-
Message #1595
Problem Solved
Feel like such an idiot - the copy command was not copying the "modules" directory. Nothing was working, not even the log. Once I copied the folder over, the Nagios Server registered the client and there was a log, and all was right with the world.
I want to thank you guys for your support. Now that I can deploy, I will be an avid Nagios and NSClient user!
Jeff02/22/10 10:44:26 (3 years ago)-
Message #1596
One last question - how can I install (using nsclient++ /install) without installing the firewall module?
I saw in the readme that version 0.37 "* Added "firewall exception" to installer"
Please let me know...
Jeff02/22/10 11:01:50 (3 years ago)-
Message #1615
nsclienht++ /install wont add any firewall exceptions. Firewall exception comes from the MSI installer (and can be disabled with a tick-box)
Michael Medin
mickem02/26/10 07:05:08 (3 years ago) -
Message #1598
Jeff,
Glad to hear you solved it.
As I explained to you before, the firewall module does nothing else then adding an exception to your firewall for port 5666 (default nrpe). If you're installing nsclient on a server (Server 2003) the firewall option won't do anything because the OS' firewall is disabled.
If the firewall is enabled, you would need the exception otherwise your checks won't work, so why would you want to exclude it ?mike2k02/23/10 08:44:43 (3 years ago)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
