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 not responding while server is online

Discussion in 'EasyApache' started by lambov, Jan 31, 2017.

  1. lambov

    lambov Member

    Joined:
    Oct 9, 2016
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Earth
    cPanel Access Level:
    Root Administrator
    i often get my apache/httpd stop responding and get back online after a while..its about 2 or 3 minutes and sometimes it takes about 30 minutes
    or i must restart apache to get back online soon..

    when apache not responding, i don't see http process on HTOP/TOP command and cpu usage very low and i don't see error log when apache not responding

    i use default mpm event from EA4, my server is 8 core 30GB RAM (web hosting production)
    my apache global configuration:

    Start Servers 5
    Minimum Spare Servers 5
    Maximum Spare Servers 10
    Server Limit 500
    Max Request Workers 500
    Max Connections Per Child 10000


    is the problem because of my apache configuration? what is the best apache configuration based on my server spec?
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    37,064
    Likes Received:
    1,288
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    Are you able to review /usr/local/apache/logs/error_log and let us know the last output you see before Apache stops responding or before you notice the restart attempt?

    Thank you.
     
  3. lambov

    lambov Member

    Joined:
    Oct 9, 2016
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Earth
    cPanel Access Level:
    Root Administrator
    this is my
    error log before apache stops responding and after restarting

    Code:
    [Tue Jan 31 16:31:11.262617 2017] [core:error] [pid 841326:tid 140032891315968] [client 120.188.87.215:37097] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:12.418051 2017] [core:error] [pid 842797:tid 140032673273600] [client 202.67.40.238:37085] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:12.418087 2017] [core:error] [pid 842797:tid 140032673273600] [client 202.67.40.238:37085] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:22.695389 2017] [core:error] [pid 843095:tid 140032589354752] [client 114.124.26.25:37120] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:22.695436 2017] [core:error] [pid 843095:tid 140032589354752] [client 114.124.26.25:37120] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:24.628418 2017] [core:error] [pid 842607:tid 140032912295680] [client 180.245.157.255:37124] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:24.628478 2017] [core:error] [pid 842607:tid 140032912295680] [client 180.245.157.255:37124] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:24.701815 2017] [core:error] [pid 842607:tid 140032683763456] [client 202.67.40.238:37144] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:24.701855 2017] [core:error] [pid 842607:tid 140032683763456] [client 202.67.40.238:37144] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    [Tue Jan 31 16:31:27.086900 2017] [core:error] [pid 843375:tid 140032880826112] [client 180.245.157.255:37151] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
    -------------------------------------------
    NO ERROR LOG WHEN APACHE NOT RESPONDING
    -------------------------------------------
    [Tue Jan 31 16:35:57.523409 2017] [:error] [pid 843921:tid 140032778172160] mod_hostinglimits:Error on LVE enter: LVE(528) HANDLER(application/x-httpd-ea-php56) HOSTNAME(xxxxxx.com) URL(/index.php) TID(843929) errno $
    [Tue Jan 31 16:35:58.614885 2017] [:error] [pid 845761:tid 140032725722880] mod_hostinglimits:Error on LVE enter: LVE(528) HANDLER(application/x-httpd-ea-php56) HOSTNAME(xxxxxx.com) URL(/index.php) TID(845774) errno $
    [Tue Jan 31 16:36:03.609354 2017] [:error] [pid 842797:tid 140032610334464] mod_hostinglimits:Error on LVE enter: LVE(528) HANDLER(application/x-httpd-ea-php56) HOSTNAME(xxxxxxcom) URL(/index.php) TID(842821) errno $
    [Tue Jan 31 16:36:08.331351 2017] [:error] [pid 845761:tid 140032694253312] mod_hostinglimits:Error on LVE enter: LVE(528) HANDLER(application/x-httpd-ea-php56) HOSTNAME(xxxxxx.com) URL(/index.php) TID(845777) errno $
    [Tue Jan 31 16:37:57.676552 2017] [:notice] [pid 806437:tid 140033130747872] [host my.hostname.com] mod_lsapi:  Selfstarter 806437 stopped
    [Tue Jan 31 16:38:00.097628 2017] [core:warn] [pid 102394:tid 140033130747872] AH00045: child process 810317 still did not exit, sending a SIGTERM
    [Tue Jan 31 16:38:00.097812 2017] [core:warn] [pid 102394:tid 140033130747872] AH00045: child process 837727 still did not exit, sending a SIGTERM
    [Tue Jan 31 16:38:00.097857 2017] [core:warn] [pid 102394:tid 140033130747872] AH00045: child process 811623 still did not exit, sending a SIGTERM
    
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    37,064
    Likes Received:
    1,288
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Feel free to open a support ticket using the link in my signature if the issue persists and you'd like us to take a closer look. You can post the ticket number here and we will update this thread with the outcome.

    Thank you.
     
  5. lambov

    lambov Member

    Joined:
    Oct 9, 2016
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Earth
    cPanel Access Level:
    Root Administrator
    Support Request ID is: 8201635
     
  6. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    37,064
    Likes Received:
    1,288
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    To update, our Technical Analysts determined the issue likely stems from a large number of lsphp processes being killed by the out of memory (OOM) killer on the server (the websites appear down). More information on OOM is available at:

    Understanding the Linux oom-killer's logs

    Thank you.
     
Loading...

Share This Page