Originally Posted by stefanm
That looks ok. Have you tried disabling suexec for the ispconfig interface?
At the risk of sounding completely ignorant, how do I do this for just one site?
Originally Posted by Ben
From what I read when googling around for that issue, is this maybe
- a timeout error, that the script takes too long to generate data to send
- the request limit is reached for fcgi processes
Can you reproduce the error anyhow?
Does raising the loglevel in apache help to get any further details?
These are the results of raising the log level to debug:
[Thu Dec 01 13:27:11 2011] [debug] fcgid_proc_unix.c(354): mod_fcgid: call /var/www/ispconfig/index.php with wrapper /var/www/php-fcgi-scripts/ispconfig/.php-fcgi-starter
[Thu Dec 01 13:27:11 2011] [info] mod_fcgid: server server.gracesites.com:/var/www/ispconfig/index.php(11806) started
[Thu Dec 01 13:27:11 2011] [warn] [client 220.127.116.11] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server
[Thu Dec 01 13:27:11 2011] [error] [client 18.104.22.168] Premature end of script headers: index.php
[Thu Dec 01 13:27:17 2011] [info] mod_fcgid: process /var/www/php-fcgi-scripts/ispconfig/.php-fcgi-starter(11806) exit(communication error), terminated by calling exit(), return code: 0
Also, here's the contents of the php-fcgi-starter wrapper file that's referenced:
exec /usr/bin/php -d magic_quotes_gpc=off -d session.save_path=/usr/local/ispconfig/server/temp