Issues
- SyslogNBI - Configuration changes and subsequent reloads not functioning as expectedNMS-12394Resolved issue: NMS-12394
- Bad substitution in JMS alarm northbounder component-dao wiringNMS-7948Resolved issue: NMS-7948Jeff Gehlbach
- Syslog Northbounder runs in a NullPointerExceptionNMS-6383Resolved issue: NMS-6383Alejandro Galue
3 of 3
SyslogNBI - Configuration changes and subsequent reloads not functioning as expected
Cannot Reproduce
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Details
Assignee
UnassignedUnassignedReporter
Sean TorresSean TorresComponents
Sprint
NoneAffects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
Sean Torres
Sean TorresComponents
Sprint
None
Affects versions
Priority
MajorPagerDuty
PagerDuty
PagerDuty
Created November 12, 2019 at 3:36 AM
Updated December 5, 2019 at 4:52 AM
Resolved December 5, 2019 at 4:52 AM
Activity
Show:
Sean TorresDecember 5, 2019 at 4:52 AM
Issue may be related to external dependency. Closed as cannot reproduce issue at present.
Chen Khin WaiNovember 28, 2019 at 12:19 AM
This might not be an issue with OpenNMS. I just got to know that someone changed the VIP settings in Load Balancer that causes the instability. Troubleshoot with nc command and shows connection refuse to VIP and works when connect to server directly. Please close this bug for now. We can reopen if it reoccurs.
Chen Khin WaiNovember 22, 2019 at 3:03 PM
Getting a lot of connection refuse error in output.log. Nothing is change from either side. We just did a restart.
[org.graylog2.syslog4j.SyslogRuntimeException: java.net.ConnectException: Connection refused (Connection refused)]
Steps to Reproduce: (type one)
1) Disable Syslog Northbounder by changing enabled flag to false
2) Restart OpenNMS
3) After cmd "opennms -v status" reports everything as running, wait an additional 30 minutes (it could be less or as little as 15 mins)
4) Enable the Syslog Northbounder by changing enabled flag to true
5) Send Event to reload configuration for SyslogNBI
6) No packets sent to SyslogNBI destination.
Steps to Reproduce: (type two)
1) System is up with NBI enabled and sending from OpenNMS service start
2) Disable NBI and send event to reload config
3) Messages stop being sent
4) Update NBI config, change destination host, enable NBI in config
5) Send event to reload config
6) Messages are being sent to old host and not new host