Home / server / Questions / 618618
Accepted
duenni
Asked: 2014-08-07 23:28:03 +0800 CST

mod_fcgid: can't apply process slot after software upgrade

  • 772

I'm on a shared hosting plan with a Wiki and a Bulletin Board installation. After upgrading the Wiki to the latest release my users are not able to upload files with the integrated "media manager" anymore. Server logs show:

mod_fcgid: can't apply process slot for
/var/www/cgi-bin/cgi_wrapper/cgi_wrapper, referer:
http://www.myurl.com/path/to/wiki/

I contacted the hosting company and the supporter answered that he fooled around with 

FcgidMaxProcessesPerClass
FcgidMaxProcesses

to no avail. He also changed some suexec rights, no success. mod_security is not installed.

HTTP File uploads are broken for the entire host, users from the bulletin board are not able to upload files, too (503 Service Temporarily Unavailable when trying to upload something). Everything else is working fine. Page loading speed is ok, users can edit, create and delete sites etc. Uploading files per FTP is working too. There are <30 active users on this sites so I don't think I'm out of processes or something. I am not able to change the apache settings directly. Any ideas what I can tell the support to look into?

EDIT: The bulletin board has a shoutbox which adds some load to the site. I cleared all messages and reduced the amount of kept messages. I also deactivated all wiki plugins. Still no success.

apache-2.2

2 Answers

  1. Best Answer

    Problem is solved. Hosting company changed PHP Version. At first PHP was at Version 5.2.x and as the problem arised was bumped to 5.4.x. Now, PHP was changed to 5.3.3 for testing purposes and everything works. I still don't know what caused this, both installations should run fine on PHP >5.2. So maybe there were some PHP settings that differed but sadly I can not figure this out anymore.

    • 2

  2. Solution: Ditch your webhost.

    In terms of what to ask support to look into: a refund.

    Your webhost is the only one who can diagnose and fix the server. It is also part of what you pay them to do. You don't have root, and as it is a shared hosting environment, you shouldn't have root.

    The server could be oversold, misconfigured, or more likely, both. For the server's administrators (your webhost) there is a valid technical question with a valid technical solution. For you, their customer, it is purely a customer service issue that demands an appropriate customer service resolution.

    • 1