Subscribe to
NSLog(); Header Image

MovableType 3.2 500 Error Solved

Brad Choate (yes, there's only one) spent some time with my "Error 500s with MovableType 3.2" issue yesterday and believes he's found the source of the problem: a low Apache Timeout value. Default used to be 1200, but that was recently lowered to 300. The timeout value Interland has set on my server? 5.

A simple perl script was used to test this:

#!/usr/bin/perl -w
use strict;
my $start = localtime;
my $time = int($ENV{QUERY_STRING}) || 1;
sleep $time;
my $end = localtime;
print "Content-Type: text/plain\n\n";
print "Done!\nDuration: $time\nStart: $start\nEnd: $end";

I have a ticket in with Interland to raise the value to 100. The Sand Trap is hosted on a shared account, so I don't believe that there's any way I can over-ride this setting myself. I must be hopeful that Interland has some common sense. If not, well, I'll have to move the site, I suppose.

4 Responses to "MovableType 3.2 500 Error Solved"

  1. Is that an obscure error? Were you unable to run things at all? Hardly like make sure permissions are set.

  2. does not work. works.

    The conf file ("/etc/httpd/conf/vhosts") lists a timeout of 5.

  3. I'm having the same error 500 problem with a MT install, also on Interland. Were you able to resolve this with them?

    I've done everything the Knowledge Base suggests without results. I ran your script on the server and got this:


    Duration: 1

    Start: Tue Oct 11 18:18:06 2005

    End: Tue Oct 11 18:18:07 2005

    Thanks for blogging about this and thanks for any advice you may have!

  4. doh!
    tried it with ?60, ?100, and so on... it seems to be set at 300 on this Interland server