Linux – CentOs 7.1 – Install Tomcat 8

centoslinuxtomcat

I am using this tutorial as a setup reference to getting a Tomcat 8 running on CentOs 7.1, but after typing:

[root@localhost tomcat]# sudo systemctl start tomcat

I get the error:

Job for tomcat.service failed. See 'systemctl status tomcat.service' and 'journalctl -xn' for details.

systemctl status tomcat.service prints the following:

[root@localhost tomcat]# systemctl status tomcat.service
tomcat.service - Apache Tomcat Web Application Container
Loaded: loaded (/etc/systemd/system/tomcat.service; disabled)
Active: failed (Result: exit-code) since Wed 2015-11-25 16:54:33 CET; 1min 19s ago
Process: 45873 ExecStart=/opt/tomcat/bin/startup.sh (code=exited, status=203/EXEC)

Nov 25 16:54:33 localhost.localdomain systemd[1]: Starting Apache Tomcat Web Application Container...
Nov 25 16:54:33 localhost.localdomain systemd[1]: tomcat.service: control process exited, code=exited status=203
Nov 25 16:54:33 localhost.localdomain systemd[1]: Failed to start Apache Tomcat Web Application Container.
Nov 25 16:54:33 localhost.localdomain systemd[1]: Unit tomcat.service entered failed state.

journalctl -xn prints the following:

[root@localhost tomcat]# journalctl -xn
-- Logs begin at Wed 2015-11-25 13:50:17 CET, end at Wed 2015-11-25 16:54:33 CET. --
Nov 25 16:50:41 localhost.localdomain systemd[1]: Starting PostgreSQL database server...
-- Subject: Unit postgresql.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit postgresql.service has begun starting up.
Nov 25 16:50:42 localhost.localdomain systemd[1]: Started PostgreSQL database server.
-- Subject: Unit postgresql.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit postgresql.service has finished starting up.
--
-- The start-up result is done.
Nov 25 16:50:58 localhost.localdomain sshd[39118]: pam_unix(sshd:session): session closed for user demo01
Nov 25 16:50:58 localhost.localdomain systemd-logind[631]: Removed session 44.
-- Subject: A session 44 has been terminated
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A session with the ID 44 has been terminated.
Nov 25 16:54:33 localhost.localdomain sudo[45870]: root : TTY=pts/7 ; PWD=/opt/tomcat ; USER=root ; COMMAND=/bin/systemctl star
Nov 25 16:54:33 localhost.localdomain systemd[1]: Starting Apache Tomcat Web Application Container...
-- Subject: Unit tomcat.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit tomcat.service has begun starting up.
Nov 25 16:54:33 localhost.localdomain systemd[45873]: Failed at step EXEC spawning /opt/tomcat/bin/startup.sh: Permission denie
-- 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 while executing this process is 13.
Nov 25 16:54:33 localhost.localdomain systemd[1]: tomcat.service: control process exited, code=exited status=203
Nov 25 16:54:33 localhost.localdomain 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.
Nov 25 16:54:33 localhost.localdomain systemd[1]: Unit tomcat.service entered failed state.

What does the error mean and how can i get Tomcat 8 running on my CentOs 7.1 Server?

Best Answer

I've just replied here that I had the same problem and fixed it by:

giving tomcat user ownership of the whole tomcat directory:
```
cd /opt && sudo chown -R tomcat tomcat/
```

and commenting out below line in /etc/systemd/system/tomcat.service:

Environment='CATALINA_OPTS=-Xms512M -Xmx1024M -server -XX:+UseParallelGC'

Hope it helps.

Related Solutions

Linux – Systemd service start error

I'm assuming you have checked nothing else is using port 80 (which I assume lighttpd is configured to use). Check that bonescript still doesn't have the port bound, stop it with:

systemctl stop bonescript.service
systemctl stop bonescript.socket

Systemctl Service ‘systemd-modules-load’ Fails – How to Diagnose

I too had this issue. I was able to solve it by following the instructions on the Arch Linux systemd wiki page. Here is a summary of what I did :

Lets find the systemd services which fail to start

$ systemctl --failed  
------------------------------------------------------------------------
systemd-modules-load.service   loaded failed failed  Load Kernel Modules

Ok, we found a problem with systemd-modules-load service. We want to know more.

$ systemctl status systemd-modules-load  
------------------------------------------------------------------------
systemd-modules-load.service - Load Kernel Modules      
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)     
   Active: failed (Result: exit-code) since So 2013-08-25 11:48:13 CEST; 32s ago  
     Docs: man:systemd-modules-load.service(8).  
           man:modules-load.d(5)
  Process: 15630 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

If the Process ID is not listed, just restart the failed service with

$ systemctl restart systemd-modules-load

Now we have the process id (PID) to investigate this error in depth. Enter the following command with the current Process ID (here: 15630):

$ journalctl _PID=15630
----------------------------------------------------------------------
-- Logs begin at Sa 2013-05-25 10:31:12 CEST, end at So 2013-08-25 11:51:17 CEST. --
Aug 25 11:48:13 mypc systemd-modules-load[15630]: Failed to find module 'blacklist usblp'
Aug 25 11:48:13 mypc systemd-modules-load[15630]: Failed to find module 'install usblp /bin/false'

We see that some of the kernel module configs have wrong settings. Therefore we have a look at these settings in /etc/modules-load.d/

$ ls -Al /etc/modules-load.d/
----------------------------------------------------------------------
...  
-rw-r--r--   1 root root    79  1. Dez 2012  blacklist.conf  
-rw-r--r--   1 root root     1  2. Mär 14:30 encrypt.conf  
-rw-r--r--   1 root root     3  5. Dez 2012  printing.conf  
-rw-r--r--   1 root root     6 14. Jul 11:01 realtek.conf  
-rw-r--r--   1 root root    65  2. Jun 23:01 virtualbox.conf  
...

The Failed to find module 'blacklist usblp' error message might be related to a wrong setting inside of blacklist.conf. Lets deactivate it with inserting a trailing # before each option we found via step 3:
```
/etc/modules-load.d/blacklist.conf  
----------------------------------------------------------------------
# blacklist usblp  
# install usblp /bin/false  
```

Now, try to start systemd-modules-load:

$ systemctl restart systemd-modules-load

If it was successful, this should not prompt anything. If you see any error, go back to step 3 and use the new PID for solving the errors left.

If everything is ok, you can verify that the service was started successfully with:

$ systemctl status systemd-modules-load
----------------------------------------------------------------------
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: active (exited) since So 2013-08-25 12:22:31 CEST; 34s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Process: 19005 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Aug 25 12:22:31 mypc systemd[1]: Started Load Kernel Modules.

Best Answer

Related Solutions

Linux – Systemd service start error

Systemctl Service ‘systemd-modules-load’ Fails – How to Diagnose

Related Question