EmersonPrado
commented
1 year ago Which Suse version? I presume it's a recent enough one so it uses systemd. Or was at the time, since the issue is quite old...
I hit this error with a RedHat version with systemd, which doesn't have /etc/init.d - it's a SysV specific directory. That is, the module is trying to setup SysV files in a systemd OS.
Make sure you have jethrocarr/initfact module installed, from the module setup requirements. This is what detects the init system correctly for class wildfly::service. Without this module, function wildfly::service_config tries to do it, but I have to say it's not that good in it (probably written before the newer OS versions).
Otherwise, you might have to play with wildfly::service parameters.
I am working with SUSE Linux. I am running this Module on my Puppet Master and on my agent i am running JBOSS-EAP.
/var/log/jboss-eap/console.log
Loaded: loaded (/etc/systemd/system/jboss-eap.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2018-11-14 16:32:46 CET; 13s ago Process: 18637 ExecStop=/etc/init.d/jboss-eap stop (code=exited, status=0/SUCCESS) Process: 18986 ExecStart=/etc/init.d/jboss-eap start (code=exited, status=1/FAILURE)
Nov 14 16:32:46 suse001 systemd[1]: Starting Wildfly Application Server... Nov 14 16:32:46 suse001 jboss-eap[18986]: /etc/init.d/jboss-eap: line 13: /etc/init.d/functions: No such file or directory Nov 14 16:32:46 suse001 systemd[1]: jboss-eap.service: Control process exited, code=exited status=1 Nov 14 16:32:46 suse001 systemd[1]: Failed to start Wildfly Application Server. Nov 14 16:32:46 suse001 systemd[1]: jboss-eap.service: Unit entered failed state. Nov 14 16:32:46 suse001 systemd[1]: jboss-eap.service: Failed with result 'exit-code'.