Starting EAP 6 RPM install sometimes falsely reports "Process crashed on startup"
Issue
- We've installed EAP 6 from the RPM. Starting up sometimes we see "Process crashed on startup" immediately.
- This occurs because multiple pids are unexpectedly seen at the below lines in the service script:
echo `pidof -x "$JBOSSSH_only"` > $JBOSSPID
read ppid < $JBOSSPID
if [ ! -z $ppid ]; then
if [ `ps --pid $ppid 2> /dev/null | grep -c $ppid 2> /dev/null` -eq '1' ]; then
- The child process being started up is still seen at this line in a state similar to the parent process as it is being forked:
16498 ? S 0:00 $EAP_HOME/bin/CLOUD_0000.sh -P standalone.conf-c standalone-full-ha.xml
16593 ? S 0:00 \_ /$EAP_HOME/bin/CLOUD_0000.sh -P standalone.conf -c standalone-full-ha.xml
Environment
- JBoss Enterprise Application Platform (EAP) 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
