Tomcat8 service could not be started using tomcat8 start service

Question

I am using Vagrant to deploy on Ubuntu Linux and trying to start the tomcat8 service.

Tomcat 8 has apt-get install tomcat8 .

When using the service tomcat8 start I received the following error:

Work for tomcat8.service failed. See "Systemctl status tomcat8.service" and "journalctl -xe" for details.

Then I tracked systemctl status tomcat8.service , found that:

---

? tomcat8.service - LSB: Start Tomcat. Uploaded: uploaded (/etc/init.d/tomcat8)
Active: failed (Result: exit-code) from Monday 2016-03-28 09:44:17 GMT; 5s ago
Documents: man: systemd-sysv-generator (8)
Process: 884 ExecStop = / etc / init.d / tomcat8 stop (code = displayed, status = 0 / SUCCESS)
Process: 1312 ExecStart = / etc / init.d / tomcat8 start (code = exited, status = 1 / FAILURE)
March 28 09:44:12 vagrant-ubuntu-trusty systemd [1]: Launch LSB: Start Tomcat ....
Mar 28 09:44:12 vagrant-ubuntu-trusty tomcat8 [1312]: * Launch Tomcat tomcat8 servlet engine
Mar 28 09:44:17 vagrant-ubuntu-trusty tomcat8 [1312]: ... crash!
March 28 09:44:17 vagrant-ubuntu-trusty systemd [1]: tomcat8.service: the management process is completed, code = status output = 1
March 28 09:44:17 vagrant-ubuntu-trusty systemd [1]: LSB failed to start: start Tomcat ..
March 28 09:44:17 vagrant-ubuntu-trusty systemd [1]: Unit tomcat8.service entered a failure state.
March 28 09:44:17 vagrant-ubuntu-trusty systemd [1]: tomcat8.service failed.

I'm not sure how to get started with my Tomcat 8.

Answer 1

This may be due to this error . Recent versions of Java do not recommend the use of approved directories and fail if they are specified, but Tomcat8 indicates one, even if it does not exist. Check the /var/log/tomcat8/ as indicated in the comments on your question to see if this is really the source of your problem. If so, you can either wait for the error to be fixed, or try the updated catalina.sh file suggested in the linked error report.