• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue mod_fcgid: ap_pass_brigade failed in handle_request_ipc function

Erwan

Regular Pleskian
Plesk Onyx / Centos
=============
Hi,
Since lot of months, we have this error in the log file:
....
[Fri May 18 08:33:19.286162 2018] [fcgid:warn] [pid 3378:tid 140252660348672] (32)Broken pipe: [client x.x.x.x:38982] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: https://mydomain.fr/file/
....

There was no problem getting back up here.
But now, with some big uploads (ex 100MB file), some users but not all do not arrive at the end and get a page "inaccessible site".

We have find this article: Websites are slow and a warning appears in logs: mod_fcgid: ap_pass_brigade failed

But when we change "FcgidMaxRequestsPerProcess" (=10000, and finaly 0), there is no change. We have always the problem in the log file.

Do you have another idea?
Thanks.

Erwan
 
This is a timeout issue, not a number of processes issue. The connection is timing out before an output can be delivered by the web server. There can be many reasons why this occurs. Regarding your comment about large files, maybe using a different upload method, for example an asynchronously working uploader, can solve it.
 
Back
Top