The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Apache Error: Failed to receive status information from Apache. Unable to connect to local httpd...

Discussion in 'EasyApache' started by johnnylavah, Dec 15, 2014.

  1. johnnylavah

    johnnylavah Member

    Joined:
    Dec 4, 2014
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Reseller Owner
    Hello!

    I receive the following error when attempting to view the 'Apache Status' within WHM: "Apache server status for server.x.com. Failed to receive status information from Apache. Unable to connect to local httpd server."

    I re-built Apache using the default build and I am still receiving the error.

    When viewing the error_log (/usr/local/apache/logs/error_log) I see the following messages...
    Code:
    [notice] caught SIGTERM, shutting down
[warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[notice] ModSecurity for Apache/2.8.0 (http://www.modsecurity.org/) configured.
[notice] ModSecurity: APR compiled version="1.5.1"; loaded version="1.5.1"
[notice] ModSecurity: PCRE compiled version="8.36 "; loaded version="8.36 2014-09-26"
[notice] ModSecurity: LUA compiled version="Lua 5.1"
[notice] ModSecurity: LIBXML compiled version="2.9.2"
[notice] Status engine is currently disabled, enable it by set SecStatusEngine to On.
[warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[notice] Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 configured -- resuming normal operations
[error] [client 58.186.133.52] request failed: error reading the headers
[error] [client 58.186.133.52] request failed: error reading the headers
[error] [client 58.186.133.52] request failed: error reading the headers
[error] server reached MaxClients setting, consider raising the MaxClients setting
[warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[notice] ModSecurity for Apache/2.8.0 (http://www.modsecurity.org/) configured.
[notice] ModSecurity: APR compiled version="1.5.1"; loaded version="1.5.1"
[notice] ModSecurity: PCRE compiled version="8.36 "; loaded version="8.36 2014-09-26"
[notice] ModSecurity: LUA compiled version="Lua 5.1"
[notice] ModSecurity: LIBXML compiled version="2.9.2"
[notice] Status engine is currently disabled, enable it by set SecStatusEngine to On.
[warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[warn] pid file /usr/local/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[notice] Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 configured -- resuming normal operations
[error] server reached MaxClients setting, consider raising the MaxClients setting
[notice] caught SIGTERM, shutting down
[warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[notice] ModSecurity for Apache/2.8.0 (http://www.modsecurity.org/) configured.
[notice] ModSecurity: APR compiled version="1.5.1"; loaded version="1.5.1"
[notice] ModSecurity: PCRE compiled version="8.36 "; loaded version="8.36 2014-09-26"
[notice] ModSecurity: LUA compiled version="Lua 5.1"
[notice] ModSecurity: LIBXML compiled version="2.9.2"
[notice] Status engine is currently disabled, enable it by set SecStatusEngine to On.
[warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[notice] Apache/2.2.29 (Unix) mod_ssl/2.2.29 OpenSSL/1.0.1e-fips mod_bwlimited/1.4 configured -- resuming normal operations
[error] server reached MaxClients setting, consider raising the MaxClients setting
    Any thoughts or advice? Thank you for any insight!
     
    #1 johnnylavah, Dec 15, 2014
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    34,894
    Likes Received:
    1,063
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Re: Apache Error: Failed to receive status information from Apache. Unable to connect to local httpd

    Hello :)

    The following error message appears in the log output you provided:

    You may find this post helpful:

    Apache Failing

    Thank you.
     
    #2 cPanelMichael, Dec 16, 2014
  3. johnnylavah

    johnnylavah Member

    Joined:
    Dec 4, 2014
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Reseller Owner
    Re: Apache Error: Failed to receive status information from Apache. Unable to connect to local httpd

    Thank you! I installed (D)DoS Deflate and I have been in good shape the past few days. Appreciate your help!
     
    #3 johnnylavah, Dec 21, 2014
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    34,894
    Likes Received:
    1,063
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Re: Apache Error: Failed to receive status information from Apache. Unable to connect to local httpd

    I am happy to see you were able to address the issue. Thank you for updating us with the outcome.
     
    #4 cPanelMichael, Dec 22, 2014
(You must log in or sign up to post here.)
Loading...
Similar Threads - Apache Error Failed
  1. Reado

    SOLVED [case EA-6287][May 17 2017] EasyApache 4 UI fails to load with UTF-8 error - The subprocess error

    Reado, May 17, 2017, in forum: EasyApache
    Replies:
    29
    Views:
    1,707
    BluegrassNet
    May 18, 2017 at 10:21 AM
  2. cmonego

    Error when migrating EasyApache3 to EasyApache4

    cmonego, Apr 13, 2017, in forum: EasyApache
    Replies:
    4
    Views:
    188
    cmonego
    Apr 13, 2017
  3. steven5493

    received 500 error after updating to apache 2.4 with easyapache

    steven5493, Apr 9, 2017, in forum: EasyApache
    Replies:
    1
    Views:
    121
    cPanelMichael
    Apr 10, 2017
  4. Nirjonadda

    SOLVED Apache Forbidden Error

    Nirjonadda, Mar 23, 2017, in forum: EasyApache
    Replies:
    8
    Views:
    313
    Nirjonadda
    Mar 27, 2017
  5. mikefromnz

    Domain used only for email showing SSL error in Apache Log

    mikefromnz, Mar 11, 2017, in forum: Security
    Replies:
    1
    Views:
    169
    cPanelMichael
    Mar 12, 2017

Share This Page