wildfly-init-debian.sh gives a check status return code 4 and does not start

[wesseloc]

Using the example wildfly-init-debian.sh on ubuntu 12.04 fails to start.

After some scratching it seems that this line is pidofproc -p $JBOSS_PIDFILE $JAVA >/dev/null 2>&1 is setting the  status to 4. Meaning it cannot determine the pid file status.

The service is being run as root. Anybody got any idea how to solve this?

Kind Regards

[wesseloc]

Okay after allot of fiddling I seemed to find a workaround on Ubuntu 12.04.

Seem to have found a work around for it. I modified my pidofproc return a status code of 3 when the PID is not found but the -p (with PID path) is specified. 

The service now starts up. Is seems it was failing because pidofproc was not finding the PID file (because it was not present at first run) and then returned status 4 (cannot determine state of PID).

This causes the script to hang as there is no catch for the option 4.

[jaikiran]

Wessel Pieterse wrote:

Is seems it was failing because pidofproc was not finding the PID file (because it was not present at first run) and then returned status 4 (cannot determine state of PID).

This causes the script to hang as there is no catch for the option 4.

Would you like to contribute this fix to the WildFly codebase? If yes, then please create a pull request with the fix and submit it to the WildFly upstream repo. More details here https://community.jboss.org/wiki/HackingOnWildFly

[ramiz.ismailov]

I don't think it's a good workaround to change the pidofproc, since it could be used by other scripts.

I've stumbled on the same issue and fixed my /etc/init.d/wildfly script as following:

in line

if [ $status_start -eq 3 ]; then

replaced -eq by -ge, that is, I got

if [ $status_start -ge 3 ]; then

so it will work for both 3 and 4

[wesseloc]

Hi

The pidofproc changes I made was from a proposed patch to the function . But this solution is much better. Thank you! Maybe you should do a pull request to Wildfly because this solves the issue 100%.

[graham.stewart]

This problem still exists with 8.1.0.Final.Your fix solved it.

You also need to change the same test in the shutdown wait loop in the stop command

as it will time out and try to kill an unknown process

thanks

Graham

[jaikiran]

Please do file a JIRA WildFly - JBoss Issue Tracker and propose this patch or issue a pull request so that this gets fixed. Else you will end up seeing this issue in every other release.

[jorsol]

There must be something wrong with your setup... how do you install wildfly?

This script is tested and fully works in Ubuntu 12.04... can you provide more details about your enviroment?

do you set JAVA_HOME or any other enviroment variable?

Can you try by simply deleting the /var/run/wildfly directory and start the service again.