Copyright © 2004-2013 The OpenNMS Group, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts and with no Back-Cover Texts. A copy of the license is available at http://www.gnu.org/copyleft/fdl.html
Table of Contents
OpenNMS is the creation of numerous people and organizations, operating under the umbrella of the OpenNMS project. The original code base was developed and published under the GPL by the Oculan Corporation until 2002, when the project administration was passed on to Tarus Balog.
The current corporate sponsor of OpenNMS is The OpenNMS Group, which also owns the OpenNMS trademark.
OpenNMS is a derivative work, containing both original code, included code and modified code that was published under the GNU General Public License. Please see the source for detailed copyright notices, but some notable copyright owners are listed below:
Please send any omissions or corrections to this document to Tarus Balog.
OpenNMS is the world's first enterprise-grade network management system developed under the open source model. As with any complex and powerful system, getting it installed and configured can take a little effort. It is the purpose of this document to explain what is required to get OpenNMS installed.
So, how should you use this document? It is arranged in the following sections:
The programs on which OpenNMS depends, and how they need to be modified
Installation and upgrade instructions, including details for specific operating systems and distributions
Getting started with OpenNMS, including initial configuration and logging into the web interface
Building OpenNMS from source
Troubleshooting and Where to Get Help
This installation guide relies strongly on the idea of "packages." Most modern operating systems and distributions have a system where software can be installed and managed through the use of packages that group the files belonging to a given application together (as well as managing changes to those files, removal, upgrades, etc.).
Please see the latest release notes to see if your operating system is supported. Currently, OpenNMS runs on many Linux distributions, Solaris, Mac OS X and Windows.
This guide assumes that if you use packages, you do so consistently. This is because OpenNMS will attempt to determine if the software it requires is installed by using the operating system's built in package management system. If you've installed, say, Java, but not via packages, OpenNMS will be unable to determine that Java is installed and it will fail.
To get back to the original question of "how should you use this document," first go through the second section to insure that you have all of the prerequisite applications properly installed and configured. Use the third section to help get those packages installed for your particular operating system, as well as the OpenNMS software. Finally, use the last section to help correct any errors your might encounter.
While it is impossible to exactly size OpenNMS for a particular environment, the following represents the minimum requirements for installation, assuming a network of about 200 devices. Note that OpenNMS can monitor more than 100 times that given the proper hardware.
A 1 GHz Pentium III (or equivalent processor) or better. OpenNMS can also take advantage of multiple processors.
A minimum of 256 MB of RAM, although 512 MB is strongly recommended. The OpenNMS Java Virtual Machine benefits from large amounts of memory, up to 2 GB, and more if using a 64-bit processor.
Given a budget choice between more RAM and a faster CPU, choose more RAM.
OpenNMS requires about 200 MB of disk space for the program files. In addition, each data variable collected requires, by default, a little under 300 KB of disk space. It is safe to assume that each interface being managed will require around 2 MB of disk space, so for 200 interfaces you are looking at 400 MB (conservatively). Depending on the number of events stored, you can assume 100 MB to 200 MB are required for the database. Finally, the OpenNMS logs can grow quite large, especially in debug mode.
log4j.properties file in the OpenNMS
configuration directory (usually
/etc/opennms) to change those settings. By
default, the Log4J file rotation is configured to use 100MB per log
file, which ends up using a little under 2 GB.
Note: Due to the write-heavy nature of time-series data and the database, it is recommended that you do not use RAID-5 with OpenNMS. RAID-1 or RAID-1+0 is recommended if using RAID. In addition, LVM adds a small but appreciable amount of overhead and it is recommended that you do not use it.
Table of Contents
Before you start, you may want to install the yum-fastestmirror RPM if your distro supports it. This can often speed up downloads of large packages. See the CentOS Wiki for more details. This step is not strictly necessary, but can make your overall yum experience better.
[user@localhost]$ sudo yum install yum-fastestmirror Setting up Install Process ... Running Transaction Installing: yum-fastestmirror ######################### [1/1] Installed: yum-fastestmirror.noarch 0:1.1.9-2.fc8 Complete!
There are 4 types of releases available through yum.
To simplify installation through Yum, we've created an RPM that contains the configuration necessary for Yum to be able to find the other OpenNMS packages. Based on the release you chose in the section above, choose the approprate RPM from the OpenNMS Yum Repository.
For example, to install the latest snapshot release on Fedora 7, you would run:
rpm -Uvh http://yum.opennms.org/repofiles/opennms-repo-snapshot-fc7.noarch.rpm
Or, to install the latest unstable release on CentOS or RHEL 5, you would run:
rpm -Uvh http://yum.opennms.org/repofiles/opennms-repo-unstable-rhel5.noarch.rpm
Now you should see OpenNMS packages available when you get a list of yum packages:
[user@localhost]$ sudo yum list opennms ... Available Packages opennms.noarch 1.5.96-1 opennms-unstable
If you are using older yum-based distributions (like CentOS 3, for example), you may
need to append the yum configuration to
versions of yum don't recognize
/etc/yum.repos.d/ as a valid
location for yum configuration. You can fix this by using
to append the repository configurations to
[root@localhost]# cat /etc/yum.repos.d/* >> /etc/yum.conf
First, you'll want to enable the primary Mandriva URPMI repositories. The easiest way to do so is to follow the instructions at EasyURPMI. For example, on Mandriva Linux 2007, you would end up running something like this:
urpmi.addmedia main ftp://mirrors.usc.edu/pub/linux/distributions/mandrakelinux/official/2007.1/i586/media/main/release with media_info/hdlist.cz urpmi.addmedia --update main_updates ftp://mirrors.usc.edu/pub/linux/distributions/mandrakelinux/official/2007.1/i586/media/main/updates with media_info/hdlist.cz
Now, you'll need to enable the OpenNMS Mandriva repositories. First, add the OpenNMS stable repository (replace mandriva2007 with your release):
urpmi.addmedia --probe-hdlist opennms-stable http://yum.opennms.org/stable/mandriva2007
If you want OpenNMS stable snapshots, add the testing repository next (replace mandriva2007 with your release):
urpmi.addmedia --probe-hdlist opennms-testing http://yum.opennms.org/testing/mandriva2007
If you want the latest unstable version, add the unstable as well (replace mandriva2007 with your release):
urpmi.addmedia --probe-hdlist opennms-unstable http://yum.opennms.org/unstable/mandriva2007
And if you want to install nightly snapshots, then add the snapshot one (replace mandriva2007 with your release):
urpmi.addmedia --probe-hdlist opennms-snapshot http://yum.opennms.org/snapshot/mandriva2007
First, you need to tell apt-get how to find OpenNMS. Add the following
contents to your
deb http://debian.opennms.org stable main deb-src http://debian.opennms.org stable main
If you wish to use the latest development version of OpenNMS, add unstable instead:
deb http://debian.opennms.org unstable main deb-src http://debian.opennms.org unstable main
OpenNMS is written mainly in Java, although there are a few JNI calls to some C code in order to implement things such as ICMP. and so it follows that Java would need to be installed.
OpenNMS requires Java SE 5.0 or higher (JDK 1.5). It is recommended that the JDK from Sun is used with OpenNMS. If OpenNMS is to be run on a 64-bit system, be sure to install the 64-bit JDK.
The Sun JDK is available in our Yum repository. If you have configured Yum as specified above, you just need to run:
yum install jdk
Because of a bug in the 64-bit RPM signing, if you are on x86_64, you will
need to disable GPG checking. You can do so with the
option to yum:
yum --nogpgcheck install jdk
The Sun JDK is available in our URPMI repository. If you have configured URPMI as specified above, you just need to run:
urpmi --auto jdk
Sun's Java can now be installed using "apt" on Debian Etch or higher.
apt-get install sun-java5-jdk
This should also work on Ubuntu 6.10 (Edgy Eft) or higher. Alternatively, you could install sun-java6-jdk, which has performance improvements over the java5 version.
It is important to install the JDK instead of the JRE, as the web UI will need to compile JSPs into Java code.
You will need to use Sun's Java SE, version 5 (1.5) or later. You can download it from Sun's Java website. Step through the licensing process and then download the proper version of Java for your operating system.
PostgreSQL (or "Postgres") is a relational database that OpenNMS uses to store information about devices on the network, as well as information about events, notifications and outages.
When installing OpenNMS, two things must happen. First, OpenNMS has to be able to contact the database over TCP/IP (even on localhost) and second, the installation process must be able to create the database.
OpenNMS requires version 7.4 or later of PostgreSQL, although 8.1 or higher is recommended for performance reasons.
On modern versions of Red Hat Enterprise Linux, CentOS, and Fedora,
you should just need to install the
[user@localhost]$ sudo yum -y install postgresql-server Setting up Install Process ... Running Transaction Installing: postgresql-server ######################### [1/1] Installed: postgresql-server.x86_64 0:8.2.5-1.fc8 Complete!
Red Hat Enterprise Linux 3 and CentOS 3 call their PostgreSQL packages "rhdb" for the "Red Hat DataBase" so if you are on one of these older distributions, you will have to substitute "rhdb" for "postgresql" when installing:
sudo yum -y install rhdb-server
On Mandriva, you use URPMI to install the PostgreSQL server:
sudo urpmi --auto postgresql-server
On Debian or Ubuntu, use apt to install the PostgreSQL server:
sudo apt-get update sudo apt-get install postgresql-8.1
On Windows, all you should need to do is get the latest Windows installer from PostgreSQL.org.
If you are running on a FAT32 filesystem, see the detailed installation instructions on the wiki.
First, unpack the installer. The installer does not run properly from inside a zipped folder, so you will need to extract the ZIP file. You should be able to just copy the postgresql-X.X.msi and postgresql-X.X-int.msi files to your desktop and run them from there.
Then, run the postgresql-X.X.msi and follow the instructions. For the most part, the defaults should be just fine, although if you're allowing the installer to initialize your database, make sure the encoding is set to "UTF-8".
Once you have installed PostgreSQL, you will need to make two changes
to Postgres configuration files:
These files are only created once PostgreSQL has been started, so if
your installation method for Postgres did not start the database, do
so before continuing. Usually, startup scripts will be placed in
Locate the Postgres "data" directory. Often this is
You should then find the two files we need to modify in that directory.
This file controls some basic parameters of PostgreSQL. We need to change three of these parameters.
First we need to make sure PostgreSQL is listening on an IP socket, and not just a local unix socket.
For PostgreSQL 7.4 and 8.0, make sure the following line is set and uncommented:
tcpip_socket = true
On PostgreSQL 8.1 and up, use this instead:
listen_addresses = 'localhost'
Next, find the line in the file that contains
max_connections. It needs to be at least:
max_connections = 256
Find the line that contains
It needs to be at least:
shared_buffers = 1024
pg_hba.conf file controls which machines
and users can access the database on a given machine via TCP/IP.
Since that is how OpenNMS accesses the database (via
it is necessary to modify this file to allow OpenNMS to work. The easiest
thing to do is to just allow anyone from the localhost to access the database
(do not add the last line if your system does not support IPv6):
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD local all all trust host all all 127.0.0.1 255.255.255.255 trust host all all ::1 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff trust
Make sure that no other lines are uncommented in this file.
You will need to stop and restart Postgres after making these changes.
Most distributions will automatically initialize the default database on first startup, but if yours doesn't (for example, on Solaris), you will need to do so manually.
postgres user, go to the
/usr/local/pgsql/bin directory (or wherever your PostgreSQL
binaries are installed), and run:
./initdb -D /usr/local/pgsql/data -E "UNICODE"
Then you'll need to start the database:
./pg_ctl -D /usr/local/pgsql/data start
OpenNMS makes heavy use of a stored procedure called "iplike". Since it is written in C, it has been removed from the main OpenNMS code and placed in its own project.
If a C-based iplike is not installed, the OpenNMS installer will add a version written in the PostgreSQL command language. It will work, but not as quickly as the compiled iplike will.
To install iplike, simply download the proper package for your distribution. There should be a package for PostgreSQL versions 7.4-8.1, and one for 8.2+. In addition, there will be separate 32-bit and 64-bit versions. It is also possible to download a tarball from the OpenNMS SourceForge project page, and do the usual "./configure", "make", and "make install". Once installed it should not be required to update it on every OpenNMS upgrade.
Java has never had a really good API for ICMP. Since ICMP is the basis for the "ping" command, it is rather imperative that any Java-based network management platform address the need for ICMP. OpenNMS does this by using some code written in C, and accessing it using the Java Native Interface (JNI).
As of OpenNMS 1.3.6, the ICMP code has been moved to it's own library outside of OpenNMS. This makes the main OpenNMS application pure Java, and as such it only has to be built once, instead of for each platform.
Packages for JICMP are available for most distributions. If your distribution does not have packages available, you can download the source from the SourceForge download page for JICMP.
On most RPM-Based Distributions, all you should need to run is:
yum install jicmp
On Mandriva, you can install JICMP with the command:
urpmi --auto jicmp
If JICMP has not already been compiled on your RPM-based platform, you can build a native RPM from the source tarball like so:
If you are on a 64-bit platform, you can build a 64-bit RPM instead like so:
On Debian or Ubuntu, you can install JICMP through apt:
sudo apt-get install libicmp-jni
To build from source, download the latest source tarball from SourceForge, unpack it, and run the usual:
./configure make make install
Table of Contents
You need to be root when running most of the commands in this chapter.
OpenNMS stores data in a number of locations:
OpenNMS configuration files.
On some distributions, upstream changes in files in this directory are detected and means are provided for migrating those changes to the new release.
On RPM-based distributions, if an OpenNMS configuration file has changed,
RPM will create a "
.rpmnew" file which contains the
version of that configuration file that shipped with the new version of
OpenNMS. You will need to look at the changes between your file
and the new one and merge them manually, at the moment. The command
diff -u <old file> <new file> | less" can
assist you in seeing what has changed.
On Debian-based distributions, dpkg will automatically prompt you when a configuration file has changed upstream between versions, and will offer you a set of options to deal with it.
RRD data files that store response time data and performance data collected
from SNMP (and elsewhere). The installer should not touch the RRD files in
$OPENNMS_HOME/share/rrd. Unless you are migrating from
RRDTool to jRobin, you should not have to worry about them.
The OpenNMS web application. While data is not stored here, some users may customize the web interface and these customizations should be saved before upgrading OpenNMS.
Data about nodes, services, events, notifications, etc., are stored in the
opennms table in PostgreSQL.
Follow the instructions in this section appropriate for your operating system if you are performing a fresh install. If you are upgrading an existing installation of OpenNMS, see the next section.
As of version 1.6, OpenNMS is packaged in a modular fashion. The following packages are available for installation:
opennms-core: The core OpenNMS code, responsible for network discovery, polling, data collection, notification, and more.
opennms-webapp-jetty: The OpenNMS web UI, designed to be started by the opennms-core engine.
opennms: A convenience package which installs everything you need for a functional OpenNMS installation on a single system.
opennms-remote-poller: The standalone remote poller, which can report back to an OpenNMS instance.
opennms-plugin-ticketer-centric: The CentricCRM/Concursive ticketer plugin.
As long as Yum is configured to point at the OpenNMS repository, all you should need to run is:
sudo yum install
[packages] is the list of packages above
that you wish to install.
If URPMI is configured to point at the OpenNMS repository, you can install by running:
sudo urpmi --auto
[packages] is the list of packages above
that you wish to install.
Download the packages you wish to install from the SourceForge download page for OpenNMS.
rpm -i to install the packages:
rpm -ivh opennms*.rpm
As of OpenNMS 1.3.10, you can use the
--relocate flag to RPM
if you wish to put the logs and collection data in an alternate location:
rpm -ivh --relocate /var/opennms=/mnt/netapp/opennms-data /var/log/opennms=/mnt/netapp/opennms-logs opennms*.rpm
Download the appropriate package for your Solaris version from the SourceForge download page for OpenNMS.
Then, install the package using
#gzip -d opennms-*-local.gz
#pkgadd -d `pwd`/opennms-*-local
OpenNMS is supported on Mac OS X via the Fink project.
Once you've installed Fink, you should be able to install OpenNMS by running:
fink install opennms
OpenNMS is supported on Windows as well, although the lack of true package management makes it a bit more work to maintain.
To install on Windows, download the latest
file from the
OpenNMS SourceForge download page.
You should be able to then just double-click the jar file in Explorer, and follow the instructions in the install wizard.
Once you're done, you may want to make a pristine copy of the
so it's easy to tell what's changed in later releases later.
There are a number of things you can do that can help ease the transition when doing upgrades.
Should you not be doing this already, either using vacuumd or cron, prune away any unneeded events. The events table will most probably be the largest, and there's no point backing up data that you don't need.
For example, to delete any events older than 6 weeks that have no
associated outages, you can run, from the
--# this deletes any events that are not associated with outages DELETE FROM events WHERE NOT EXISTS (SELECT svclosteventid FROM outages WHERE svclosteventid = events.eventid UNION SELECT svcregainedeventid FROM outages WHERE svcregainedeventid = events.eventid UNION SELECT eventid FROM notifications WHERE eventid = events.eventid) AND eventtime < now() - interval '6 weeks';
Depending on the version you are upgrading from and the version you are upgrading to, you may run into issues with the database upgrade. It is strongly recommended that you back up the database.
pg_dump -U postgres -Fc -C -f opennms-database-backup.pg opennms
Back up your
$OPENNMS_HOME/etc directory before doing any
upgrades, so you can go back to your previous version if something goes wrong, and
so you have a reference of your previous configuration when adapting config file
changes to the new version.
tar -C $OPENNMS_HOME -cvzf /tmp/opennms-etc-backup.tar.gz etc
If you have a large number of events, you may need to increase the amount
of memory passed to the OpenNMS
install tool. For example,
if you have 250k events, you will need almost 600MB of heap. When the time comes
to run the
install tool, assuming you have enough available
memory, it's probably safe to just use a very large value to pass to
install -Xms1024m -Xmx2048m -dis
If you have the OpenNMS Yum repositories configured, all you should need to do to get the new release is run:
sudo yum upgrade opennms
If you are comfortable letting your distribution give you OS updates along with OpenNMS, you can just run:
sudo yum upgrade
If you have the OpenNMS URPMI repositories configured, you can upgrade by running:
sudo urpmi --auto opennms
As with Yum, if you are comfortable letting URPMI give OS updates along with OpenNMS, you can run:
sudo urpmi --auto --auto-select opennms
You can upgrade RPM systems manually by downloading the RPM packages from SourceForge and upgrade them by running:
sudo rpm -Uvh opennms*.rpm
If your Debian or Ubuntu system is configured with the OpenNMS Apt repository, you should just need to run:
sudo apt-get update sudo apt-get -u install opennms
Since there is no automated installation/upgrade procedure for Windows, you will have to do some preparation before installing the latest version.
Back up and then remove
Once you've cleaned up the etc and lib directories, the next
step is to download the latest
standalone-opennms-installer-X.X.X.jar from the
OpenNMS SourceForge download page.
Next, run the installer jar, and install over your existing OpenNMS location.
If you backed up the pristine
etc directory on your
previous installation, you can compare it to the current one to see
if there are any configuration changes you wish to integrate into
your new install.
Copy your backed up
etc directory back into the
You should now be able to run your upgraded OpenNMS.
Before you can run the post-install, OpenNMS needs to be configured
to use an appropriate Java Runtime Environment (JRE). The OpenNMS tool
runjava is used to set this up, and it can either
search for a suitable JRE or you can tell it exactly which JRE to use.
runjava with the "
option to search for a JRE:
No matter which installation method above you choose, and whether
you are performing a fresh install or an upgrade, you still need to run
the OpenNMS installer. This tool will setup the
within PostgreSQL among other things.
#$OPENNMS_HOME/bin/install -l /usr/local/lib -dis
The "-l" parameter will look for the jicmp and/or jrrd libraries in the location specified. The "-dis" will initialize and check the database. Note at the end of the output from the installer it will indicate if iplike has been installed properly.
For a full list of options the installer accepts, run
Table of Contents
By default, OpenNMS will not discover hosts until you configure it to do so, or explicitly add them in the Admin UI. You will most likely want to tell OpenNMS where to look to discover hosts on your network.
should see an example <include-range> tag with a <begin> and an
<end> which is commented out.
You will most likely want to uncomment it and change the beginning and end
ranges (within the
tags, respectively). Additionally, you can add as many
<include-range>es as you'd like.
If you would rather list the individual host that you want to have
discovered, you can insert
<specific> tags above the
Lastly, if you prefer to use the web interface to add individual hosts for OpenNMS to monitor, you leave the contents of this file commented out.
By default, OpenNMS's built-in web server listens on port 8980, so point
your browser at
(where <host> is the host you're running OpenNMS on). The initial
user name is "
admin" and the password is
If everything looks good, you can configure OpenNMS to start automatically at boot time. By default on most platforms OpenNMS does not start automatically until you configure it to do so.
The OpenNMS packages add an init script in
/etc/init.d), however you need to execute
chkconfig to enable the service to start
#/sbin/chkconfig --add opennms
Table of Contents
OpenNMS is not terribly heavy on CPU usage, but is extremely I/O-bound, and will also take advantage of as much RAM as you can give it. OpenNMS itself doesn't use a huge amount of RAM per-node, but allowing the OS to cache filesystem interaction makes a very large performance difference.
If you are running on hardware RAID, it is strongly recommended that you have a battery-backed write cache. For example, one user reported that on an HP DL380 G4, the I/O wait of the server dropped from 15% to essentially nothing, using a 128MB battery-backed write cache.
You will get the most out of OpenNMS if you spread your I/O out into multiple spindles and/or separate disks/channels.
PostgreSQL writes primarly to 2 classes of files and directories.
The main PostgreSQL database is in
$PGDATA is usually something like
PostgreSQL keeps a journal of transactions, in
If you can separate the pg_xlog directory onto another spindle or mount point, you will increase your PostgreSQL performance considerably. To do so, you should be able to just shut down PostgreSQL, move that directory, symlink it to the old location, and start it back up.
sudo /etc/init.d/postgresql stop sudo mv /var/lib/pgsql/data/pg_xlog /mnt/xlogspindle/pg_xlog sudo ln -s /mnt/xlogspindle/pg_xlog /var/lib/pgsql/data/pg_xlog sudo /etc/init.d/postgresql start
The RRD data is the single heaviest source of I/O in most OpenNMS installations. Making sure that it is on a different spindle from PostgreSQL makes a huge difference.
RRD data storage causes a large number of small random disk writes, usually a few writes for each update.
By default, OpenNMS stores each collected variable in its own file, unless the store by group feature is enabled.
Normally, there will be 2-3 writes for each update: one for the file header, one for the previous RRA, one for the next RRA.
When multiple samples are consolidated into a single stored data point in the RRA, there will be additional writes. By default, such consolidations happen hourly and daily on the GMT day boundary. This will cause higher than normal amount of writes after the top of the hour and after the GMT day boundary.
The OpenNMS RRDs live, by default, in
If you are using the RPMs, this will be
sudo mv /var/opennms /mnt/rrdspindle/opennms sudo rm -f /opt/opennms/share sudo ln -s /mnt/rrdspindle/opennms /opt/opennms/share
If you are dedicating spindles or drives to OpenNMS, you can mount them
noatime option on Linux or Solaris for an
additional performance boost. This will keep the OS from updating the
file access time on individual RRD and database files every time they
On Linux, you do so by editing
/etc/fstab and adding
noatime to the options section of the filesystem. For example:
LABEL=/ / ext3 defaults 1 1 LABEL=/var/opennms /var/opennms ext3 defaults,noatime 1 2 LABEL=/var/lib/pgsql /var/lib/pgsql ext3 defaults,noatime 1 2 LABEL=/var/lib/pgsql/data/pg_xlog /var/lib/pgsql/data/pg_xlog ext3 defaults,noatime 1 2
On Solaris, you edit
/etc/vfstab and add
noatime as an option at the end of the mountpoint
information, like so:
/dev/dsk/c1d0s0 /dev/rdsk/c1d0s0 / ufs 1 no /dev/dsk/c1d1s0 /dev/rdsk/c1d1s0 /opt/opennms/share ufs 2 no noatime /dev/dsk/c1d2s0 /dev/rdsk/c1d2s0 /usr/local/pgsql/data ufs 2 no noatime /dev/dsk/c1d3s0 /dev/rdsk/c1d3s0 /usr/local/pgsql/data/pg_xlog ufs 2 no noatime
Use a mirrored stripe (RAID-10), with enough disks to handle the amount of data you need to collect. A single disk, a pair of mirrored disks (RAID-1), or a RAID-5 is only appropriate for an installation doing a small amount of data collection.
There are a number of other things you can do to tune PostgreSQL. For a good writeup on PostgreSQL performance tuning, see this page at revsys.com.
If you have a reasonable amount of RAM (2GB+), the following settings should give much better performance than the defaults that come with the PostgreSQL configuration:
shared_buffers = 20000 work_mem = 16348 maintenance_work_mem = 65536 vacuum_cost_delay = 50 checkpoint_segments = 20 checkpoint_timeout = 900 wal_buffers = 64 stats_start_collector = on stats_row_level = on autovacuum = on
On systems with 4GB or more of RAM, we've found that changing the max_fsm_pages and max_fsm_releations, as well as work_mem and maintenance_work_mem improves performance dramatically:
work_mem = 100MB maintenance_work_mem = 128MB #max_fsm_pages = 204800 # min max_fsm_relations*16, 6 bytes each max_fsm_pages = 2048000 #max_fsm_relations = 1000 # min 100, ~70 bytes each max_fsm_relations = 10000
If you increase memory settings for PostgreSQL, you will probably need
to increase the maximum shared-memory settings in your OS. On Linux,
you can do this by editing
/etc/sysctl and adding
Depending on how many shared memory segments you need, you may need to adjust that value.
Because of OpenNMS's high-I/O profile, there are a number of things that will cause performance issues on reasonably large installs.
Don't put the database or RRD data on file systems managed by LVM.
Don't put DB or RRD data on file systems on RAID-5.
Don't use older kernels. Linux 2.6 and Solaris 10 perform much better than older releases.
Table of Contents
OpenNMS is a complex software product, and it does not (yet) have a
./configure && make && make install"
build process like many other tools. If there is a packaged release for
your operating system, we highly suggest you use that instead. If you have
problems with a packaged release, please see the troubleshooting section
Table of Contents
The following section contains advice for overcoming common installation issues. If your issue is not addressed below, please see the section on where to get help.
To assist with code management, the easiest way to install OpenNMS
is via packages. Every effort has been made to insure that the packages
OpenNMS depends on are required before the OpenNMS package can be
installed. You should be able to find those packages on the distribution
CDs that came with your system. For some of the more obscure packages,
you can visit the OpenNMS FTP
site and check in the
In addition, sites like Ibiblio and FreshRPMs are also good
This can happen for a a number of reasons. You can run
opennms -v status" a few times after getting this error to
see if OpenNMS eventually starts itself completely and if not, to see
which daemons never start up completely. Here are some of the likely
causes of this problem:
OpenNMS takes a while to startup. This can happen on larger
installations and when this happens "
opennms -v status"
will eventually show that all services have started up. By default,
the startup script will try 10 times to see if OpenNMS has started
and will wait 5 seconds between each try. You can increase the
number of times by creating
$OPENNMS_HOME/etc/opennms.conf and adding a
line like "
START_TIMEOUT=20" to double the number of
times it tests. You can set the value to
0 to have the
startup script not wait for OpenNMS to start.
Database is not running. If only about half or less of the
daemons are shown as running, you can check for this condition by
FATAL errors in the log files. You'll see
something like "
Error accessing database" in the
Dhcpd doesn't start. See the item in the next section.
JNI library problem. OpenNMS uses a few native C libraries that are accessed using JNI (Java Native Interface). Normally they just work, except users have started seeing problems when running Linux in native AMD64 mode where they end up using a 32-bit (x86) version of Java and a 64-bit (AMD64) version of the JNI libraries, or vice-versa. If you have this problem, you might want to try switching your version of Java from 32-bit to 64-bit or in the other direction.
Other. If the OpenNMS is installed, and the packages were not
forced in using options like "
application should run just fine. If not, OpenNMS has a robust
logging facility. Change to the logs directory (usually
/var/log/opennms) and search the logs, using
grep or your tool of choice, for words like
ERROR (the two highest log
severities). Those events should give you clues as to why OpenNMS is
The OpenNMS DHCP poller will fail to start most operating systems
(Linux, in particular) if you are running a DHCP client on the OpenNMS
server. You'll see this by running "
opennms -v status" and
seeing everything in the
running state, except for
Dhcpd. The solution is to edit
comment-out the "
Dhcpd. For example, this is what the section would look
like after modification to disable
<!-- Commented out since we have a DHCP client on this server <service> <name>OpenNMS:Name=Dhcpd</name> <class-name>org.opennms.netmgt.dhcpd.jmx.Dhcpd</class-name> <invoke pass="1" method="start"/> <invoke at="status" pass="0" method="status"/> <invoke at="stop" pass="0" method="stop"/> </service> -->
We discourage the running of OpenNMS on a server that is a DHCP client, both because OpenNMS may not be able to monitor DHCP servers on the network, and it is important that the monitoring server have a static IP address for receiving traps and to be reliant on as few network services as possible.
program is used to
locate a suitable JRE for OpenNMS at install time that will be used for
the installer and also for running OpenNMS after installation. See the
section earlier in this manual on installing Java for OpenNMS. If you
installed Java in a location that
runjava cannot find, you
can use its "
-f" option to specify the JRE you want OpenNMS
You either need to set "
lc_messages = 'C'" in your
postgresql.conf file and restart PostgreSQL or upgrade to PostgreSQL 7.4
The installer does not always verify that an operation will succeed before executing the operation (e.g.: dropping database functions). In this case, it catches the exceptions returned from the database and checks the exception to see if it is an "okay" exception that should be ignored (e.g.: if the database function does not exist when attempting to drop a function).
In PostgreSQL 7.4 and later, a new client/server protocol is used
(version 3, to be specific) that provides specific error codes intended
for programmatic evaluation and we use these error codes if the server
provides them. However for PostgreSQL versions before 7.4, we require
that the database server error language be in English (the
C' locale) so that we can parse the text error messages.
If you are not running PostgreSQL 7.4 or newer, the installer executes a
bogus query against the database and checks for an expected result in
This is a warning that the installer might not update tables successfully. Make sure that your database is backed up, and run the installer again with the "-N" option to ignore this check.
As an attempt to ensure that the install will complete successfully, a check is done to see if there might be any rows with NULL columns that might be inserted into a column in an upgrade table with a NOT NULL constraint. This usually happens when a previous run of the installer failed, or might be due to modifications to the database schema or a really old version of the schema.
When the installer runs to upgrade the OpenNMS database from a
previous install, it often updates table schemas. When it does this, it
copies the data in a table to a temporary table (e.g.: the contents of
node are copied into
node_old_11033991291234). The original table is
deleted, the new version of the table is created, the data in the
temporary table is translated into the new table, and finally the
temporary table is deleted.
Unfortunately, the installer cannot check for all problems that might break translation, so sometimes the translation step fails. In this case, the installer "reverts" the table it was processing by dropping the new table and moving the temporary table into its place.
Reverting the table in case of a problem is all good and well, but
sometimes even it does not work properly, especially with older versions
of the Java installer. If this happens, the temporary table (the one
with "_old_" in it) is left with all of the old data. Until OpenNMS
1.1.5, this problem would not be caught the next time you ran the
installer. The installer would see that you did not have the
node table, for example, and happily continue to
create a new one for you. This is bad, especially since you probably
still have data that you care about that is now in the "old"
If you get this error, you will want to get rid of the table(s)
containing "_old_", however you want to first check if they contain
data. For example, if you have a single table,
node_old_11033991291234, no other
node_old_* tables, and no
table, you can simply rename the table:
# psql -h localhost -U opennms opennms
Welcome to psql 7.4.6, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit opennms=#ALTER TABLE node_old_11033991291234 RENAME TO node;
You can use the "\d" command within
see what other tables exist in your database. You can use "
count(*) from table;" (fill in the table name for "table") to get
a count of rows in any table. If you have empty tables, you can just
drop them. If you have multiple tables with data, you will have to
decide which table of data you want to keep or merge them. This is left
as a (not so simple) exercise for the reader.
Over time OpenNMS extends its database schema to improve functionality. This error can happen because of the way certain administrative functions in older versions of OpenNMS functioned or if the database was modified outside of OpenNMS (the latter is common for larger sites). Over time OpenNMS has introduced additional foreign key constraints on its database. These are used to ensure internal database consistency when data in two tables are tied together by a shared key. For example, each event can have a pointer to the node that it is related to; there is a foreign key constraint that requires that an event must not point at a node that does not exist.
Starting with 1.1.5, when we upgrade the database schema, we first check for rows that violate any new foreign key constraints that might be added. There are three options to to fix these errors:
Remove the offending rows. This is suggested if the number of
rows that violate the constraint is small in comparison to the total
number of rows in the affected table and if you don't need the data.
$OPENNMS_HOME/bin/install -C <constraint>
-X" to delete the offending rows.
Mark the key in the offending rows to NULL. This is suggested
if you need to keep the data around or are not yet sure about what
to do with it. Use "
<constraint>" to mark the key column to NULL in the
Fix the key in the offending rows. This is for advanced users and requires a good amount of effort. This is left as an exercise for the reader.
The PostgreSQL server cannot access the iplike.so file. This could be due to the file itself not having appropriate permissions for the user that PostgreSQL runs as and/or one or more of the parent directories of the iplike.so not having appropriate permissions.
This error is seen even when running the installer as root because it is not OpenNMS nor the installer that cannot access the iplike.so file, but the PostgreSQL database. The installer instructs the PostgreSQL database to load the iplike.so and the PostgreSQL database server usually runs as a non-root user, so it is subject to filesystem access control checks like any other normal user. This is commonly seen when people install OpenNMS into a home directory for root or another user and the permissions on that home directory do not allow users other than the owner of the directory access.
The latter part of the error could be something like
<path>/iplike.so: cannot open shared object file: No such
file or directory" or "
ld.so.1: postgres: fatal:
<path>/iplike.so: wrong ELF class: ELFCLASS32".
The PostgreSQL server cannot load the
This is almost always caused by the PostgreSQL server and the iplike.so
file being compiled for different processor instruction sets. This is
commonly seen when the PostgreSQL server is compiled to use a 64-bit
instruction set but the OpenNMS
iplike.so shared object is
compiled for a 32-bit instruction set, although the opposite is
possible, as well. You can use the "
file" command on
iplike.so and the
postmaster binary with
PostgreSQL to check their instruction sets.
The easiest solution is to see if there is a packaged version of
OpenNMS compiled for the same instruction set (32- or 64-bit) as your
PostgreSQL server. The next easiest method for most users is to switch
the PostgreSQL server to match the instruction set that the
iplike.so file was compiled for. For advanced users, you
can compile OpenNMS yourself to fit the processor set that you need. See
post to the discuss list for some pointers.
This error means the database was not created properly. Since the installer script is supposed to create the database, one might assume it is a problem with OpenNMS, but instead it is an issue with the SELinux portions of Red Hat 4 (and CentOS 4). Basically, the postgres init_db command is not able to write to /dev/null, and it fails without a useful error message.
To get around this, run the following commands:
rm -rf /var/lib/pgsql/data
Note that step 2 will delete any changes you made to the postgresql configuration files and you'll need to redo them.
An exact example of this error is:
If the above error happens when using admin functions through the web interface, such as managing users, notifications, and adding nodes, then the Tomcat web server is running as a non-root user but you haven't changed the permissions on the configuration files so the Tomcat user can access them. Go back and follow the instructions earlier in the install guide on setting up Tomcat to run as a non-root user.
OpenNMS is a community supported project. Please keep that in mind when seeking help on the program, as no one gets paid to work on the project (unless it is through a commercial support contract).
Check the release notes for this release. They are in the Documentation section of the OpenNMS project page at SourceForge.
The main OpenNMS site is a Wiki. As a community project, there is a lot of good advice and information available there. In particular, we suggest checking the above-mentioned release notes, the FAQ entries on the wiki, the bug database and, of course, Google, before posting to a mailing list.
OpenNMS maintains a number of active mailing lists on SourceForge:
A low traffic, moderated mailing list for OpenNMS announcements. All posts to this list are duplicated on the opennms-discuss list.
This is a fairly high traffic list of all updates to the Subversion repositories on SourceForge. Moderated. Only SVN updates are posted here (no discussion).
This list is for discussion of development of the OpenNMS codebase.
This is the main OpenNMS discuss list. It's pretty friendly, and reasonably high-volume. It tends to focus on configuration issues and general discussion of network management, but pretty much anything goes here. However, it is suggested that installation-related issues go to the opennms-install list instead.
This is a great list for new users to OpenNMS. The main focus is installation issues (cleared up by this great documentation, right?) but most "newbie" questions are welcome here.
OpenNMS has a network map feature, which includes code for automatically determining relationships between hosts (Linkd). This is the appropriate list for discussion of maps and the underlying Linkd code.
A discussion list for people running OpenNMS on Windows.
A list for discussion of OpenNMS in French.
A list for discussion of OpenNMS in Italian.
A list for discussion of OpenNMS in Japanese, as well as general discussion among the Tokyo OpenNMS Users Group.
A list for discussion of OpenNMS in UK English for those who don't speak American English (OK, just kidding). Actually, a discussion list for the UK OpenNMS Users Group. ;)
The OpenNMS mailing lists are also archived at gmane.org.
If you are using OpenNMS in a production environment, or are considering it, you might be interested in commercial support. The OpenNMS Group maintains the OpenNMS project, and we also offer support, training, consulting services and custom development.