Tag Info

Hot answers tagged

6

PHP-FPM is a patch for PHP to provide some advanced process management features which are useful when used in its FastCGI variant. On a side note, PHP 5.4 will probably include PHP-FPM out of the box (according to Antony Dovgal). Since mod_fcgid doesn't support externally spawned FastCGI servers, you need to use mod_fastcgi or mod_proxy_fcgi. Google found ...


5

Solution: FcgidMaxRequestLen -->This is causing the problem. Before updating to the newest version, it was default set to 1gb. Now it is 128kb. Add the following to the file /etc/apache2/conf.d/fcgid.conf : FcgidMaxRequestLen 1073741824 This wil give you a limit of 1gb. Next, restart your apache.


4

You're using ubuntu. Therefore recompile is pretty simple. Add source repository to your /etc/apt/sources.list . For 12.04 run echo "deb-src http://de.archive.ubuntu.com/ubuntu/ precise main"|sudo tee -a /etc/apt/sources.list change de.archive.ubuntu.com to whatever country you're in. After that update your repository. apt-get update Change dir and ...


3

Or you can apt-get install apache2-suexec-custom after install go to cd /etc/apache2/suexec edit the file vi www-data You can see the first 2 lines, make the changes: replace /var/www with /home esc :wq after, restart apache /etc/init.d/apache2 restart


3

These are comparing apples and oranges and bananas. First, FastCGI is a protocol for communicating between a persistent application (or application server) and a webserver. A FastCGI-capable application runs on its own and receives requests from the webserver, then returns the responses to the webserver to give to the client. FastCGI was invented because ...


3

<Directory /srv/www/hostname/public> Order allow,deny Allow from all </Directory> That doesn't include /srv/www/hostname/fcgid-bin/; assuming there's no Allow applying to it elsewhere in your config, this is the problem. You'll need to Allow access to this location.


3

Is this common behaviour? It's your specific settings. Solution: Options -MultiViews Apache Manual says (you will have to scroll down a bit): The effect of MultiViews is as follows: if the server receives a request for /some/dir/foo, if /some/dir has MultiViews enabled, and /some/dir/foo does not exist, then the server reads the directory ...


2

I doubt you'll find this neatly written up from a reliable source. I think the answer to your headline question is to take a look at suPHP. Unfortunately the documentation is rather sparse. Out of the box suPHP is compiled in paranoid mode which means that you have to set the user and group that you want PHP to run as with the suPHP_UserGroup directive on ...


2

Yes this is expected behaviour. It would appear you had 5 copies of ab running at the same time. This resulted in your 150 PHP processes to handle the 30 requests for each of your 5 ab processes. Apache works best when all its threads can run in memory. There will be a load at which the threads will need to be swapped to disk. Response time will ...


2

These errors mean, that the scripts were running longer than 31 seconds and thus they were terminated, as your fcgid.conf says so. The standard timeout is 40 seconds btw. You can easily check this behaviour by writing a test.php: <?php sleep(32); ?> This should give you an error 500 and put this error in your logs. You have two possibilities to ...


2

mysqldump by default will write lock the database while it runs so the data isn't altered during the backup, which can cause corruption. Drupal writes to the database on every request, so requests will hang while mysqldump is running, and eventually timeout. If you're using InnoDB (or can convert to it), then you can use Percona XtraBackup to do hot ...


2

SUExec is requiring that the directory (/var/www/html/) and the binary (/var/www/cgi-bin/php5/php-fcgi-starter) be owned by the same user/group. Looks like 10001/2523 owns the dir, and root owns php-fcgi-starter. Fix that, or turn off SUExec.


2

Trac is written in Python and supports running under mod_wsgi (per an item in the FAQ), so I'd drop several of those moving parts and switch to the fantastic mod_wsgi, which supports specifying a user for a script to run as. I use this functionality for another project and it works well. Checking for the official mod_wsgi docs, to point you at how this is ...


2

I'm using the IUS RPMs from Rackspace, and suexec came compiled and configured by default. Here are the pertinent parts of my mod_fcgid config: LoadModule fcgid_module modules/mod_fcgid.so AddHandler fcgid-script fcg fcgi fpl php DefaultInitEnv PHPRC "/etc/" FCGIWrapper /usr/bin/php-cgi .php I suggest removing the "ScriptAliasMatch" Directive and ...


2

We could see your problem as 'not really a problem', as when timeout occurs the php script ends. If it was not ending after the timeout you would get in bigger problems :-). Then to reduce the hangs time you would at least be able to play with the FcgidBusyTimeout & FcgidBusyScanInterval parameters, ...


2

'IPCCommTimeout' may be too large. Set the normal limit(60-180) 'IdleTimeout' set to 3600 or higher 'DefaultMaxClassProcessCount' set to (number or CPU core) 'ProcessLifeTime' set to 7200 'MaxProcessCount' set large 'DefaultMaxClassProcessCount'(2*'DefaultMaxClassProcessCount')


2

This basically means that all the php processes are busy processing requests, and no free php processes are available to handle new incoming requests. This causes the 500 error. Usually this means that the php code that you are running is slow, swamping the php processes. Try enabling your mysql slow log to see if slow queries are the culprit, try php ...


2

As I have seen this issue with the cpanel server only, so I am assuming that you are using the same. For the fix, this is what you need to do: # mv /opt/xml2 /opt/xml2.bak Then re execute EasyApache from WHM > EasyApache (Apache Update) or via shell using the command /scripts/easyapache –force This should fix the problem. This blog explains the same.


2

This is the purpose of mod_info. On the server-info page, you will see all the possible configuration options and if they are customized. If there is no custom setting, then it is the compile-time default, which does seem to be 1000 as confirmed by the documentation and source code (line 48). Note: don't use the Location /server-info or create a link to ...


2

Given how many PHP related tasks are in progress on my server, I generally use a different php.ini file for Apache/mod_fcgid... FcgidWrapper "/usr/bin/php-cgi -c /etc/httpd/conf/php.ini" .php This way, all confusion as to what ini file has been parsed is removed.


1

First of all, you're overkilling it. You don't need suphp + php-fpm since they basically do the same thing. If you want multi-user multi-vhost enviroment you should be using the following stack: apache+mod_fastcgi+php-fpm php-fpm allows you to define pools that can run under different user with totally different php settings. For that configuration you ...


1

Those parameters are configurated in php.ini, usually located in /etc/php5/php.ini but may also be more specific like : /etc/php5/apache2/php.ini or maybe /etc/php5/fastsgi/php.ini To be absolutly accurate you can create a "phpinfo file", it will show you the path of actually used config file : Create a info.php file on your server and ...


1

When you're using mod_fcgid apache doesn't know anything about php anymore. It simply sends it off. So those configurations can't be in any apache configs. You'll need to add those settings to php.ini. http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html http://www.howtoforge.com/how-to-set-up-apache2-with-mod_fcgid-and-php5-on-centos-6.2


1

Checking out varnish and apache2 showed that they both returned 200 OK codes. The issue was actually load balancer on our hosting providers network intercepting responses.


1

yes that directive is correct, but you have to add that directive to the .htaccess in any directory, or in alternative you can add it in your httpd.conf file. Ensure that the module is loaded with a2enmod command


1

Got it! The problem was the safe_mode option. safe_mode was enabled and caused an error in the header, because safe_mode is not supported in PHP 5.4.


1

Split your error logs per VirtualHost and make the clients deal with their own web site errors.


1

Why don't you just go with DSO as a PHP Handler + Mod_Ruid2 + APC? It's a great configuration (also for high traffic sites) and it can be installed using EasyApache in WHM.


1

I have had my problem, the error is mainly because the timeout is exceeded mod_fastcgi, put the solution here which to me has solution: Modify this file /etc/httpd/conf.d/fcgid.conf and change, FcgidIOTimeout to FcgidIOTimeout 500 And restart apache: /usr/sbin/apachectl restart Source: ...


1

Modify this file /etc/httpd/conf.d/fcgid.conf and change, FcgidIOTimeout to FcgidIOTimeout 90 It works for me. Tkx JD



Only top voted, non community-wiki answers of a minimum length are eligible