I set up my MT several days ago and it was working fine. I made a small change to my index.html template and now I get error 500's. Premature end of script errors. I've seen reports of this happening when you rebuild, but not when you save. I can't save ANY templates. I can create entries and rebuild the entire site, I just can't save templates. Can anyone offer any advice on what to check? I'ts 2:30am and I've been looking at this problem for over an hour. I'm beat.

EDIT: Ok, it seems as if the template file is getting saved, because when I click back after the 500 error and do a rebuild, the saved change shows up on the web site, so the problem seems to be with something AFTER the file is saved.

Mike

I get this same error! It's quite annoying and even though changes are saved, I'd like to not get that 500 error.

Does anyone know why this is happening?

Who's your hosting provider? Mine's Vizaweb.

Mike

Mine is a different host (though who knows these days with reselling?).

I have even gotten the 500 error when trying to log into the interface, but it worked on second try. Very odd indeed!

Are you guys on cpanel ?

I had the same problem and think it's caused by a cpanel daily update,
as I saw several topics saying about this problem and was posted about 1st of july,

Any Idea ?

I have started getting the same error yesterday. All of a sudden, saving templates or any other html file (entry) the second time after they have been created.

It seems to be a file limitation problem. To prove this I have created a simple test template and included my css file and some simple lines of code.

Here is what this template looks like:



Don't forget the css file is quite lengthy. When I try to save this template I get a 500 ISE error and a core dump in the mt directory. The error log indicates a

[Fri Jul 1 13:07:15 2005] [error] [client 66.14.203.76] Premature end of script headers: /home/utata21/public_html/mt/mt.cgi

By the way, watch those coredumps as they add 10Mo files to your server at each save.

But back to the test template, as it is right now, it throws the 500 error after saving. If I remove one sigle line of text, or a carriage return, the file saves just fine. Also, if I replace the css file with one containing less lines, it also works.

It definitely looks like a limitation on the number of HTML lines and it's quite annoying. All entries that are too lengthy will throw a 500 error, but they actually save.

I don't know who I should talk to, my host admin said this would be the best place to start after they have been scratching their heads for an entire day.

Thanks, I'd really appreciate any input regarding this issue.
Thanks,
Irina

Ugh, forgot that HTML is converted. See source for test template, I am too lazy to convert it to "visible" html. Or maybe there is an easier way I don't know of. Nevermind (OT).

Yeah, I'm getting this too. I'm with surpass hosting and they've been trying to help me out... they wound up showing me this thread to see if anyone figures out what this is about.

I only seem to be getting this when I save certain changes such as a making a weblog dynamic or static, making a new weblog, etc. I also get it on weblogs that are dynamic when I make a post that's longer than a few sentences or try to change the category.

This literally came out of nowhere. I had not changed a single thing with the installation.

Same problem. Huge core dumps. 500 server errors. No response from Cpanel, as usual.

I'm on Surpass too and am having the same issues. I tried to update a post and it saved (meaning it successfully update MySQL) but it can't rebuild the page. It's getting a 500 error because of the same "Premature end of script headers" problem.

Anybody got a clue?

Surpass basically told me that this doesn't seem to be an issue with my server and that someone else was having this issue as well. They mention the same thing talked about in here, how the new page is saved and not rebuilt and how there is a core dump.

It's just a wait and see thing as far as this goes, I guess. Hopefully someone involved with the project or whatever might have an idea.

Anymore info on this. I just started noticing the errors today and everything was fine as of yesterday afternoon.

I have been fighting with this one too. My provider A Small Orange is checking to see if a new or updated perl module from CPAN may be causing the problem. Said they would keep me informed.

Hi, I'm from A Small Orange. The only CPAN module that's been updated recently was Time::HiRes on the 29th. That may be the one that's causing issues, as it's used by MovableType in lib/MT/Builder.pm. Unfortunately, my Perl skills are rather lacking, so if someone else could step in and let us all know how this may have broken, that would be great. It appears that cPanel installed version 1.71 and the previous version was 1.69.

Edit: 1.72 is the latest version in cPanel. You may want to tell your hosts to use this command to fix the issue (if they hvae cPanel):

/scripts/perlinstaller Time::HiRes

No guarantees if this fixes the issue or not, but given that they released this version in short order from the last, that may say they found a problem.

Edit 2: Well, that didn't seem to do the trick, but I'm tracing though the code on this one...

timdorr, tried that and it didn't work, I'm trying to update everything now but nothing there seems to be helping.

Good luck finding the solution, I have a dozen tinkerers on my server who keep in touch with each other so I'm getting tons of IMs asking me when I'm going to fix it.

Right now I've got it down to this line in lib/MT/Entry.pm:

$entry->SUPER::save(@_) or return;

Unfortunately, my Perl is pretty bad, so I don't know exactly where that goes. But when it fails upon re-saving an entry, it is failing at that point. I can get an error if I force one before that, but it 500's if I try the error after.

Edit: Ok, figured that out. It goes up to ObjectDriver's save, which invokes DBI in this case. I've found it's failing on the update subroutine for the UPDATE sql call. I suppose I should reinstall DBI::mysql? I'll see what I can do...

Hi,

The problem was with DBI perl module. It has to be at 1.47 in order to work.

Thank you

I'm at version 1.48. Did you downgrade?

Reinstalled Hires as well as DBI::mysql.

No dice.

Yes we had to downgrade all servers.

How did you downgrade? What;s the command? I'm on SSH with a Cpanel setup.

Here is what I did:


After this, do I need to reboot Apache or something?

No luck here with either 1.47 or 1.48...

Try downgrading DBD::mysql to version 2.9006.

I think that did the trick! Thanks

The link to that version is http://www.cpan.org/modules/by-module/DBD/...l-2.9006.tar.gz for those that need it.

Thanks to everyone for their hard work figuring this one out!

Umm... this is great and all for you techies, but the rest of us who don't run our own servers and can't do the command line bit are still stuck with the problem. And I have the feeling that my web host won't be able to downgrade my perl and sql just for my account.

Is SixApart even aware of this problem? Are they working on a patch? For how long will I have a dysfunctional blog? Is there something that even a layman can do to fix this?

Any help would be much appreciated.

Thanks to LivingDot

I hope sixapart take a look at this thread and help to solve this issue as these modules and thing update everyday and may cause this problem again in future,

Same problem here. Started yesterday afternoon. Most annonying. Using cPanel, hosted by Hosting Matters., which, I believe, mainly hosts MT blogs. They're working on it.

When they come up with something, I'll let ya'll know.

Same with me. And I don't have access to shell to do thoes stuff. I hope SixApart will make a path soon.

Can someone please post exact steps to downgrade DBI and DBD installations?

Now I'm getting precondition failures: "The precondition on the request for the URL /mt/mt.cgi evaluated to false," which prevents me from even previewing an entry, much less saving or publishing it.

I found some instructions here:
http://sniptools.com/vault/tipstricks/mt-c...d-downgrade.htm

Hi,

Yes SixApart is aware of it. Please rest assured they'll not leave the problem unattended

Great, I'm glad to hear that. As of right now I can't even really do anything properly with my site lol.

BTW, for me at least, the DBI downgrade didn't appear to be neccessary, just the DBD downgrade. To be honest, I'd like a newer version installed instead, but we can't all get what we want...

I'm with small orange as well. Unfortunately, in an attempt to fix this myself, I wiped my MT install and set everything up again. Now I'm getting the same core dump when attempting to re-import all my old entries. Everything else seems to be working as it should except this.

I've tried my full 3.8Mbs entry backup, then halving that, then halving that.. and then finally taking it down to only 10k worth of entries. Same exact failure each time.

Any ideas?

Yeah, my host isn't able to downgrade the problem modules, because of it possibly being a security risk. Anyway, I'll be watching here for a patch or the like from SA.

I just wanted to chime in and say that I started getting these errors this morning. I'm on TotalChoiceHosting.

I installed MT earlier this week and had no problems making any changes until today. At first it was just my stylesheet that was giving me the 500 error; now it's all of the templates and occasionally the main login page (mt.cgi).

Like the person who started this thread, all of these templates are saved despite the server error, because when I rebuild I see the modifications I've made on my site (www.foecus.com/plog).

Watching with interest - am probably the only person running MT on my host's server and there's no way they'll downgrade anything just for me!

Hi Folks,
Many kudos to Tim Dorr at A Small Orange who is my host provider. He worked tirelessly resolving this problem and I have passed the resolution on to MT Support.

The solution was to downgrade DBD::mysql to 2.9006.

So contact your providers and let them know. Meanwhile, I assume that the fine folks at MT will be working to see that the problem doesn't arise with the more recent versions of DBD.

I highly recommend ASO as a host for movable type. My experience with them has been excellent , and Tim's efforts show they know their stuff and will do all within their power to resolve problems.

Surpass Hosting has also rolled back that for me as well. They've been a lot of help the past few days (they originally directed me to this thread even).

Now everything works perfectly. Here's hoping Six Apart gets around this issue soon.

I noticed one big thing: DBD::mysql 3.0000 was released on Jun 30th. That means it was pushed to cPanel servers on July 1st. It would seem that version is causing the problems, I think.

I'm also with Surpass Hosting, and this same error started occurring for me as of at least this morning (July 3). I'm crossing my fingers that someone can fix this issue.

It looks like cPanel is rolling back the changes. I'm going to have to set up a cronjob to automatically downgrade nightly, otherwise it's going to keep doing this every night.

FWIW, I've run into the 500 errors with MT-Blacklist (this is an older version on MT 2.64) and tracked it down to the PluginData module. It's saving binary data into a TEXT column, which aparently no longer works.

I'm not sure how 6A is going to address this (I'd think that changing that column to a BLOB would have made more sense to begin with), but I've worked around this problem by replacing the data function in PluginData.pm with the one described by David Raynes. I'd only reccomend doing that "if you know what you're doing" and only in dire situations (like you host won't downgrade the DBD::mysql module and you cannot wait for an official fix).

I get the same Premature End of Script Headers and have downgraded to 2.9006 as per the instructions here but I still face a 500 error. Any other ideas?

It appears there's a 3.0000_0 DBD::mysql release on the horizon: http://search.cpan.org/src/CAPTTOFU/DBD-my...mysql-3.0000_0/

And so everyone knows, there's no need to downgrade all the way back to 2.9006, you can use 2.9008 and get the bugfixes in that release too: http://search.cpan.org/CPAN/authors/id/R/R...l-2.9008.tar.gz

Only 3.0000 seems to break, so far.

Surpass Hosting downgraded my DBD::mysql to 2.9006 as well. No luck--I still get the errors. Although they are not as consistent as they were before, they are still there. Yargh.

Is there any word from the Six Apart people on how soon they might fix this?

I'm getting the problems again with Surpass too. They said they set my CPanel updates to manual, but it seems that the update went through again anyway... I mailed them again, but I'm not in a rush over it anymore.

I don't think the problem is on Six Apart's end, it's possible that the DBD::mysql 3.0 is buggy. We will see