Apache keeps going down on a Plesk server: server reached MaxRequestWorkers setting

Follow

Comments

9 comments

  • Avatar
    Kingsley Felix

    I am tired of plesk, i inscreased this and it is still happening

    0
    Comment actions Permalink
  • Avatar
    Dan Neuhaus

    Still having the same issue on two servers despite raising MaxRequestWorkers to 1000

    1
    Comment actions Permalink
  • Avatar
    Bulat Tsydenov

    @Dan, Am I right that even after changing 'MaxRequestWorkers' to 1000 and restarting apache you still see 'server reached MaxRequestWorkers setting' errors in apache logs? Additionally, you may check this article which contains troubleshooting steps.

    0
    Comment actions Permalink
  • Avatar
    Luis Zubeldia

    for mpm_event where i can change MaxRequestWorkers value?

    0
    Comment actions Permalink
  • Avatar
    Alexandr Tumanov

    @Luis, the path is almost the same:

     

    Debian/Ubuntu /etc/apache2/mods-enabled/mpm_event.conf 

    CentOS the same file but <IfModule mpm_event_module> section.

    0
    Comment actions Permalink
  • Avatar
    Ryan Yzquierdo (Edited )

    This issue continues to be a problem, despite having these settings already (which I just verified following the instructions above). Everything has been working fine on my server for past few months since I fixed some problems after a previous Plesk update. Lo and behold, Plesk autoinstaller updated last night around 3am and I have been dealing with this problem since I got up. Frustrating that Plesk updates keep causing problems.

    0
    Comment actions Permalink
  • Avatar
    Anzhelika Khapaknysh

    @Ryan Yzquierdo,

    If you still experience any issues after the update, don't hesitate to contact our Support Team so they can thoroughly check the issue.

    0
    Comment actions Permalink
  • Avatar
    Björn

    I got the same error.

    To ward off url attacks, I wrote in php in case of evil Url

     

    sleep(99999);

    exit;

    I dropped sleep and changed it into

    exit;

    That was my problem. Now I get no maxRequestErro error any more.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Björn

    Thank you for sharing your user experience.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request