Hi folks,

We've been experiencing problems with publishing entries and comments for awhile now, and now it's escalated to the point where it's completely broken, and large core dump files are showing up in the install directory. MT support suggests this might have something to do with a Perl module conflict, but since there are hundreds on our host, it's tough to track down.

Has anybody else experienced this problem, or does anybody have a suggestion as to where to look? The server error logs only show the generic "premature end of script headers," which is no help. This is a pretty high profile blog, and currently dead in the water. Any help would be appreciated.

Let me know if I can post any more info that might help. Thanks.

Here's a bit of info:

* Movable Type version: 4.1

* MT home directory: ./
* Operating system: linux
* Perl version: 5.8.8
* Perl include path:
plugins/WXRImporter/lib
plugins/spamlookup/lib
plugins/WidgetManager/lib
plugins/commchallenge/lib
plugins/Textile/lib
plugins/StyleCatcher/lib
plugins/MultiBlog/lib
plugins/feeds-app-lite/lib
addons/Commercial.pack/lib
extlib
extlib
lib
/usr/lib/perl5/5.8.8/i686-linux
/usr/lib/perl5/5.8.8
/usr/lib/perl5/site_perl/5.8.8/i686-linux
/usr/lib/perl5/site_perl/5.8.8
/usr/lib/perl5/site_perl/5.8.5
/usr/lib/perl5/site_perl/5.8.4
/usr/lib/perl5/site_perl/5.8.3
/usr/lib/perl5/site_perl/5.8.2
/usr/lib/perl5/site_perl/5.8.1
/usr/lib/perl5/site_perl/5.8.0
/usr/lib/perl5/site_perl

404 means that the page can not be found.

ImageMagic can cause problems if misconfigured.

Thanks for your reply. I was aware that a 404 is a file not found. It's throwing that because the script is crashing/timing out.

Can you tell me how I could tell if ImageMagick is misconfigured?

Thanks.

A script timing out / crashing should return an error 500.

My host always sorted out any IM problems I had. Does mt-check.cgi show IM installed?

What makes you say that? A script dying would most likely produce a 500 error; a timeout would say it was a timeout. A 404 implies the script doesn't even exist to be causing the error in the first place.

I say that partly because I've had that experience in the past, with both MT and other platforms. The script is clearly there. I was also informed by MT support that a severely crashing mt.cgi could return a 404.

ImageMagick is installed. Mt.check.cgi shows:

"Your server has Image::Magick installed (version 6.3.7)."