Dear HelpDesk,

We own a MovableType license for already several months.

Unfortunately we have a big problem with our comments.

Several visitors reported that when they are trying to publish a comment after about 20 seconds the browser reports a “500 Internal Server Error� message.

Interesting is that even if the visitor is receiving this error message the comment will appear in the Web site.

What can we do to avoid letting the error message appear to those visitors that are so kind to comment our posts?

Reference:
http://www.masternewmedia.org/2003/09/29/f...omic_change.htm


I look forward your prompt and kind feedback,

With my Best Regards,
Mihai Alexandru Bocsaru

I just tested it. and can confirm this as true, but i'm not sure what the problem could be.

Do you have any plugins that check comments before publishing?

Dear Faf,

In the plugins folder I have the following plugins:

- Compare v1.01
- DirifyPlus ver (1.5)
- entry.pl, v 1.4
- FirstNWords v1.1
- MTFastInclude v1.1
- MTIncludePlus v1.1
- otherblog v1.4
- Related entries v2.0
- MT-Textile v1.1

Not all the above-mentioned plugins are called from the RobinGood’s Sharewood Tidings Blog.

Only inside “entry.pl� I can find a reference for comments.




In case the problem is not related to the plugins we use, we look forward more opinions on how to solve this unpleasant situation.

Warm Regards,
Mihai Bocsaru

Dear HelpDesk,

I have sent a request also to my host and they say that the problem is related ONLY to MovableType.

Can somebody from MovableType clarify this issue?

Thanks,
Mihai

I have a similar problem:

When posting entries from the control panel and making comments in a pop-up I receive the following: Internal Server Error. When investigating the logs it tells me that there is a “Premature end of script headers� in the mt-comments.cgi file.

Despite this error message, all entries and comments are posted successfully – visitors however, get the see the error message when making a comment, and so, repeat the process leading to duplicate posts.

The website, www.htzine.net is in the root directory with MT residing in my cgi-bin. I have a number of other weblogs, over 50, in their own sub-directories that are unaffected.

I have replaced all the cgi files using the latest download and set permissions at 0755, but the problem still exists.

The problem started about five weeks ago, after the site had been running ok for more than six months with over 800 comments.

Any help to resolve this issue would be appreaciated.

Techie Stuff:

-Apache Virtual Server running on Linux
-Perl version: 5.6.1
-MT is running under cgiwrap or suexec
- MT is set up in cgi-bin though the db file is in a private area.

Dear Friends,

Checking the Error Logs the problem is:

“www.masternewmedia.org [Mon Oct 6 08:31:37 2003] [error] [client xx.xx.xxx.xxx] Premature end of script headers: … mt-comments.cgi�

What can I do to avoid the error message?

Thank you,
Mihai Bocsaru

Dear Support,

While performing my yesterday's testing from 4 (four) trials 2 (two) worked perfectly. The other two shown me the "Internal Server Error" message.

I have again written to our Host and this time they told us that our script is violating their resource policies.

- no more than 8 MB memory space;
- no more than 30 CPU seconds to complete.

They are recommending us to refine the script.

Is there something we can do in this respect?

I have seen that this problem is not only mine and maybe we can all benefit from the solution.


Thank you,
Mihai Bocsaru

I've encountered a similar problem, and I believe I know what's happening. My experience is not with mt-comments.cgi, but rather with mt-xmlrpc.cgi -- I'm posting this in the hopes that the two issues are related.

I am using MovableType with the Twisted Web server, and although mt-comments.cgi works well, I am unable to make any posts to mt-xmlrpc.cgi with any blogging tools.

Below is the error listed in my web server log:


...and so on. This looks normal, and one might wonder why this is happening. So I whipped out Python, read the file, and noticed the exact format of the whitespace:


Aha! This violates HTTP standards, as far as I can tell. The appropriate way to separate headers from response is with either \n\n, \r\r, or \r\n\r\n. The above is none of the three; it's a mix, one which some web servers ignore, but some (including mine) do not.

Unfortunately, as far as I can tell, this doesn't look like it's a MovableType error -- it looks like it's either part of SOAP::Lite, HTTP::Headers, or HTTP::Response. I'm not a very good Perl hacker, so I can't tell what needs to be fixed, but it looks to me like this standards-incompliance is the problem.

Can anyone else who's having this problem open your log files with Python or a hex editor and find out whether your MT scripts are doing the same thing?