SUSE Enterprise Linux下Apache Tomcat8开机自启异常求助

Hey there, let's figure out why your Tomcat 8 isn't accessible after setting it to start on boot—this is a common gotcha, so let's break it down step by step.

First, Verify the Basics #

Before diving into fixes, let's confirm what's actually happening:

• Check if Tomcat is running: Run ps aux | grep java or ps aux | grep tomcat to see if the process exists.
• Check port listening: Use ss -tulpn | grep 8080 to confirm Tomcat is bound to the correct port (look for 0.0.0.0:8080 or :::8080 to ensure remote access is allowed).
• Check local access: Run curl localhost:8080 directly on the server. If this works but remote browsers don't, it's likely a firewall issue.

Common Causes & Fixes #

1. Missing Environment Variables in Auto-Start Context #

When you run startup.sh manually, you're using your user's shell environment (which has JAVA_HOME, CATALINA_HOME, etc.). But system auto-start scripts run with a minimal environment—so these variables might be missing.

Fix:
Add explicit environment variables to your auto-start script:

#!/bin/bash
# Replace paths with your actual JDK and Tomcat locations
export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk
export CATALINA_HOME=/opt/tomcat8
export PATH=$PATH:$JAVA_HOME/bin:$CATALINA_HOME/bin

# Navigate to Tomcat's bin directory first (avoids relative path issues)
cd $CATALINA_HOME/bin
./startup.sh

2. Incorrect Working Directory in Auto-Start Script #

If your script runs from a different directory than Tomcat's bin folder, relative paths in Tomcat's config can break.

Fix:
Always cd to Tomcat's bin directory before executing startup.sh—like the example above.

3. Systemd Service Configuration Issues (If Using Systemd) #

If you set up a systemd service for Tomcat, incorrect settings can make systemd think Tomcat started successfully even if it failed.

Fix:
Create/update /etc/systemd/system/tomcat8.service with these settings:

[Unit]
Description=Apache Tomcat 8
After=network.target  # Ensures Tomcat starts after network is ready

[Service]
Type=forking  # Matches Tomcat's forking startup behavior
User=tomcat   # Use a dedicated tomcat user (create if needed)
Group=tomcat
Environment="JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk"
Environment="CATALINA_HOME=/opt/tomcat8"
Environment="CATALINA_BASE=/opt/tomcat8"
Environment="CATALINA_PID=/opt/tomcat8/temp/tomcat.pid"
ExecStart=/opt/tomcat8/bin/startup.sh
ExecStop=/opt/tomcat8/bin/shutdown.sh
Restart=on-failure

[Install]
WantedBy=multi-user.target

Then run these commands to apply:

# Create tomcat user if you haven't already
useradd -r -m -U -d /opt/tomcat8 -s /sbin/nologin tomcat
chown -R tomcat:tomcat /opt/tomcat8

# Reload systemd and enable the service
systemctl daemon-reload
systemctl enable tomcat8
systemctl start tomcat8

4. Firewall Blocking Port 8080 #

Manual testing might have worked because you temporarily opened the port, but the firewall resets on boot.

Fix:
Open port 8080 permanently:

• For firewalld:

  firewall-cmd --add-port=8080/tcp --permanent
  firewall-cmd --reload
  

• For iptables:

  iptables -A INPUT -p tcp --dport 8080 -j ACCEPT
  service iptables save
  service iptables restart
  

5. Permission Issues #

If the auto-start user (e.g., root or tomcat) doesn't have read/write access to Tomcat's logs, temp, or webapps directories, Tomcat might fail to initialize silently.

Fix:
Ensure the tomcat user owns all Tomcat files:

chown -R tomcat:tomcat /opt/tomcat8
chmod -R 755 /opt/tomcat8

Check Tomcat Logs for Clues #

If none of the above works, dig into Tomcat's logs at $CATALINA_HOME/logs/catalina.out—look for errors like:

• Address already in use (port conflict)
• Permission denied (directory access issues)
• Could not find Java (missing JAVA_HOME)

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