Updating NConf to version

Today I found out that the NConf crew released version of their awesome Configuration utility for Nagios. If you read my last posts, you probably already know that I´m a big fan of that project. Of course I wanted to apply the update immediately – and ignored the warnings on the NConf page 😉

To say it right from the start: Updating NConf from version to is not a 5 minute process, since the NConf crew changed some major parts in the inheritance and architecture. Further information can be found here:  Nconf Release Notes
Now let´s get back to the Update process. Here´s what I did (based on the official tutorial Official NConf Update How-To)

  1.  Created backup of Nconf directory with
    cp -rp nconf/ nconf.BAK
  2. Create mysql dump of the nconf database with
    mysqldump -u DBUSER -p DBNAME > nconf-dbdump.sql
  3. Unpacked the nconf archive
    tar -zxf nconf-1.3.0-0.tgz
  4. Overwrote the existing Files
    /bin/cp -rv * /way/to/old/directory/of/nconf/
  5. Checked the permissions of the following folders in the nconf directory:
    /config  /output  /static_cfg  /temp
  6. Went to the URL of the local NConf webpage
    here you can just click “update page” and will be directed into the Update procedure.
    After that you will come to a point where this information comes up. Here you have to decide if you want to move on with your old configuration scheme or switch to the new one. I did the conversation and will probably report about my experiences in a later article.
  7. After finishing the process you will see a summary of the changelog. READ IT!
    Security issue with ‘call_ajax.php’:
    Please remove this file from your nconf/ directory.
    A replacement which is more secure has been implemented (‘call_file.php’). So I did:  rm call_ajax.php 
  8. Delete Update/Installation files.
    rm –r UPDATE*

    rm –r INSTALL*

I can proudly report that the update process works as described.

Changes I checked so far (see NConf page for highres Screenshots):

  •     Look & Feel is a little bit different
  •     You can define default service templates for checkcommands (Yey!)
  •    New “advanced service” section (not figured out yet)
  •     Inheritance of variables is visible
  •     First notification interval can be set
  •     Deployment module

I have to say that the overall feeling is more solid and trustworthy than I will write a more detailed report later.

Currently I´m trying to adapt my configuration to the new architecture, before exploring the new included deployment function. This one should replace my cronjob deployment.


About sitweak
Monitoring, Network, Firewall, Mobile Security. I´m totally into that stuff!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: