Wildfly will not start

book

Article ID: 196276

calendar_today

Updated On:

Products

CA Virtual Network Assurance

Issue/Introduction

When trying to upgrade VNA, we noticed Wildfly will not start

Cause

When checking wildfly's status, the following is shown:

systemctl status wildfly.service
wildfly.service - LSB: WildFly Application Server
   Loaded: loaded (/etc/rc.d/init.d/wildfly; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2020-07-28 10:05:47 EDT; 4min 21s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 16514 ExecStart=/etc/rc.d/init.d/wildfly start (code=exited, status=1/FAILURE)
 Main PID: 12155

systemd[1]: Starting LSB: WildFly Application Server...
wildfly[16514]: The user "wildfly" is not owner of "/opt/CA/VNA/wildfly"
wildfly[16514]: Try: chown -R wildfly:wildfly "/opt/CA/VNA/wildfly"
systemd[1]: wildfly.service: control process exited, code=exited status=1
systemd[1]: Failed to start LSB: WildFly Application Server.
systemd[1]: Unit wildfly.service entered failed state.
systemd[1]: wildfly.service failed.

Environment

Component : Virtual Network Assurance

Resolution

The following message is called out in the status call that describes the root cause and its resolution:

wildfly[16514]: The user "wildfly" is not owner of "/opt/CA/VNA/wildfly"
wildfly[16514]: Try: chown -R wildfly:wildfly "/opt/CA/VNA/wildfly"

The wildfly directory needs to be owned by the wildfly user and this can be accomplished by running the suggested command:

chown -R wildfly:wildfly "/opt/CA/VNA/wildfly"

Additional Information

Note: If you are running the Centrify application on the VNA system, it is possible for it to inhibit your chown command.  If you are running Centrify or the like and the chown command seems successful but the file ownership never changes, please reach out to your Linux administration team for further assistance.