• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved apache going down with event

agaitan

Basic Pleskian
Server operating system version
Almalinux 8
Plesk version and microupdate number
18.0.54
[Tue Jul 18 09:03:08.206899 2023] [mpm_event:error] [pid 80515:tid 140403841104192] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting

im getting this

my conf
01-cgi.conf



# This configuration file loads a CGI module appropriate to the MPM
# which has been configured in 00-mpm.conf. mod_cgid should be used
# with a threaded MPM; mod_cgi with the prefork MPM.

<IfModule mpm_worker_module>
LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_event_module>
LoadModule cgid_module modules/mod_cgid.so
MaxRequestWorkers 600
ServerLimit 26
</IfModule>
<IfModule mpm_prefork_module>
LoadModule cgi_module modules/mod_cgi.so
</IfModule>
 
[mpm_event:error] [pid 69713:tid 139944054524224] AH00484: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
 
i already done that, even tried this


<IfModule mpm_worker_module>
LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_event_module>
LoadModule cgid_module modules/mod_cgid.so
MaxRequestWorkers 800
ServerLimit 800
</IfModule>
<IfModule mpm_prefork_module>
LoadModule cgi_module modules/mod_cgi.so
MaxRequestWorkers 800
ServerLimit 800
</IfModule>

but still same error
] [mpm_prefork:error] [pid 105954] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
and im using MPM mode as PREFORK for apache, maybe a website is doing that? how i can know that, as i have almost 1000 domains in server and i never had that issue before
 
[root@panel httpd]# httpd -V | grep MPM
Server MPM: prefork

and conf

# This configuration file loads a CGI module appropriate to the MPM
# which has been configured in 00-mpm.conf. mod_cgid should be used
# with a threaded MPM; mod_cgi with the prefork MPM.

<IfModule mpm_worker_module>
LoadModule cgid_module modules/mod_cgid.so
</IfModule>
<IfModule mpm_event_module>
LoadModule cgid_module modules/mod_cgid.so
MaxRequestWorkers 400
ServerLimit 16
</IfModule>
<IfModule mpm_prefork_module>
LoadModule cgi_module modules/mod_cgi.so
MaxRequestWorkers 400
ServerLimit 400
</IfModule>
 
I assume you restarted apache after modifying the config file?

If so, I am not really sure why the modified values don't solve the error. But here are some toughs that might help you:

1) It's unlikely, but I just to be sure you could search trough the conf directory to see if the MaxRequestWorkers settings isn't present in another another file also. Run grep -rnw '/etc/httpd/conf.modules.d/' -e 'MaxRequestWorkers' to search to all files in the /etc/httpd/conf.modules.d/ directory.

2) If that doesn't yield any result then you might have to play around with the MaxRequestWorkers value. Trying higher values, but also try lower values. See if that helps.
 
I assume you restarted apache after modifying the config file?

If so, I am not really sure why the modified values don't solve the error. But here are some toughs that might help you:

1) It's unlikely, but I just to be sure you could search trough the conf directory to see if the MaxRequestWorkers settings isn't present in another another file also. Run grep -rnw '/etc/httpd/conf.modules.d/' -e 'MaxRequestWorkers' to search to all files in the /etc/httpd/conf.modules.d/ directory.

2) If that doesn't yield any result then you might have to play around with the MaxRequestWorkers value. Trying higher values, but also try lower values. See if that helps.
what i did was restarted all vmware esxi server and for now it works, also i had to disable php 7.4 and upgrade some websites
 
Back
Top