/etc/init.d/opennms startup and shutdown fail or timeout
Description
Hi!
Updated my install with 1.12 branch to test and modify xmp code. I notice that when I use /etc/init.d/opennms to start everything, it comes back as failed even though things eventually run. It looks like jetty is my culprit. I put START_TIMEOUT=15 in opennms.conf and it still times out.
Similar issue with shutdown using /etc/init.d/opennms – shutdown will say its complete but java still running. running bin/opennms -v status shows items still running. Puzzled.
Bobby
Environment
Linux fedora 15 VM
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Seth Leger March 30, 2016 at 5:38 PM
I don't think anyone has noted any OpenNMS startup issues since our round of bugfixes for OpenNMS 14. Marking as fixed.
Seth Leger November 21, 2013 at 9:42 PM
This is a bit of a long-standing issue. It's exacerbated by running on slower machines that simply cannot crank up the JVM quickly enough but I've been noticing slowdowns on my machine lately due to initializing RMI during startup.
We should revisit the init code a bit and provide more accurate monitoring of the startup process instead of just running "service opennms status" a few times and "failing" when it doesn't come back in a certain timeout.
Hi!
Updated my install with 1.12 branch to test and modify xmp code. I notice that when I use /etc/init.d/opennms to start everything, it comes back as failed even though things eventually run. It looks like jetty is my culprit. I put START_TIMEOUT=15 in opennms.conf and it still times out.
Similar issue with shutdown using /etc/init.d/opennms – shutdown will say its complete but java still running. running bin/opennms -v status shows items still running. Puzzled.
Bobby