Upgrading NSClient++ from version 0.3.9 to 0.5.2.35

[rferebee]

Hello,

We're using a very old version of the NSClient++ and we'd like to upgrade it on all of our endpoints.

It appears however that the configuration files are completely different from our version to the updated one. Would it be possible for someone from Nagios to assist us in getting a new configuration file setup?

To be honest there is a lot going on in the new .INI file and we're not sure where to even begin.

Thank you.

[lmiltchev]

I would recommend that you follow the steps below:

1. Disable notifications in Nagios XI for this server while you are upgrading the agent, so that your contacts wouldn't get flooded with notifications.

2. Make a backup of the "old" NSClient++ config (NSC.ini) just in case you have some custom commands defined. You are correct - the syntax is different, so you may not be able to use the same commands in most cases, but at least you will have a reference point.

3. Make a backup of your old scripts, located in the NSClient++ directory, especially if you have some custom scripts

4. Remove the old agent.

5. Install the new one.

6. Run the command for generating all of the "default" settings to the nsclient.ini file from the CMD prompt (as administrator). You will find the command somewhere in the top section of the nsclient.ini file.

Example:

Code: Select all

cd "c:Program Files\NSClient++"
nscp settings --generate --add-defaults --load-all

Note: You may see an error or two - don't worry about it. Open the nsclient.ini file to verify that it has been populated with all of the default settings (it should contain a lot more directives now, after running the above command).

7. Enable all of the modules under the [/modules] section, that you would like to use, save, exit and restart NSClient++ service, so that changes can take effect.

8. Test to see if you can monitor your system via NSClient++ and check_nt/check_nrpe, etc. (whatever you are using). You can run a couple of commands from the CLI on the Nagios XI server to check things out:

Code: Select all

/usr/local/nagios/libexec/check_nt -H <client ip> -p 12489 -s <'password'> -v CLIENTVERSION
/usr/local/nagios/libexec/check_nrpe -H <client ip>

9. If basic checks are working fine, then you can try adding any "custom" command that you might have, and testing them.

10. Finally, enable notifications in XI, provided everything works as expected.

Let us know if you run into some issues. Thank you!

[rferebee]

Since we are paying for support, can't I give you our current config file and the new one and have you folks make it work for us?

As much as I'd love to figure it out myself, I really don't have the time dealing with all my Log Server issues.

[npolovenko]

@rferebee, Can you upload the old NSC.ini file as well the new nsclient.ini files in this thread? I will make the changes and send the new file back to you.

PS: Our forum support, for the most part, includes troubleshooting guidance and recommendations. What you're asking is something we usually do during remote sessions that require phone support, which is a paid option that will allow you to call us in during office hours and have our support technician work on your system live.

[rferebee]

Thank you! That would be fantastic. I'll PM you the files.

[npolovenko]

@rferebee, No problem. I pm'ed you the new nsclient.ini file. Please place it instead of the existing one and then restart the nsclient service from the windows services menu.
There is one problem. Many default modules used in the NSClient 0.3.9 were deprecated. But the newest NSClient has slightly different commands for most/all kinds of checks you were performing. So if you replace the nsclient.ini and some checks in XI are still failing with incorrect syntax you can find the correct commands in this KB article:
https://support.nagios.com/kb/category.php?id=186
And change them in the CCM.
If you're having trouble finding the correct version of the failing command please send the old command/service check definition from the CCM and I will give you the modified syntax to get it to work.

[rferebee]

This can be locked, thank you.