Did you check your server.log?
Thanks for the response Wolfgang but there are no logs at all. It seems that the service never even gets started. Any other ideas?
I understand you installed the WildFly start script into the /etc/init.d directory as it is the case for the init process (systemd usually looks into /etc/systemd/system)
Maybe there is an issue with your wildfly start script.
So you could try to start WildFly directly like:
sudo /etc/init.d/wildfly start
Thanks for the suggestion. Here's what happens:
myuser@ip-172-31-27-23:~⟫ sudo /etc/init.d/wildfly start
[sudo] password for myuser:
Starting wildfly (via systemctl): wildfly.serviceJob for wildfly.service failed because the control process exited with error code. See "systemctl status wildfly.service" and "journalctl -xe" for details.
1 myuser@ip-172-31-27-23:~⟫ systemctl status wildfly.service
● wildfly.service - LSB: WildFly Application Server
Loaded: loaded (/etc/init.d/wildfly; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-08-04 17:13:27 UTC; 17s ago
Process: 6962 ExecStart=/etc/init.d/wildfly start (code=exited, status=1/FAILURE)
I still have this "bad; vendor preset: enabled" error but I have no idea what it means. Can you help?
Thank you for your assistance.
"bad; vendor preset: enabled" as such is not an error (systemd - sudo service status includes bad; - Ask Ubuntu )
But your "/etc/init.d/wildfly start" command exited with status=1 (generic or unspecified error).
Since this is comming from your start script, I'd suggest that you analyse your /etc/init.d/wildfly script and check under which conditions the status 1 is returned in the start function.
One reason might be that the $JBOSS_PIDFILE is still available or some file permission is missing.
I am very new to Wildfly so please bear with me. I am using the standard script with no changes as supplied by the Wildfly installation and frankly have no idea what it is doing. I am running this under a stock Ubuntu 16.04 so I'm very surprised that this just "simply run out of the box". I really don't know how to debug the script file. Since this is the official JBoss site I would really think somebody would understand what has gone wrong with the default script. I'm not sure how to proceed. Thank you for your ongoing help.
I am not sure what you mean with the 'official JBoss site'. Under $JBOSS_HOME/docs/contrib/scripts/init.d/ you should find examples for Debian and Redhat. But there is no 'default'. And it is difficult to analyze issues if you don't understand your environment. But if you open eg wildfly-init-redhat.sh you will see that the script logs to $JBOSS_CONSOLE_LOG.
So if you run 'export JBOSS_USER=wildfly && /etc/init.d/wildfly start' you might see something like:
Starting wildfly: chown wildfly /var/run/wildfly || true
wildfly started with errors, please see server log for details
In the $JBOSS_CONSOLE_LOG (eg /var/log/wildfly/console.log) you will probably find some 'permission denied' messages there.