Page 1 of 1

Several Questions concerning upgrading to the 1.3 release

Posted: Fri Jan 06, 2012 23:10
by kaplan71
Hi there --

I was planning on installing the 1.3 release of NConf in place of the current 1.2.6 distribution, but prior to doing so, I had some preliminary questions:

1. If I decide to upgrade the existing directory, is the upgrade procedure designed to facilitate the process, or should I consider installing the newer version into another directory, doing an import, and making the necessary changes there?

2. Prior to doing anything, there is one outstanding issue with the 1.2.6 release. During the process of setting up everything, a large number of passive checks on services and hosts were inadvertently disabled. Is there a way to enable all the disabled checks without having to individually activate each host and service?

Thanks.

Re: Several Questions concerning upgrading to the 1.3 releas

Posted: Tue Jan 10, 2012 15:37
by agargiulo
1. If I decide to upgrade the existing directory, is the upgrade procedure designed to facilitate the process, or should I consider installing the newer version into another directory, doing an import, and making the necessary changes there?
Whenever possible you should do an update instead of doing an import. NConf maintains some additional data in its database that is not exported when you generate the config. If you start with a clean install of NConf and import your Nagios config, some information will be lost and you will have to set it again manually (I'm talking about certain attributes like "monitored by", "OS", "host-alive check" etc.). The update procedure will guide you step by step through the update process.
2. Prior to doing anything, there is one outstanding issue with the 1.2.6 release. During the process of setting up everything, a large number of passive checks on services and hosts were inadvertently disabled. Is there a way to enable all the disabled checks without having to individually activate each host and service?
I'm not sure what issue you're referring to exactly. Part of the logic of NConf is that if you set up a distributed environment with multiple Nagios instances, NConf will generate config files for each instance individually. Depending on what type of server you have chosen, the check will either all be active or all passive. This is a feature which has not changed in 1.3.0. So if you upgrade, passive check should still behave the same way.