How To Install Apache Tomcat 8 on Ubuntu 16.04

To ensure the Tomcat service re-starting at boot, you have to enable it:

$ sudo systemctl enable tomcat

Hello,

For me (in ubuntu 14 (i know this is for ubuntu 16)), in the step 4 : sudo chmod g+r conf/* ==> does not work “No file or directory”.

Is it normal ?

Thanks for the step by step tomcat installation procedure.

I get error in the step when we start the tomcat service sudo systemctl start tomcat On checking the status by this command - sudo systemctl status tomcat. I see following error - Jun 27 16:09:52 maddy-VirtualBox systemd[6182]: tomcat.service: Failed at step EXEC spawning /opt/tomcat/bin/startup.sh: Permission denied

Although I am logged in as user (which has sudo privileges) still I am getting Permission denied error. I have also changed the ownership of /opt/tomcat/bin directory to the user from which I am firing those commands, still the error is coming.

Can anybody help me in this problem?

Hello, I’ve got this error and can not shutdown the tomcat properly. Is there a way to solve it?

Using CATALINA_BASE: /opt/tomcat
Using CATALINA_HOME: /opt/tomcat
Using CATALINA_TMPDIR: /opt/tomcat/temp
Using JRE_HOME: /usr/lib/jvm/java-8-oracle/jre
Using CLASSPATH: /opt/tomcat/bin/bootstrap.jar:/opt/tomcat/bin/tomcat-juli.jar
Jul 06, 2016 5:54:58 PM org.apache.catalina.startup.Catalina stopServer
SEVERE: Could not contact localhost:8005. Tomcat may not be running.
Jul 06, 2016 5:54:58 PM org.apache.catalina.startup.Catalina stopServer
SEVERE: Catalina.stop:
java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at java.net.Socket.connect(Socket.java:538)
	at java.net.Socket.<init>(Socket.java:434)
	at java.net.Socket.<init>(Socket.java:211)
	at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:476)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:408)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:497)

Thank you.

If you are having problems getting tomcat 8 to start and getting this error

● tomcat.service - Apache Tomcat Web Application Container Loaded: loaded (/etc/systemd/system/tomcat.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2016-07-30 12:15:27 EDT; 1s ago Process: 13807 ExecStart=/opt/tomcat/bin/startup.sh (code=exited, status=203/EXEC) Jul 30 12:15:27 xxxxxxx systemd[1]: Failed to start Apache Tomcat Web Application Container. Jul 30 12:15:27 xxxxxxx systemd[1]: tomcat.service: Unit entered failed state. Jul 30 12:15:27 xxxxxxxxx systemd[1]: tomcat.service: Failed with result ‘exit-code’.

then you might want to give tomcat user ownership of the whole tomcat directory:

cd /opt && sudo chown -R tomcat tomcat/

Worked for me.

See http://unix.stackexchange.com/questions/235891/tomcat-8-will-not-start-after-initial-install

This comment has been deleted

This comment has been deleted

Hi

Just installed Tomcat 8on Ubuntu 16.04 . Changed the Tomcat-user.xml file too with manager-gui role and changed the password , but I keep getting the 403 Access Denied Page when I click the Manager App from the Tomcat 8

Is there some permissions I have not set ?

Thanks

Hi, i have been trying to figure this out for a week but unable to get Tomcat 8 to start while following this guide.

-- 
-- Unit tomcat.service has failed.
-- 
-- The result is failed.
Aug 22 00:12:17 aimed-ubuntu-blr systemd[1]: tomcat.service: Unit entered failed state.
Aug 22 00:12:17 aimed-ubuntu-blr systemd[1]: tomcat.service: Failed with result 'exit-code'.
Aug 22 00:12:27 aimed-ubuntu-blr systemd[1]: tomcat.service: Service hold-off time over, scheduling restart.
Aug 22 00:12:27 aimed-ubuntu-blr systemd[1]: Stopped Apache Tomcat Web Application Container.
-- Subject: Unit tomcat.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tomcat.service has finished shutting down.
Aug 22 00:12:27 aimed-ubuntu-blr systemd[1]: Starting Apache Tomcat Web Application Container...
-- Subject: Unit tomcat.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tomcat.service has begun starting up.
Aug 22 00:12:27 aimed-ubuntu-blr systemd[26177]: tomcat.service: Failed at step EXEC spawning /opt/tomcat/bin/startup.sh: Permission denied
-- Subject: Process /opt/tomcat/bin/startup.sh could not be executed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The process /opt/tomcat/bin/startup.sh could not be executed and failed.
-- 
-- The error number returned by this process is 13.
Aug 22 00:12:27 aimed-ubuntu-blr systemd[1]: tomcat.service: Control process exited, code=exited status=203
Aug 22 00:12:27 aimed-ubuntu-blr systemd[1]: Failed to start Apache Tomcat Web Application Container.
-- Subject: Unit tomcat.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tomcat.service has failed.
-- 
-- The result is failed.
Aug 22 00:12:27 aimed-ubuntu-blr systemd[1]: tomcat.service: Unit entered failed state.
Aug 22 00:12:27 aimed-ubuntu-blr systemd[1]: tomcat.service: Failed with result 'exit-code'.

Im having a issue that when I restarted the Ubuntu 16.04 running Tomcat 8, it would not let me access…

I saw that it was binding it to IPv6 so I disabled it a kernel level. Now it is listening to IPv4 but it still does not let me access.