Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.12.6, 1.12.7, 1.12.8, 1.12.9, 14.0.1
-
Fix Version/s: 14.0.2
-
Component/s: Alarms / Automations / Vacuumd
-
Security Level: Default (Default Security Scheme)
-
Labels:
-
Environment:OpenNMS 1.12.6 running on CentOS 6.5
Description
While generally working as designed, I notice that in some cases the syslog northbounder does not forward alerts to the syslog server and throws exceptions in alarmd.log instead:
2014-05-08 05:01:39,473 ERROR [SyslogNBI:org.opennms.netmgt.alarmd.northbounder.syslog.SyslogDestination@a54f742-Thread] SyslogNorthbounder: Caught exception sending to destination 'SEC': org.hibernate.LazyInitializationException: could not initialize proxy - no Session org.hibernate.LazyInitializationException: could not initialize proxy - no Session at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:86) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:140) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:190) at org.opennms.netmgt.model.OnmsServiceType_$$_javassist_27.getName(OnmsServiceType_$$_javassist_27.java) at org.opennms.netmgt.alarmd.northbounder.syslog.SyslogNorthbounder.createMapping(SyslogNorthbounder.java:227) at org.opennms.netmgt.alarmd.northbounder.syslog.SyslogNorthbounder.forwardAlarms(SyslogNorthbounder.java:170) at org.opennms.netmgt.alarmd.api.support.AbstractNorthbounder.run(AbstractNorthbounder.java:139) at java.lang.Thread.run(Thread.java:662)
This always happens with the same alerts types, in this case it was a 'NodeLostService' event that triggered the alarm. Other alarms such as uei.opennms.org/internal/authentication/failure consistently work OK.
