https://bz.apache.org/bugzilla/show_bug.cgi?id=63041
--- Comment #14 from no...@email.it --- This fix seems to break the shell script /etc/init.d/tomcat I use to manage Tomcat as a service with systemd (generated from init.d): https://git.io/fhQv4 Output follows: $ sudo service tomcat start Job for tomcat.service failed because the control process exited with error code. See "systemctl status tomcat.service" and "journalctl -xe" for details. $ systemctl status tomcat.service ● tomcat.service - LSB: Start Tomcat. Loaded: loaded (/etc/init.d/tomcat; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-02-10 21:11:07 CET; 7s ago Docs: man:systemd-sysv-generator(8) Process: 4938 ExecStop=/etc/init.d/tomcat stop (code=exited, status=0/SUCCESS) Process: 5066 ExecStart=/etc/init.d/tomcat start (code=exited, status=1/FAILURE) CGroup: /system.slice/tomcat.service ├─5094 /bin/sh /opt/tomcat/bin/catalina.sh start └─5095 /usr/lib/jvm/java-8-oracle/bin/java -Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties Feb 10 21:11:02 raspberrypi systemd[1]: Starting LSB: Start Tomcat.... Feb 10 21:11:07 raspberrypi tomcat[5066]: Starting Tomcat servlet engine: tomcat failed! Feb 10 21:11:07 raspberrypi systemd[1]: tomcat.service: Control process exited, code=exited status=1 Feb 10 21:11:07 raspberrypi systemd[1]: Failed to start LSB: Start Tomcat.. Feb 10 21:11:07 raspberrypi systemd[1]: tomcat.service: Unit entered failed state. Feb 10 21:11:07 raspberrypi systemd[1]: tomcat.service: Failed with result 'exit-code'. $ journalctl -xe Feb 10 21:11:02 raspberrypi systemd[1]: Starting LSB: Start Tomcat.... -- Subject: Unit tomcat.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit tomcat.service has begun starting up. Feb 10 21:11:07 raspberrypi tomcat[5066]: Starting Tomcat servlet engine: tomcat failed! Feb 10 21:11:07 raspberrypi systemd[1]: tomcat.service: Control process exited, code=exited status=1 Feb 10 21:11:07 raspberrypi systemd[1]: Failed to start LSB: Start Tomcat.. -- Subject: Unit tomcat.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit tomcat.service has failed. -- -- The result is failed. Feb 10 21:11:07 raspberrypi systemd[1]: tomcat.service: Unit entered failed state. Feb 10 21:11:07 raspberrypi systemd[1]: tomcat.service: Failed with result 'exit-code'. That /etc/init.d/tomcat script is a slightly modified version of the one accompanying the Tomcat 8 package distributed with Debian APT. It's worth noting that the server eventually starts despite the error, but I'm not able to manage it as a service afterwards. Now I'm using the old catalina.sh from v9.0.14 that works fine, but I'm considering whether it is better to modify my script in order to support the new catalina.sh or not. Thanks for your great work. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
