Hello, and happy new year!
We have a conference coming up next month and the website has a dev site (which works fine) and a live site (which doesn't work at all). These two sites are sub-servers in the same home directory and have different codebases, databases and Apache virtual hosts.
dev site: http://dev.la2011.designfordrupal.com
live site: http://la2011.designfordrupal.com/index.php
Well, the live site is really http://la2011.designfordrupal.com but that points to a temporary redirect until this problem is fixed.
I couldn't figure out why the dev site works and the live one doesn't, so searched through every page I could find on this "Premature end of script headers" problem with mod_fcgid and I've checked things and tested them and checked again. I even deleted the virtual servers and recreated them. Same problem.
Requests to http://la2011.designfordrupal.com/index.php result in internal server errors (error 500). This is from /home/ddcla/domains/dev.la2011.designfordrupal.com/logs/error_log:
[Sat Jan 01 02:34:57 2011] [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi server error.
[Sat Jan 01 02:34:57 2011] [error] [client 76.94.217.50] Premature end of script headers: index.php
Is there any help you can provide? I've been at this for a few hours and I'm at my wits' end. Thanks!
Comments
Submitted by christefano on Sat, 01/01/2011 - 02:59 Pro Licensee Comment #1
You can log into this server with:
ssh -p 31415 virtualmin@musclebeach.ladrupal.org
The password is
qcf0om5rk0
and this user is in sudoers.Submitted by christefano on Sat, 01/01/2011 - 03:00 Pro Licensee Comment #2
You can also log in with the same username and password at https://ladrupal.org:10000/
Submitted by andreychek on Sat, 01/01/2011 - 11:10 Comment #3
Hmm... well, the problem you're seeing isn't actually related to fcgid, that message you're seeing is just a notice that a problem is occurring, and the script is exiting out before mod_fcgid expected it to. Just to be certain -- I tried switching your server to use CGI, and the 500 Errors continued.
Next, I created a test PHP script named "test.php" on your live server. It actually runs just fine, and the PHP inside is executed correctly.
And then finally, I temporarily moved my test.php over to index.php, and the test script continued to work correctly.
With all that in mind -- it unfortunately looks like a Drupal issue rather than a server configuration issue.
One question would be, how did you go about setting up Drupal your live server? Could any paths have inadvertently been copied over from the dev site?
Submitted by christefano on Sat, 01/01/2011 - 15:25 Pro Licensee Comment #4
The code running in /home/ddcla/domains/la2011.designfordrupal.com/ddcla/public is a git clone and is identical to what's running in /home/ddcla/domains/dev.la2011.designfordrupal.com/ddcla/public
Well, except for the settings.php in public/sites/default, which is pointing to a different database. I'll point it to another database to see if the problem is in the ddcla2011_live database.
Submitted by christefano on Sat, 01/01/2011 - 17:49 Pro Licensee Comment #5
Ah, so what happened was I did:
sed s/dev.la2011.designfordrupal.com/la2011.designfordrupal.com/g ddcla_dev.sql > ddcla_live.sql
... when I should have done:
sed 's/dev.la2011.designfordrupal.com/la2011.designfordrupal.com/g' ddcla_dev.sql > ddcla_live.sql
I'd left out the single quotes. :/
Sorry for the false alarm!