Job for tomcat.service failed because the control process exited with error code. See “systemctl sta
tags: Mistake java tomcat linux
CentOS 7 Configures Tomcat Self-Start Times The following error
Job for tomcat.service failed because the control process exited with error code. See "systemctl status tomcat.service" and "journalctl -xe" for details.
usesystemctl status tomcat.serviceCommand view error message
The error message is lacking the Java_Home or JRE_HOME environment variable, even if the / etc / profile is configured, Tomcat is not loaded, then find a file called setclasspath.sh in Tomcat's BIN.
The approximate process launched by Tomcat is startup.sh-> catalina.sh-> setclasspath.sh, while the role of setClassPath.sh is to load environment variables.
It can be seen that the first sentence executed by the script is to load the environment variable, so Java_Home is needed to be in front.
Re-execute Systemctl Start Tomcat can run successfully
Intelligent Recommendation
Job for postfix.service failed because the control process exited with error code. See "systemctl st
Centos7 failed to start postfix Try to solve Modify the settings of /etc/postfix/main.cf...
Job for jenkins.service failed because the control process exited with error code. See "systemctl st
systemctl status jenkins.service I see the reason because: Solution: Solution: 1> View current Java environment variables echo $JAVA_HOME 2> Copy the Java environment variable address, edit the ...
Job for network.service failed because the control process exited with error code. See “systemctl st
Virtual machine networking issues Restart the network card and report the following error: Job for network.service failed because the control process exited with error code. See “systemctl statu...
Job for jenkins.service failed because the control process exited with error code. See “systemctl st
Record a Jenkins startup error Jenkins has been booting up all the time, and the boot access failed today, so check it out and try to restart: Reported the above error, prompt to use the command:syste...
Job for redis.service failed because the control process exited with error code. See “systemctl stat
Note this: could not create server tcp listenging socket 127.0.0.1:6379: bind: address already in use [root@ebs-65684 bin]# ./redis-cli 127.0.0.1:6379> shutdown not connected> exit Jul 27 22:37:...
More Recommendation
Solve Job for Network.Service Failed Because The Control Process Exited with error code. See "Systemctl
Report error Solve the problem This way is OK....
Solve Job for Docker.service Failed Because The Control Process Exited with error code. See "Systemctl S
Installing the installation of Docker Docker daemon in Ubuntu16.04 can't afford it, and report the following error: Job for docker.service failed because the control process exited with error code. Se...
Job for smbd.service failed because the control process exited with error code. See “systemctl statu
error One step one-step detection error At this time, I found that the problem of the configuration file is not set. Re-modify the configuration file At this time, I found it. then Enough...
Job for nginx.service failed because the control process exited with error code. See “systemctl ....
Nginx abnormal Job for nginx.service failed because the control process exited with error code. See “systemctl status nginx.service” and “journalctl -xe” for details. Nginx Nor...
Job for httpd.service failed because the control process exited with error code. See “systemctl stat
illustrate At the same time, HTTPD and Nginx are installed, the default port is 80, conflict error. Wrong solve View the port is occupied 1. Modify one of the default ports Nginx Httpd 2, uninstall on...