From OpenNMS

This page shows, beginning with version 1.3.7, which configuration files (in $OPENNMS_HOME/etc/) require a restart for changes to take effect for different versions of opennms.

Unfortunally there is another page in the wiki describing this: Configuration_File_Index , both pages should be merged!

Contents 1 OpenNMS 1.8.x and newer 2 OpenNMS 1.6.x and newer 2.1 Files with an associated event that can trigger a re-read of the configuration 3 OpenNMS 1.3.7 and newer 3.1 Require a restart 3.2 Do not require a restart 3.3 Restart Daemons to reread Configuration Files

OpenNMS 1.8.x and newer

Beginning somewhere in OpenNMS 1.7.x a new method was introduced to reload configuration files, triggered by an event:

$OPENNMS_HOME/bin/send-event.pl -p 'daemonName name ' uei.opennms.org/internal/reloadDaemonConfig

Watch out for events like

uei.opennms.org/internal/reloadDaemonConfigSucessful
The daemon: name configuration changes have successfully been applied

For thresholding, there are two options:

1. If you want to reload the configuration for thresholds (i.e., to reload thresholds.xml), you should send:

$OPENNMS_HOME/bin/send-event.pl -p 'daemonName Threshd' uei.opennms.org/internal/reloadDaemonConfig

that is the short way to this:

$OPENNMS_HOME/bin/send-event.pl -p 'daemonName Threshd' -p 'configFile thresholds.xml' uei.opennms.org/internal/reloadDaemonConfig

2. If you want to reload the configuration for threshold packages (i.e., to reload threshd-configuration.xml), you should send:

$OPENNMS_HOME/bin/send-event.pl -p 'daemonName Threshd' -p 'configFile threshd-configuration.xml' uei.opennms.org/internal/reloadDaemonConfig

Following daemons already use this new methods, for all others see below the older versions of OpenNMS:

Daemon	Functionality
ackd
discovery
notifyd
statsd
threshd	thresholding

You can follow bug http://bugzilla.opennms.org/show_bug.cgi?id=2331 to see the latest changes.

OpenNMS 1.6.x and newer

Since 1.6.x and newer some daemons can be triggered by an event to reload their configuration files, see the following table. For those listed for version 1.3.7 below "Do not require a restart" opennms should detect the change after about 30 seconds (be careful not to save an invalid config file during editing!) and reload them. All others probably will need a restart of OpenNMS.

Files with an associated event that can trigger a re-read of the configuration

The table includes also events available since version 1.6.1
Check your $OPENNMS_HOME/etc/eventconf.xml for uei's containing ConfigChange or reload to see which ones are available with your installed opennms version.

Use $OPENNMS_HOME/bin/send-event.pl uei on your opennms server to send one of those events.

File	Associated Event
reload all configuration files? found in 1.7.9, but probably still not working completely	uei.opennms.org/internal/reloadDaemonConfig
destinationPaths.xml
discovery-configuration.xml	uei.opennms.org/internal/discoveryConfigChange
eventconf.xml	uei.opennms.org/internal/eventsConfigChange
rerun Importer Service	uei.opennms.org/internal/importer/reloadImport
ksc-performance-reports.xml
notifd-configuration.xml
notificationCommands.xml
notifications.xml
poll-outages.xml (pending verification)	uei.opennms.org/internal/schedOutagesChanged?
poller-configuration.xml	uei.opennms.org/internal/reloadPollerConfig or uei.opennms.org/internal/reloadSnmpPollerConfig
poll-outages.xml	uei.opennms.org/internal/schedOutagesChanged
scriptd-configuration.xml ?	uei.opennms.org/internal/reloadScriptConfig
snmp-config.xml
syslogd-configuration.xml	uei.opennms.org/internal/syslogdConfigChange
thresholds.xml (pending verification)	uei.opennms.org/internal/thresholdConfigChange
vacuumd-configuration.xml	uei.opennms.org/internal/reloadVacuumdConfig

OpenNMS 1.3.7 and newer

Require a restart

• actiond-configuration.xml
• c3p0.properties
• capsd-configuration.xml
• castor.properties
• categories.xml
• chart-configuration.xml
• collectd-configuration.xml
• database-schema.xml
• datacollection-config.xml
• dhcpd-configuration.xml
• discovery-configuration.xml uei.opennms.org/internal/discoveryConfigChange
• eventconf.xml (uei.opennms.org/internal/reloadEventConfig? uei.opennms.org/internal/eventsConfigChange?)
• eventd-configuration.xml
• events/*
• events-archiver-configuration.xml
• events.archiver.properties
• exclude-ueis.properties (pending verification)
• http-datacollection-config.xml
• jcifs.properties
• jmx-datacollection-config.xml
• linkd-configuration.xml
• map.disable
• map.properties
• model-importer.properties (uei.opennms.org/internal/importer/reloadImport?)
• monitoring-locations.xml
• nsclient-config.xml
• nsclient-datacollection-config.xml
• opennms-database.xml
• opennms.properties
• opennms-server.xml
• poller-config.properties (uei.opennms.org/internal/reloadPollerConfig?)
• poller-configuration.xml
• rrd-configuration.properties
• rtc-configuration.xml
• scriptd-configuration.xml (uei.opennms.org/internal/reloadScriptConfig?)
• service-configuration.xml
• statsd-configuration.xml (pending verification)
• syslogd-configuration.xml
• threshd-configuration.xml
• translator-configuration.xml
• trapd-configuration.xml
• viewsdisplay.xml
• vulnscand-configuration.xml
• webui-colors.xml
• xmlrpcd-configuration.xml
• xmpp-configuration.properties

Do not require a restart

• AvailabilityReports.xsl
• groups.xml (pending verification)
• javamail-configuration.properties
• log4j-controller.properties
• log4j.properties
• magic-users.properties
• PDFAvailReport.xsl (maybe)
• response-adhoc-graph.properties
• response-graph.properties
• site-status-views.xml
• snmp-adhoc-graph.properties
• snmp-graph.properties
• surveillance-views.xml
• SVGAvailReport.xsl
• users.xml

Restart Daemons to reread Configuration Files

There seems to be a possibility to restart at least some of the daemons so they will reread their configuration files, see daemons for more details.