The service runs under Tomcat, and sometimes it encounters a situation where Tomcat can't get up. There are several situations that you often encounter:
1, the Tomcat service port is preempted, causing the Tomcat process to not come;
2, check the service log directory permissions, it is possible that the directory permissions are not correct, resulting in the Tomcat process does not come;
For example: The service code is printed with a service log directory of/testdeploy/test/, and the service is started with normal user test. At this time if the/testdeploy/test/permission is root:root or something else, as long as it is not the test user has permission to write, the Tomcat process will not get up;
3, hostname was modified, hostname command execution results and/etc/hostname results inconsistent, resulting in Tomcat does not come;
4. Server.xml,<context> label exception in Tomcat under Conf directory
1) may not be configured
2) <context> label position is not lil bit, position to be placed in the
5, <context> label specified webapp The following application is deleted
6, the service inputs parameter configuration is wrong
Why does the Tomcat process not come up with "original summary"?