CentOS 7中Tomcat 7服务处于Inactive(Dead)状态排障求助

Hey there, let's break down how to figure out why your Tomcat 7 service is showing up as inactive after a seemingly successful YUM install. Here are the practical steps I'd recommend checking:

• Check systemd's detailed service logs
  The catalina.out might not capture all startup issues, especially those tied to systemd itself. Run this command to get the full context of what's happening when the service tries to launch:

  sudo journalctl -u tomcat.service -xe
  

  Keep an eye out for lines marked ERROR or Failed—these will almost always point to the root cause, like missing dependencies or misconfigured paths.

• Verify JAVA_HOME configuration
  Tomcat depends entirely on a properly set JAVA_HOME environment variable. For YUM-installed Tomcat on CentOS 7, this is usually defined in /etc/sysconfig/tomcat. Open the file and confirm JAVA_HOME points to a valid JDK installation (Tomcat 7 requires JDK 7 or newer):

  sudo nano /etc/sysconfig/tomcat
  

  You can also check the system-wide Java version with:

  java -version
  

  If Java isn't installed or is the wrong version, install the required package:

  sudo yum install java-1.7.0-openjdk-devel
  

• Check file and directory permissions
  Tomcat runs as the tomcat user, so it needs proper access to its installation and log directories. Verify permissions for key paths:

  ls -ld /var/lib/tomcat /var/log/tomcat
  

  If the owner/group isn't tomcat:tomcat, fix it with:

  sudo chown -R tomcat:tomcat /var/lib/tomcat /var/log/tomcat
  

• Start Tomcat manually in foreground mode
  Bypass systemd temporarily to see real-time startup output, which can reveal issues that don't make it to log files. Run:

  sudo /usr/share/tomcat/bin/catalina.sh run
  

  Watch the output as it tries to start—any errors will show up immediately, like port conflicts or broken config files.

• Check for port conflicts
  Tomcat defaults to using port 8080. If another service is using this port, Tomcat won't start. Check with:

  sudo ss -tulpn | grep 8080
  

  If you see another process bound to 8080, either stop that service or edit /etc/tomcat/server.xml to change Tomcat's HTTP port to something else (like 8081).

• Validate Tomcat configuration files
  A typo in server.xml, web.xml, or context.xml can prevent Tomcat from starting. Use the built-in config validation tool:

  sudo /usr/share/tomcat/bin/configtest.sh
  

  This will flag any syntax errors or invalid settings in your configuration files.

Once you've worked through these steps, try starting the service again with sudo systemctl start tomcat and check the status with sudo systemctl status tomcat.

内容的提问来源于stack exchange，提问作者TheProvost