Adding an IPv6 address for discovery manually makes OpenNMS need 2 attempts to start
Description
Environment
FreeBSD 8.2 AMD64
openjdk version "1.6.0"
OpenJDK Runtime Environment (build 1.6.0-b22)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
Acceptance / Success Criteria
None
Attachments
2
Lucidchart Diagrams
Activity
Show:
Matt Brozowski October 21, 2011 at 3:02 PM
I'm not sure how to reproduce this bug.. Can you reopen it with details on how to recreate it?
Benjamin Reed May 25, 2011 at 9:37 PM
Hm, I don't see anything wrong in the discovery logs (at least, from the 20th on). It acts like it's discovering v6 stuff.
Having a hard time understanding what "2 attempts to start" even really means... Which start corresponds with the failure? Did you have a clean DB or existing stuff? What's in your discovery-configuration.xml?
I can't reproduce the problem here.
Benjamin Reed May 24, 2011 at 5:56 PM
I can't reproduce this, and the dumps aren't really telling me anything all that useful. Could you bump DISCOVERY up to debug in log4j.properties and send me the discovery.log ?
I'm discovering things just fine with, eg:
Sevan Janiyan May 20, 2011 at 2:25 PM
Thread dumps extracted from output.log on startup & shutdown
Adding an IPv6 address to discovery-configuration.xml manually (because the web-ui wont allow you to) & restarting causes opennms to crash on the first attempt to start & succeeds on the subsequent attempt, it will then crash on shutdown.