Two-digit years in timestamps and bare NTFCNCDE auto block not supported
Description
As reported on the opennms-discuss mailing list:
From: BEDIOU, stephane.bediou@capgemini.com Subject: [opennms-discuss] TL1 autonomous message configuration Date: August 24, 2009 10:22:34 AM EDT To: opennms-discuss@lists.sourceforge.net
Hi, we ave some trouble in configuring TL1 daemon. Please find herafter tl1d startup log file and output file that describe error message while receiving autonomous message from NMS. Do we have to make specific configuration or just tl1d-configuration.xml as describe in documentation ?
Thanks !
tl1d config :
2009-08-19 05:36:19,550 DEBUG [Main] DefaultTl1ConfigurationDao: Loading TL1d configuration configuration from URL [file:/opt/opennms/etc/tl1d-configuration.xml] 2009-08-19 05:36:19,572 INFO [Main] DefaultTl1ConfigurationDao: Loaded TL1d configuration in 21ms 2009-08-19 05:36:19,589 DEBUG [Main] Tl1d: OpenNMS.Tl1d initializing. 2009-08-19 05:36:19,589 INFO [Main] Tl1d: onInit: Initializing Tl1d connections. 2009-08-19 05:36:19,595 INFO [Main] Tl1d: onInit: Finished Initializing Tl1d connections. 2009-08-19 05:36:19,595 DEBUG [Main] Tl1d: OpenNMS.Tl1d initialization complete. 2009-08-19 05:36:19,595 DEBUG [Main] Tl1d: SPRING: context.classLoader= java.net.FactoryURLClassLoader@11b86e7 2009-08-19 05:36:20,887 DEBUG [Main] Tl1d: OpenNMS.Tl1d starting. 2009-08-19 05:36:20,887 INFO [Main] Tl1d: onStart: Initializing Tl1d message processing. 2009-08-19 05:36:20,888 INFO [Main] Tl1d: start: TL1 client: 10.68.153.15:8003 2009-08-19 05:36:20,888 INFO [Main] Tl1d: start:Connection delay = 30000 2009-08-19 05:36:20,889 DEBUG [Tl1-Message-Processor] Tl1d: doMessageProcessing: Processing messages. 2009-08-19 05:36:20,890 INFO [Main] Tl1d: Started TL1 client: 10.68.153.15:8003 2009-08-19 05:36:20,890 INFO [Main] Tl1d: onStart: Finished Initializing Tl1d connections. 2009-08-19 05:36:20,890 INFO [Main] Tl1d: OpenNMS.Tl1d started. 2009-08-19 05:36:20,891 INFO [TL1-Socket-Reader] Tl1d: readMessages: Begin reading off socket... 2009-08-19 05:36:20,892 INFO [TL1-Socket-Reader] Tl1d: readMessages: reading line from TL1 socket... 2009-08-19 05:36:20,896 DEBUG [TL1-Socket-Reader] Tl1d: resetTimeout: Resetting timeout Thread 2009-08-19 05:56:16,790 DEBUG [TL1-Socket-Reader] Tl1d: readMessages: offering message to queue: DSALC003 09-04-20 07:38:35
parseAutoBlock: Autoblock: "ENV-2:MJ,MISC,4-7,7-30-15,\"Miscellaneous environment alarm\"" parseAutoBlock: aidAndCode: "ENV-2:MJ Exception in thread "TL1-Socket-Reader" java.util.NoSuchElementException at java.util.StringTokenizer.nextToken(StringTokenizer.java:332) at org.opennms.netmgt.tl1d.Tl1AutonomousMessageProcessor.parseAutoBlock(Tl1AutonomousMessageProcessor.java:188) at org.opennms.netmgt.tl1d.Tl1AutonomousMessageProcessor.processAutoBlock(Tl1AutonomousMessageProcessor.java:152) at org.opennms.netmgt.tl1d.Tl1AutonomousMessageProcessor.process(Tl1AutonomousMessageProcessor.java:64) at org.opennms.netmgt.tl1d.Tl1ClientImpl.detectMessageType(Tl1ClientImpl.java:219) at org.opennms.netmgt.tl1d.Tl1ClientImpl.createAndQueueTl1Message(Tl1ClientImpl.java:203) at org.opennms.netmgt.tl1d.Tl1ClientImpl.readMessages(Tl1ClientImpl.java:187) at org.opennms.netmgt.tl1d.Tl1ClientImpl.access$000(Tl1ClientImpl.java:56) at org.opennms.netmgt.tl1d.Tl1ClientImpl$1.run(Tl1ClientImpl.java:99)
Environment
Operating System: All
Platform: PC
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Benjamin Reed September 17, 2009 at 11:58 AM
unit test, yay!
merged to branches/1.6 in r14681
Jeff Gehlbach August 25, 2009 at 2:01 PM
Fix committed to 1.6-testing at r14486 and merged to trunk at r14491.
As reported on the opennms-discuss mailing list:
From: BEDIOU, stephane.bediou@capgemini.com
Subject: [opennms-discuss] TL1 autonomous message configuration
Date: August 24, 2009 10:22:34 AM EDT
To: opennms-discuss@lists.sourceforge.net
Hi, we ave some trouble in configuring TL1 daemon.
Please find herafter tl1d startup log file and output file that describe error message while receiving autonomous message from NMS.
Do we have to make specific configuration or just tl1d-configuration.xml as describe in documentation ?
Thanks !
tl1d config :
2009-08-19 05:36:19,550 DEBUG [Main] DefaultTl1ConfigurationDao: Loading TL1d configuration configuration from URL [file:/opt/opennms/etc/tl1d-configuration.xml]
2009-08-19 05:36:19,572 INFO [Main] DefaultTl1ConfigurationDao: Loaded TL1d configuration in 21ms
2009-08-19 05:36:19,589 DEBUG [Main] Tl1d: OpenNMS.Tl1d initializing.
2009-08-19 05:36:19,589 INFO [Main] Tl1d: onInit: Initializing Tl1d connections.
2009-08-19 05:36:19,595 INFO [Main] Tl1d: onInit: Finished Initializing Tl1d connections.
2009-08-19 05:36:19,595 DEBUG [Main] Tl1d: OpenNMS.Tl1d initialization complete.
2009-08-19 05:36:19,595 DEBUG [Main] Tl1d: SPRING: context.classLoader= java.net.FactoryURLClassLoader@11b86e7
2009-08-19 05:36:20,887 DEBUG [Main] Tl1d: OpenNMS.Tl1d starting.
2009-08-19 05:36:20,887 INFO [Main] Tl1d: onStart: Initializing Tl1d message processing.
2009-08-19 05:36:20,888 INFO [Main] Tl1d: start: TL1 client: 10.68.153.15:8003
2009-08-19 05:36:20,888 INFO [Main] Tl1d: start:Connection delay = 30000
2009-08-19 05:36:20,889 DEBUG [Tl1-Message-Processor] Tl1d: doMessageProcessing: Processing messages.
2009-08-19 05:36:20,890 INFO [Main] Tl1d: Started TL1 client: 10.68.153.15:8003
2009-08-19 05:36:20,890 INFO [Main] Tl1d: onStart: Finished Initializing Tl1d connections.
2009-08-19 05:36:20,890 INFO [Main] Tl1d: OpenNMS.Tl1d started.
2009-08-19 05:36:20,891 INFO [TL1-Socket-Reader] Tl1d: readMessages: Begin reading off socket...
2009-08-19 05:36:20,892 INFO [TL1-Socket-Reader] Tl1d: readMessages: reading line from TL1 socket...
2009-08-19 05:36:20,896 DEBUG [TL1-Socket-Reader] Tl1d: resetTimeout: Resetting timeout Thread
2009-08-19 05:56:16,790 DEBUG [TL1-Socket-Reader] Tl1d: readMessages: offering message to queue: DSALC003 09-04-20 07:38:35
169 REPT ALM ENV
"ENV-2:MJ,MISC,4-7,7-30-15,\"Miscellaneous environment alarm\""
;
output.log
parseAutoBlock: Autoblock: "ENV-2:MJ,MISC,4-7,7-30-15,\"Miscellaneous environment alarm\""
parseAutoBlock: aidAndCode: "ENV-2:MJ
Exception in thread "TL1-Socket-Reader" java.util.NoSuchElementException
at java.util.StringTokenizer.nextToken(StringTokenizer.java:332)
at org.opennms.netmgt.tl1d.Tl1AutonomousMessageProcessor.parseAutoBlock(Tl1AutonomousMessageProcessor.java:188)
at org.opennms.netmgt.tl1d.Tl1AutonomousMessageProcessor.processAutoBlock(Tl1AutonomousMessageProcessor.java:152)
at org.opennms.netmgt.tl1d.Tl1AutonomousMessageProcessor.process(Tl1AutonomousMessageProcessor.java:64)
at org.opennms.netmgt.tl1d.Tl1ClientImpl.detectMessageType(Tl1ClientImpl.java:219)
at org.opennms.netmgt.tl1d.Tl1ClientImpl.createAndQueueTl1Message(Tl1ClientImpl.java:203)
at org.opennms.netmgt.tl1d.Tl1ClientImpl.readMessages(Tl1ClientImpl.java:187)
at org.opennms.netmgt.tl1d.Tl1ClientImpl.access$000(Tl1ClientImpl.java:56)
at org.opennms.netmgt.tl1d.Tl1ClientImpl$1.run(Tl1ClientImpl.java:99)