Fixed
Details
Assignee
Benjamin ReedBenjamin ReedReporter
Alejandro GalueAlejandro GalueComponents
Affects versions
Priority
Major
Details
Details
Assignee
Benjamin Reed
Benjamin ReedReporter
Alejandro Galue
Alejandro GalueComponents
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created February 8, 2012 at 12:31 PM
Updated January 27, 2017 at 4:21 PM
Resolved February 8, 2012 at 3:35 PM
Some users use "etc-pristine" for the upgrade process. The problem is that the opennms-core package contains all configuration files (including files from optional packages) and put them into "etc-pristine" which is wrong.
Because 1.10 has been splitted into several packages, those configuration files which are part of the optional packages must exist (in etc-pristine and $OPENNMS_HOME/etc ) only if the user install explicitly the packages.
Here are some of the package with potential problems:
opennms-plugin-protocol-nsclient
opennms-plugin-protocol-xmp
opennms-plugin-protocol-xml
The problem reported by some users is this:
Could not load class
'org.opennms.protocols.xml.collector.XmlStorageStrategy' for resource
type 'ss7M3ua'; nested exception is java.lang.ClassNotFoundException:
org.opennms.protocols.xml.collector.XmlStorageStrategy
There is a file called etc/datacollection/3gpp.xml which contains all the resource types defined for the 3GPP data collection. This file is part of the default configuration files of the XML Collector package. Because this optional package is not installed, OpenNMS throws ClassNotFoundException.
Indeed the file does not exist in $OPENNMS_HOME/etc and when you install the package of the XML collector, the files will appear in that directory. But, even without installing the XML collector package, those files exist in "etc-pristine" as part of the opennms-core installation.