Tomcat: Can't start tomcat after installing it on Ubuntu: "Job for tomcat.service failed because the control process exited with error code."

Question

I followed the steps https://www.digitalocean.com/community/tutorials/how-to-install-apache-tomcat-8-on-ubuntu-16-04 to install tomcat 8.5.24 on Ubuntu 16.04, till running sudo ufw allow 8080 in "Step 6: Adjust the Firewall and Test the Tomcat Server".

然后就无法启动tomcat，

$ sudo systemctl start tomcat
Job for tomcat.service failed because the control process exited with error code. See "systemctl status tomcat.service" and "journalctl -xe" for details.

并且链接http://localhost:8080/在 firefox 和 google chrome 浏览器中都不起作用。

我想知道如何解决这个问题。

以下详细信息是我遵循sudo systemctl start tomcat的上述 output 消息的内容。 似乎/opt/tomcat/bin/startup.sh成功，而/opt/tomcat/bin/shutdown.sh失败。 非常感谢您的帮助！

$ systemctl status tomcat.service
● tomcat.service - Apache Tomcat Web Application Container
   Loaded: loaded (/etc/systemd/system/tomcat.service; disabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2017-12-01 18:55:30 EST; 2s ago
  Process: 19490 ExecStop=/opt/tomcat/bin/shutdown.sh (code=exited, status=1/FAILURE)
  Process: 19478 ExecStart=/opt/tomcat/bin/startup.sh (code=exited, status=0/SUCCESS)
 Main PID: 19440 (code=exited, status=127)

Dec 01 18:55:30 ocean systemd[1]: tomcat.service: Control process exited, code=exited status=1
Dec 01 18:55:30 ocean systemd[1]: Failed to start Apache Tomcat Web Application Container.
Dec 01 18:55:30 ocean systemd[1]: tomcat.service: Unit entered failed state.
Dec 01 18:55:30 ocean systemd[1]: tomcat.service: Failed with result 'exit-code'.

$ journalctl -xe

-- Unit tomcat.service has begun starting up.
Dec 01 18:51:24 ocean startup.sh[18873]: Existing PID file found during start.
Dec 01 18:51:24 ocean startup.sh[18873]: Removing/clearing stale PID file.
Dec 01 18:51:24 ocean startup.sh[18873]: Tomcat started.
Dec 01 18:51:24 ocean shutdown.sh[18885]: PID file found but no matching process was found. Stop aborted.
Dec 01 18:51:24 ocean systemd[1]: tomcat.service: Control process exited, code=exited status=1
Dec 01 18:51:24 ocean 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.
Dec 01 18:51:24 ocean systemd[1]: tomcat.service: Unit entered failed state.
Dec 01 18:51:24 ocean systemd[1]: tomcat.service: Failed with result 'exit-code'.
Dec 01 18:51:34 ocean systemd[1]: tomcat.service: Service hold-off time over, scheduling restart.
Dec 01 18:51:34 ocean 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.
Dec 01 18:51:34 ocean 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.
Dec 01 18:51:35 ocean startup.sh[18896]: Existing PID file found during start.
Dec 01 18:51:35 ocean startup.sh[18896]: Removing/clearing stale PID file.
Dec 01 18:51:35 ocean startup.sh[18896]: Tomcat started.
Dec 01 18:51:35 ocean shutdown.sh[18908]: PID file found but no matching process was found. Stop aborted.
Dec 01 18:51:35 ocean systemd[1]: tomcat.service: Control process exited, code=exited status=1
Dec 01 18:51:35 ocean 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.
Dec 01 18:51:35 ocean systemd[1]: tomcat.service: Unit entered failed state.
Dec 01 18:51:35 ocean systemd[1]: tomcat.service: Failed with result 'exit-code'.

我的 Java 版本是

$ java --version
java 9.0.1
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)

$ javac --version
javac 9.0.1

---

更新：

如果我运行，而不是sudo systemctl start tomcat会给出上述错误

cd /opt/tomcat/bin

sudo ./catalina.sh run

http://localhost:8080/显示正确的网页。 那么一个不起作用而另一个起作用的原因是什么？

Answer 1

使用户tomcat成为整个 tomcat 目录的所有者：

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

Answer 2

我通过从/etc/systemd/system/tomcat.service JAVA_HOME中删除“ /jre ”解决了这个问题

Answer 3

找到 JAVA_Home ($env | grep JAVA_HOME)

须藤vi /etc/systemd/system/tomcat.service

Environment="JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64"

Answer 4

您可能在 tomcat 服务中添加了以下行：-

Environment="JAVA_HOME=/usr/lib/jvm/default-java"

您必须将其替换为您正在使用的实际 Java 版本。 在终端中键入以下命令：-

须藤更新-java-alternatives -l

输出

将上述命令的输出替换为 JAVA_HOME 变量路径，您的变量应如下所示：-

Environment="JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64"

现在重新加载守护程序并重新启动您的服务它应该可以正常工作

须藤 systemctl 守护进程重新加载

须藤 systemctl 启动 tomcat

检查服务状态

须藤 systemctl 状态 tomcat

Answer 5

我在 Ubuntu 上现有的Tomcat安装中遇到了同样的问题：

当我尝试通过制作现有文件的副本然后使用以下命令创建新文件来清除日志文件时，我开始遇到此问题：

sudo cp /opt/tomcat/logs/catalina.out catalina_copy.out
sudo rm -rf /opt/tomcat/logs/catalina.out
sudo touch /opt/tomcat/logs/catalina.out

当我尝试使用sudo systemctl restart tomcat启动tomcat时，我遇到了这个错误：

$ sudo systemctl start tomcat
Job for tomcat.service failed because the control process exited with error code. See "systemctl status tomcat.service" and "journalctl -xe" for details.

这是我修复它的方法：

问题是，在我创建并复制文件后，文件的所有权从tomcat更改为root ，我通过在/opt/tomcat/logs目录中运行以下命令来确认：

ls -lh

我所要做的就是通过运行以下命令将所有权从root更改为tomcat ：

sudo chown -R tomcat:tomcat catalina.out
sudo chown -R tomcat:tomcat catalina_copy.out

这次当我尝试使用sudo systemctl restart tomcat服务器时，它运行良好。

就这样。

我希望这有帮助

Answer 6

只需从 'tomcat.service' 文件中的 JAVA_HOME 中删除 '/jre'，服务就会启动。

Answer 7

我今天遇到了类似的问题，唯一的区别是该服务直到昨晚都运行良好，然后突然停止了..

原因是 Java 版本已自动更新，从而更改了 java 路径。

我所要做的就是更新 tomcat.service 文件中的新 Java 路径，重新启动守护程序和中提琴..！！