Symptoms
-
Error inÂ
/var/www/vhosts/example.com/logs/error_log:mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: http://www.example.com/index.php
-
FcgidMaxRequestsPerProcess parameter is defined in web configuration. The below command returns non-empty output:On RedHat/CentOS/CloudLinux:
# grep FcgidMaxRequestsPerProcess /etc/httpd/conf.d/fcgid.conf /var/www/vhosts/system/example.com/conf/vhost.conf /var/www/vhosts/system/example.com/conf/httpd.conf
On Ubuntu/Debian:
# grep FcgidMaxRequestsPerProcess /etc/apache2/mods-enabled/fcgid.conf /var/www/vhosts/system/example.com/conf/vhost.conf /var/www/vhosts/system/example.com/conf/httpd.conf
Optional symptoms:
-
Websites on Plesk server are slow or not available:
500 Internal server error
- Cannot send mail via PHP script
Cause
“FcgidMaxRequestsPerProcess” limit is reached in “mod_fcgid” Apache module configuration.
Resolution
Solution for all domains on the server
-
OpenÂ
/etc/httpd/conf.d/fcgid.conf(on RedHat/CentOS/CloudLinux) orÂ/etc/apache2/mods-enabled/fcgid.conf(on Ubuntu/Debian)Â using “vi”; -
Increase value of
FcgidMaxRequestsPerProcessparameter:<IfModule mod_fcgid.c>
FcgidMaxRequestsPerProcess 500
</IfModule> -
Reload Apache configuration:
On RedHat/CentOS/CloudLinux:
# service httpd reload
On Ubuntu/Debian:
# service apache2 reload
-
If it does not help, try to tune other mod_fcgid parameters, for example set
FcgidOutputBufferSizeequal 0.
Solution for one particular domain
-
Go to Domains > example.com > Apache & nginx Settings > Additional Apache directives;
-
Set up or increase the FcgidMaxRequestsPerProcess parameter value in Additional directives for HTTP and Additional directives for HTTPS fields depending on website’s preferable protocol (or in both):
<IfModule mod_fcgid.c>
FcgidMaxRequestsPerProcess 500
</IfModule>
