Updating

Observium has been designed from its initial inception to be easy and seamless to upgrade. We recommend keeping Community Edition installations updated to the latest version and updating Subscription Edition installations at least once per month.

Quick Update

To jump immediately to the Subscription Edition update instructions, click here

Subscription Edition#

What is the Subscription Edition?#

The Subscription Edition is released in stable and current trains using our SVN-based update system. It includes the new alerting system with advanced features, the traffic accounting system, routing protocols and additional future Service Provider and Enterprise-targeted features. It receives receive rapid bug fixes and feature improvements thanks to the SVN-based updates system.

You can subscribe using our Subscription signup page.

What is SVN?#

Subversion (SVN) is a version control system that allows users to download the very latest version of Observium without having to wait for someone to get around to packaging it. Advantages to using Subversion include the latest version, vastly simplified updating, the ability to roll back an upgrade and the ability to easily create and submit patches.

Below are some quick directions for a couple of common tasks.

Why use SVN?#

We use SVN as an automatic update mechanism in order to rapidly deliver improvements and fixes to users without the hassle of traditional packaged updates.

Rolling and Stable#

Our use of SVN allows us to maintain two parallel trains of Observium, rolling and stable. rolling receives daily updates, and stable receives weekly updates. The stable train is intended to be safe to use for automatically updating installations.

Switch between Rolling and Stable trains#

Sometime required to switch from stable to rolling train, for exaple to check fixed issue or updated/added feature. For switch use this commands from main observium dirrectory:

Stable -> Rolling#

 svn up
 svn switch http://svn.observium.org/svn/observium/trunk

Rolling -> Stable#

 svn switch http://svn.observium.org/svn/observium/branches/stable

Migrate an existing Community Edition installation to the Subscription Edition#

In order to move to the SVN respository-delivered code it's necessary to check out a new copy of the code and move your existing config.php and rrd directory to it.

Assuming you have installed to /opt/observium :

cd /opt 
mv observium observium-old
svn co http://svn.observium.org/svn/observium/branches/stable observium
cp observium-old/config.php observium
mv observium-old/rrd observium-old/logs observium
cd observium
./discovery.php -u

Note that you will be prompted for a username and password when you update, these are provided in the Subscription Portal.

The commands above will install the stable train. If you'd like to use the rolling train, change the branches/stable part of the third command to trunk.

It's probably best to stop your cron daemon (or at least disable the Observium cron jobs temporarily), because starting the poller when you're half way the checkour, or the rrd directory move, may cause adverse effects.

Upgrading the Subscription Edition to the very latest version#

Upgrading between releases with SVN is simple. If you have direct access to the command-line on the server, you can enter the commands below directly; alternatively, you can maintain a copy on a local machine and upload updated versions to the server.

To upgrade Observium, simply use the command below in the root of the installation directory.

svn update

To ensure that your database is kept up to date, you must run discovery.php immediately after an SVN update.

./discovery.php -u

Upgrading the Subscription Edition to a specific version#

You can upgrade to a specific revision with the following command:

svn update -r <revision number>

Let's say you want to install/upgrade version 0.12.4.3049. The SVN revision is the last number, so run the following:

svn update -r 3049

It may be possible something is broken in an official release and was fixed in the development version. We can not oversee all code changes and impact they may have to any of your devices, so we can not accept bug reports for non-very-latest versions. If you find a bug, try the latest version and if it's still broken, contact us. If it's not broken any longer, well, excellent!

Community Edition#

Upgrade to latest Major release#

Disable observium cronjobs optional

Run the following commands (as root):

cd /opt
mv observium observium_old
wget -Oobservium-community-latest.tar.gz http://www.observium.org/observium-community-latest.tar.gz
tar zxvf observium-community-latest.tar.gz
mv /opt/observium_old/rrd observium/
mv /opt/observium_old/*log* observium/
mv /opt/observium_old/config.php observium/

Update DB schema:

/opt/observium/discovery.php -u

If it has been a very long time since you've updated (12 months or more), you may want to force an immediate rediscovery of all devices to make sure things are up to date :

/opt/observium/discovery.php -h all

Re-enable observium cronjobs optional

You may now delete your observium_old directory if everything has updated correctly:

rm -rf observium_old