Thread

I have an existing installation that all of the sudden stopped running.

davidlarsenforcongress.com

I can’t access the index file or any other url associated with an entry, but I CAN still access the system file. Can also still access files via FTP.

I have other EE sites, static sites, and WP sites running on the same server with no issues.

Any ideas?

Running EE 1.6.8

Plugins active:

Magpie RSS Parser (v.1.4) 
Share This! (v.1.1.0) 
Character Limiter (v.1.0)
Randomizer (v.1.0) 
Word Limiter (v.1.0) 
Twitter Timeline (v.1.2) 
XML Encode (v.1.2)
XML Encoding plugin.

Hi Mike,

The site appears to stall without loading anything; usually indicative of a server issue. Have you contacted your host regarding this? Any errors in the server logs?

Hi Mike,

Please contact your host and ask them what is causing the server 500 error (which is what I’m seeing). They should be able to see what is happening in the site logs. Is this the same error on all site pages?

Cheers

Greg

Gentlemen,

Here is the response from my host:

Taking a look at the directory structure for davidlarsenforcongress.com/html, there is a file labeled index.php.swp. These swap files are generally created, when edits are made to file through a server side text editor and then not saved (correctly or otherwise).

You may need to review the contents or configuration of this particular index file or its construction within your Expression Engine panel. I can confirm that there are no issues regarding Cluster.03 or your (gs) Grid-Service at this moment, that would only affect this one site.

Here is the swap file:
http://davidlarsenforcongress.com/swapfile.zip

I tried removing the file from the root of the directory but no luck.

Do you think the issue might be a corrupt file in the system somewhere? I read in an unrelated post about re-uploading the core files.

Again, there’s no real issue with accessing the file structure of the server, i.e. my image and css files etc. The admin panel works fine and all the existing content appears to be there and editable.

I’ve also re-uploaded the index.php file just for kicks. Didn’t change anything.

Currently waiting on Mediatemple’s response to the 500 error code question.

I tried removing the file from the root of the directory but no luck.

When you say no luck, what do you mean? Were you able to delete the file?

Sorry Sue, I just meant it didn’t fix the problem. I was able to delete the swap file and backed it up just in case. Here is the response from my host regarding the 500 error:

Looking at your error_log, I see the following message:

[Sun Sep 19 20:55:55 2010] [error] [client 207.46.195.223] Premature end of script headers: ph[Sun Sep 19 20:56:13 2010] [error] [client 72.10.62.12] Premature end of script headers: php5

Mike,

have you got a htaccess in play? Can you rename it temporarily to see if that bypasses the error?
I am seeing a number of issues when I googled that error along with mediatemple

John,

Contents of my htacess file:

ErrorDocument 404 /index.php/404/

AddHandler php5-script .php

I changed the name as suggested; now the site just serves up a blank page, and also the admin panel serves up blank. When I put the php5 handler back in everything goes back to the way it was; admin panel works fine, backend content is retrieved from the database, but no website.

The webserver serves static pages fine.

Should I try updating to 1.6.9? (currently 1.6.8)

If none of this has rung a bell with 4 moderators, perhaps I need to consider a fresh install. Maybe I am just getting antsy, but my client’s site has been down since Saturday night… at this point I’m ready to just back up my templates and reinstall. Can anyone point me to some documentation on this?

I wanted to try updating from 1.6.8 - 1.6.9 but I can’t seem to find any documentation on upgrading from 1.x to 1.x

I am unable to access the site at all. That said, this clear is a server issue of some sort, especially if it stopped running all of a sudden.

There’s some info here on upgrading.

Ingmar, the site’s CP is accesible. System file is /dlfceesys.

My other EE site run with no issues on the same server. Thanks you for the upgrade link, I’ll try that next.

If nothing else, a file refresh won’t hurt. Let us know when you get a chance to work on things. We’ll be here.

Well, after updating to 1.6.9 I found out that it was the pi.twitter_timline plug in that was screwing me over. For some reason it just broke the site instead of degrading gracefully. Apparently, twitter changed it’s authentication policies this September. I have since updated the plugin which is now at least throwing an error… sooooo on to a different post then!

Thank you so much for all of your help and patience! =)