ahoiroman
commented
2 months ago True for me, too. But it also does not work with Wildfly 10.
Open bmcnally-uw opened 9 months ago
ahoiroman
commented
2 months ago True for me, too. But it also does not work with Wildfly 10.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
class { 'wildfly': version => '31.0.0', install_source => 'https://github.com/wildfly/wildfly/releases/download/31.0.0.Final/wildfly-31.0.0.Final.tar.gz', install_cache_dir => '/tmp', java_home => '/usr/lib/jvm/java-21-openjdk-amd64', dirname => '/data/wildfly', }
What are you seeing
Wildfly fails to start through systemd. journalctl -u wildfly.service says:
systemd[1]: wildfly.service: Failed with result 'exit-code'.And systemctl says:● wildfly.service - WildFly application server Loaded: loaded (/etc/systemd/system/wildfly.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Thu 2024-02-15 15:52:44 PST; 10s ago Process: 2192950 ExecStart=/data/wildfly/bin/launch.sh ${WILDFLY_MODE} ${WILDFLY_CONFIG} (code=exited, status=1/FAILURE) Main PID: 2192950 (code=exited, status=1/FAILURE) CPU: 1.648sIf I run the service manually (outside of systemd) by exporting the variables defined in /etc/wildfly/wildfly.conf, after fixing WILDFLY_CONFIG's quoting issues, I am able to start the service successfully.What behaviour did you expect instead
Output log
Any additional information you'd like to impart
/etc/wildfly/wildfly.conf has this defined, but I'm not sure the quoting is correct here:
# The configuration you want to run WILDFLY_CONFIG="'standalone.xml -P /data/wildfly/jboss.properties'"Wildfly 30.0.0 works fine if I swap that in instead of 31.0.0.