Syslog Northbounder runs in a NullPointerException
Description
Acceptance / Success Criteria
None
Attachments
2
Lucidchart Diagrams
Activity
Show:
Fixed
Details
Assignee
Alejandro GalueAlejandro GalueReporter
Ronny TrommerRonny TrommerLabels
Components
Sprint
NoneFix versions
Affects versions
Priority
Major
Details
Details
Assignee

Reporter

Labels
Components
Sprint
None
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Created February 5, 2014 at 12:00 PM
Updated January 27, 2017 at 4:20 PM
Resolved April 25, 2014 at 11:13 AM
I tried to build a minimal setup to use the Syslog-Northbounder to forward Alarms to a syslog server. I build a minimal setup on CentOS 6.5 with rsyslog. The configuration from my rsyslog daemon is attached on the issue. I've also attached my syslog-northbounder-configuration.xml. In my example the rsyslog server is running on localhost listening on TCP/127.0.0.1:514. Syslogd in OpenNMS is not running. The setup is just in a test environment so I don't filter UEI's and want to forward all generated OpenNMS Alarms to syslog. In Alarmd log file the following error message appears after creating an outage for a node by setting a null route to the IP address.
This issue can be verified running the OpenNMS Vagrant box and using the two configuration files attached to this issue. http://www.opennms.org/wiki/OpenNMS_and_Vagrant_with_VirtualBox