{"id":265,"date":"2012-01-29T14:36:34","date_gmt":"2012-01-29T22:36:34","guid":{"rendered":"https:\/\/digitalcardboard.com\/blog\/?p=265"},"modified":"2012-06-25T12:11:29","modified_gmt":"2012-06-25T20:11:29","slug":"upgrading-to-nconf-1-3-0-on-ubuntu-11-10-oneiric-ocelot","status":"publish","type":"post","link":"https:\/\/digitalcardboard.com\/blog\/2012\/01\/29\/upgrading-to-nconf-1-3-0-on-ubuntu-11-10-oneiric-ocelot\/","title":{"rendered":"Upgrading to NConf 1.3.0 on Ubuntu 11.10 Oneiric Ocelot"},"content":{"rendered":"

Congrats to the NConf crew for reaching the 1.3.0 milestone! Two years in the making, but I’m excited to see the project continuing to move forward.<\/p>\n

It’s been over a year since I originally installed and configured Nagios and NConf 1.2.6 on my Lucid Lynx server<\/a>. In the meantime, I’ve upgraded the hardware and moved to Ubuntu 11.10 Oneiric Ocelot, mostly to keep up with the current releases. Not a whole lot has changed for what I use this server for, but keeping up with the Nagios releases in the repos has been convenient.<\/p>\n

If you’re following along with this guide but starting fresh with Nagios and Nconf, you’ll probably want to take a look at my previous guide<\/a>\u00a0and the\u00a0NConf installation documentation<\/a> to get some background information. I’ll try to provide some notes for those of you doing a fresh install, but since I’m just upgrading, I can’t make any promises.<\/p>\n

Backups!<\/h2>\n

Log into your server and make them backups!<\/p>\n

sudo cp -rp \/var\/www\/nconf \/var\/www\/nconf.bak\r\nmysqldump -u root -p nconf > ~\/nconf_sql.bak<\/pre>\n
I also backed up my Nagios configs<\/p>\n
sudo cp -rp \/etc\/nagios3 \/etc\/nagios3.bak<\/pre>\n
Download and Unpack<\/h2>\n
Wget or otherwise download the latest version on Nconf<\/a>. Wget has that issue with following SourceForge links so you may need to rename the file.<\/p>\n
Unpack the files and then copy them to where you installed NConf before, or do it all in one step:<\/p>\n
sudo tar xzvf nconf-1.3.0-0.tgz -C \/var\/www<\/pre>\n
Then fix the permissions for the NConf folder, setting them back to your apache user:<\/p>\n
sudo chown -R www-data:www-data \/var\/www\/nconf<\/pre>\n
Upgrade<\/h2>\n
Browse to http:\/\/<yourserver>\/nconf\/UPDATE.php<\/em><\/p>\n
Follow the prompts to proceed with the interactive update. NConf’s documentation on the update process<\/a> has screenshots that I won’t repost here.<\/p>\n
After the upgrade, you’ll need to remove some files and folders. Browse to your NConf folder and nuke them. I also had to remove the call_ajax.php<\/em> file, which wasn’t in the original documentation.<\/p>\n
cd \/var\/www\/nconf\r\nsudo rm -rf INSTALL\/ UPDATE\/ INSTALL.php UPDATE.php call_ajax.php<\/pre>\n
There’s been a few changes\/additions to the NConf conf file, so open up config\/nconf.php<\/em> and add the following lines:<\/p>\n
define('CHECK_UPDATE', 1);\r\ndefine(\"DEBUG_GENERATE\", 3); # [1=ERROR|2=WARN|3=INFO|4=DEBUG|5=TRACE]\r\ndefine('CHECK_STATIC_SYNTAX', 1);<\/pre>\n
Also, set the ALLOW_DEPLOYMENT<\/em> variable to 1 to enable deploying configs directly from NConf and comment out the other CONF_DEPLOY_<\/em> variables, as they aren’t used anymore.<\/p>\n
define('ALLOW_DEPLOYMENT', 1);\r\n#define('CONF_DEPLOY_URL', \"https:\/\/webserver.mydomain.com\/incoming_config.php\");\r\n#define('CONF_DEPLOY_USER', \"deployUser\");\r\n#define('CONF_DEPLOY_PWD', \"deployPass\");<\/pre>\n
At this point, you should be able to log into NConf 1.3.0 and look around.<\/p>\n
Migrating Deployment<\/h2>\n
With NConf 1.2.6, I used the ADD-ONS\/deploy_local.sh<\/em> script and a cron job to deploy configuration changes to Nagios. In 1.3.0, they’ve integrated this a little better into the core of the application, but it required some adjustment in my setup.<\/p>\n
Start off by coping the deployment.ini sample configuration file to the config folder:<\/p>\n
sudo cp \/var\/www\/nconf\/config.orig\/deployment.ini \/var\/www\/nconf\/config\/deployment.ini<\/pre>\n
Open up the config\/deployment.ini<\/em> file, uncomment the LOCAL deployment<\/em> section except<\/strong> for the [copy nagios.cfg]<\/em> section and change the target_file<\/em> variables to reference the nagios3<\/em> folder where Ubuntu places the config files.<\/p>\n
Also, add the reload command (sudo \/etc\/init.d\/nagios3 reload)<\/em> at the bottom of the [copy global config]<\/em> section. When you’re done the file will look similar to the following:<\/p>\n
;; LOCAL deployment ;;\r\n\r\n[extract config]\r\ntype = local\r\nsource_file = \"\/var\/www\/nconf\/output\/NagiosConfig.tgz\"\r\ntarget_file = \"\/tmp\/\"\r\naction = extract\r\n\r\n[copy collector config]\r\ntype = local\r\nsource_file = \"\/tmp\/Default_collector\/\"\r\n;target_file = \"\/etc\/nagios\/Default_collector\/\"\r\ntarget_file = \"\/etc\/nagios3\/Default_collector\/\"\r\naction = copy\r\n\r\n[copy global config]\r\ntype = local\r\nsource_file = \"\/tmp\/global\/\"\r\n;target_file = \"\/etc\/nagios\/global\/\"\r\ntarget_file = \"\/etc\/nagios3\/global\/\"\r\naction = copy\r\n; *** add the line below\r\nreload_command = \"sudo \/etc\/init.d\/nagios3 reload\"<\/pre>\n
; *** keep this section and the rest of the file commented out\r\n;[copy nagios.cfg]\r\n;type = local\r\n;source_file = \"\/tmp\/static_cfg\/nagios.cfg\"\r\n;target_file = \"\/etc\/nagios\/nagios.cfg\"\r\n;action = copy\r\n;reload_command = \"sudo \/etc\/rc.d\/init.d\/nagios reload\"<\/pre>\n
This process replaces the deploy_local.sh script, but we’ll need to allow the web user to issue the Nagios reload. To do that, we need to modify the sudoers<\/em> file:<\/p>\n
sudo visudo<\/pre>\n
Then add the following lines:<\/p>\n
# Allow www-data (apache) user to reload nagios\r\nwww-data ALL=NOPASSWD: \/etc\/init.d\/nagios3 reload<\/pre>\n
Save and quit.<\/p>\n
Finally, remove the entry in the root crontab entry that launched the old deploy script:<\/p>\n
sudo crontab -e<\/pre>\n
And remove the line reading:<\/p>\n
* * * * * \/var\/www\/nconf\/ADD-ONS\/deploy_local.sh<\/pre>\n
Deployment Testing and Cleanup<\/h2>\n
Let’s make sure the new deployment procedure works. Back in the NConf GUI, click Generate Nagios config<\/em>. You should hopefully see something like:<\/p>\n
[INFO]  Starting generate_config script\r\n[INFO]  Generating global config files\r\n[INFO]  Generating config for Nagios-collector 'Default Nagios'\r\n[INFO]  Ended generate_config script<\/pre>\n
If the config files generate successfully, you’ll see a button aptly labeled ‘Deploy’<\/em>.<\/p>\n
Click\u00a0Deploy, <\/em>and with any luck you’ll be presented with three OK messages in NConf \u00a0and your Nagios Event Log should show a SIGHUP message.<\/p>\n
Relax, and enjoy some JQuerified NConf 1.3.0 goodness! Gold star!<\/p>\n
I did notice that the original deployment method left a bunch of old config tgz bundles, so if you’re feeling like cleaning those up, just remove the whole lot:<\/p>\n
sudo rm \/var\/www\/nconf\/output\/NagiosConfig.tgz.*<\/pre>\n
Update (6\/25\/12):<\/strong> You’ll want to remove the\u00a0extended_host_info.cfg<\/strong> and\u00a0extended_service_info.cfg<\/strong> files from your target config directory (\/etc\/nagios3\/Default_collector\/)<\/em>, or you might get weird problems trying to deploy later on. I just found this out six months later.<\/p>\n
Troubleshooting Notes<\/h2>\n