Skip to main content

The service “httpd” appears to be down.

Adilson Parizi

Hello everyone, could anyone help me sort out this problem?

My server is displaying the following error: ‘The service “httpd” appears to be down’. It is a dedicated server running LiteSpeed. What changes do I actually need to make to ensure the server works properly? It is an official licence purchased directly from cPanel.

cPanel error message:

Server    
Primary IP Address    

Service Name    httpd

Service Status    failed ⛔
Notification    

The service “httpd” appears to be down.

Service Check Method    
The system failed to connect to this service’s TCP/IP port.

Reason    Service check failed to complete

Timeout whilst trying to retrieve data from the service: Died

Number of Restart Attempts    2

Startup Log    4 Oct 00:26:20 server.myserver.com systemd[1]: Starting Apache web server managed by cPanel EasyApache...
4 Oct 00:26:20 server.myserver.com systemd[1]: httpd.service: Cannot open PID file /run/apache2/httpd.pid (yet?) after start: No such file or directory

4 Oct 00:26:20 server.myserver.com systemd[1]: Apache web server managed by cPanel EasyApache has started.

Log Messages    [Sun 4 Oct 00:26:20.907032 2026] [mpm_event:notice] [pid 31463:tid 31463] AH00489: Apache/2.4.69 (cPanel) OpenSSL/1.1.1k mod_bwlimited/1.4 configured -- resuming normal operations

[Sun 4 Oct 00:26:20.890743 2026] [security2:notice] [pid 31459:tid 31459] ModSecurity for Apache/2.9.14 (http://www.modsecurity.org/) configured.

Memory Information
Used    12.45 GB
Available    49.31 GB
Installed    61.76 GB

Comments

2 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  Nothing in that output is helpful to identify an issue as that is just the notification telling you there was an event.  You would want to examine server logs around the time of the event in order to get more detail.  Specifically, checking /etc/apache2/logs/error_log would show anything related to the web service on the machine.

    If your license is purchased directly through us you're always welcome to create a ticket and then our team can check the system for you directly.

    0
  • Zoltan Egri | 1b.hu

    Hi,

    Since your server is using LiteSpeed, I would first verify which web server is actually running before changing any service-monitoring configuration.

    The Apache log entries you posted indicate that Apache did start, and the missing PID file warning alone does not prove that the service failed permanently.

    I would check:

    systemctl status lshttpd httpd --no-pager
    journalctl -u lshttpd -u httpd --no-pager -n 100
    ss -ltnp

    Also check WHM > Plugins > LiteSpeed Web Server to confirm whether LiteSpeed is currently the active web server.

    The important distinction is whether the web service is genuinely unavailable or whether cPanel's service monitor is reporting a failure while LiteSpeed continues serving requests.

    If LiteSpeed is active and ports 80/443 are responding, I would investigate the monitoring failure before attempting to restart or switch web servers.

    Could you confirm whether websites were actually inaccessible when the notification appeared?

    Zoltan Egri | 1b.hu

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post