Closed Footur closed 1 year ago
It's a bug, it's also happening with Wildfly:
Jun 05 06:54:48 3eb5d5439a1e standalone.sh[751]: /opt/wildfly/wildfly-27.0.0.Final/bin/standalone.sh: line 384: wildfly.pid: Permission denied
Thanks for reporting this! We'll try to fix asap and release the fixed collection as quickly as possible.
Note: If you are deploying JBoss EAP (and not Wildfly) you should use the downstream version of this collection redhat.eap, available on Ansible Automation Hub.
SUMMARY
The installation of JBoss EAP using the provided Ansible Role was successful; however, a PID (Process ID) file is not being created during startup. The following error message is displayed:
"Jun 02 10:49:34 localhost.localdomain standalone.sh[648]: /opt/jboss/jboss-eap-7.4/bin/standalone.sh: line 369: jboss-eap.pid: Permission denied."
ISSUE TYPE
ANSIBLE VERSION
COLLECTION VERSION
STEPS TO REPRODUCE
EXPECTED RESULTS
Upon starting JBoss EAP, a PID file should be created without any permission issues.
ACTUAL RESULTS
The PID file is not created during the startup process, and the log displays the error message:
"Jun 02 10:49:34 localhost.localdomain standalone.sh[648]: /opt/jboss/jboss-eap-7.4/bin/standalone.sh: line 369: jboss-eap.pid: Permission denied."
Please let me know if any further details or log files are required to troubleshoot and resolve this issue.