Contents
Upgrading from previous Icinga releases
Upgrading from Nagios 3.x releases
Upgrading from Nagios 2.x releases
Upgrading from an RPM installation
Upgrading from previous Icinga releases
During development there may be cases where the handling of bugfixes might touch the userspace. We try to avoid this as far as possible but sometimes it is inevitable.
Icinga 0.8.0 to Icinga 0.8.1
Archived Logfilename
There was a small misspelling bug in Icinga 0.8.0 resulting in archived logfile names beginning with a capital "I" like in 'Icinga-$date'". This was fixed in version 0.8.1.
If you experience this problem then please use the following script to fix the file names
cd /usr/local/icinga/var/archives for oldfilename in `find ./ -name "Icinga-*"` do newfilename=`echo $oldfilename | sed -e 's/Icinga/icinga/g'` mv $oldfilename $newfilename done
Normal Icinga update path
Regular updates of Icinga should be possible just by re-installing Icinga using
./configure make all make install
Please keep in mind that you have to call ./configure using the same options as during the first time.
Upgrading From Nagios 3.x Releases
We try to be compatible with the configuration files of the current Nagios 3.x versions so there should be very little you have to do to "upgrade" from Nagios 3.x to Icinga 0.8.3. Assuming you've already installed Nagios from source code as described in the Nagios quickstart guide, you can install Icinga quite easily.
Make sure you have a good backup of your existing Nagios installation and configuration files. If anything goes wrong or doesn't work, this will allow you to rollback to your old version.
Please install Icinga according to the quickstart guide. Instead of using "make install-config" copy your configuration files from <Nagios-path>/etc/ to <Icinga-path>/etc/. Before starting Icinga you have to alter some things:
The filename of the main config file has changed from nagios.cfg to
icinga.cfg. mv nagios.cfg icinga.cfg
should be sufficient to change that
You have to edit the main config file (icinga.cfg) to change the directives named "nagios_user" and "nagios_group" to "icinga_user" and "icinga_group" respectively. Depending on the paths you're using you may have to change them as well.
Verify your configuration files and restart Icinga.
/usr/local/icinga/bin/icinga -v /usr/local/icinga/etc/icinga.cfg /etc/init.d/icinga restart
That's it - you're done!
Please keep in mind that
the URL has changed to http://localhost/icinga/
the name of the admin user has changed to icingaadmin
Upgrading From Nagios 2.x Releases
It shouldn't be too difficult to upgrade from Nagios 2.x to Icinga 0.8.3. The upgrade is essentially the same as what is described above for upgrading from Nagios 3.x releases. You will, however, have to change your configuration files a bit so they work with Icinga 0.8.3:
The old service_reaper_frequency variable in the main config file has been renamed to check_result_reaper_frequency.
The old $NOTIFICATIONNUMBER$ macro has been deprecated in favour of new $HOSTNOTIFICATIONNUMBER$ and $SERVICENOTIFICATIONNUMBER$ macros.
The old parallelize directive in service definitions is now deprecated and no longer used, as all service checks are run in parallel.
The old aggregate_status_updates option has been removed. All status file updates are now aggregated at a minimum interval of 1 second.
Extended host and extended service definitions have been deprecated. They are still read and processed by Icinga, but it is recommended that you move the directives found in these definitions to your host and service definitions, respectively.
The old downtime_file file variable in the main config file is no longer supported, as scheduled downtime entries are now saved in the retention file. To preserve existing downtime entries, stop Nagios 2.x and append the contents of your old downtime file to the retention file.
The old comment_file file variable in the main config file is no longer supported, as comments are now saved in the retention file. To preserve existing comments, stop Nagios 2.x and append the contents of your old comment file to the retention file.
Also make sure to read the "What's New" section of the documentation. It describes all the changes that were made to the Icinga code since the latest stable release of Nagios 3.0.6. Quite a bit has changed, so make sure you read it over.
Upgrading From an RPM Installation
If you currently have an RPM- or Debian/Ubuntu APT package-based installation of Nagios and you would like to transition to installing Icinga from the official source code distribution, here's the basic process you should follow:
Backup your existing Nagios installation
Configuration files
Main config file (usually nagios.cfg)
Resource config file (usually resource.cfg)
CGI config file (usually cgi.cfg)
All your object definition files
Retention file (usually retention.dat)
Current Nagios log file (usually nagios.log)
Archived Nagios log files
Uninstall the original RPM or APT package
Install Icinga from source by following the quickstart guide
Restore your original Nagios configuration files, retention file, and log files
Note that different RPMs or APT packages may install Icinga in different ways and in different locations. Make sure you've backed up all your critical Nagios files before removing the original RPM or APT package, so you can revert back if you encounter problems.
© 2009 Icinga Development Team, http://www.icinga.org