The 1and1 control has a CGI output tool to check for server error 500. Using that, here's what came out:

Result:
+ CGI Check succeeded
Status: 200
Pragma: no-cache
Content-Type: text/html; charset=utf-8

Sign in | Movable Type Open Source

Username

Password

Remember me?

Forgot your password?



type="submit"
accesskey="s"
title="Sign In (s)"
class="primary-button"
>Sign In

STDOUT OK STDERR OK

Client
Engine gecko
Version 1.9
Platform win
System winxp
Color 32
Width 1280
Height 1024
Flash 10
All
Request-Complete 4458ms
Server
Server-Complete 2701ms (61%)
HTML
HTML-Complete 1757ms (39%)
HTML-Details
HTML-Head 1405ms (32%)
Page-Head 1ms (0%)
Page-Body 41ms (1%)
Post-Exec 116ms (3%)

http://www.virtualbeggar.us/pics/error.txt

Could it be because I use html or Javascript in my Widgets?

In the mean time, have you considered experimenting with an upgrade to MT 4.21?

I can easily say I have the same issue and that is totally new for me as well.

As far as the server logs it only indicate that the execution of rebuild, deleting entries or comments, creating new entries or adding comments seemed to loop itself somehow or other.

It could be because my webhost changed all the servers from FreeBsD to Linux servers with Apache 2.

I can publish after many days of intense headaches by removing the code for category pagination. But that itself creates issues as I need the pagination.

I'd recommend following Richard Benson's suggestion, but also going to your error logs immediately after you get a 500 error and posting the results here so we can help you.

The site publishes on its own. Sometimes a day after a post; sometimes 3 days. Basically, I create a post and it appears after 1-3 days. When I try to publish manually is when I get the error 500.

I ran the mt-check.cgi and the error check was successful.

Thank you for contacting us.

I received a case regarding 500 errors when performing tasks at http://mrshappyhousewife.com. The application is
exceeding the resource limits that we impose for your shared hosting package. I've even tried upping the resource quota of your package and that did not make a difference. Here are the limits for your reference:

Programming Limits:
CPU : 6 seconds @ 100%
Memory : 10240KB (10MB)
Numerical Processes : 12

You may find that your application/scripts will work sometimes. These are times when there are enough free resources available (more than the normal) at a
particular time to accommodate your scripts beyond those limits. The solution would be to get a (dedicated) managed server, if it is an option for you, wherein you would have all the resources of the server at your disposal with no quotas imposed.

Well, I spoken to 1and1 and I've asked them to identify which script is causing the high CPU usage. From what I read, earlier versions of MType had high CPU usage issues. Specially the mt-comments script. She does get a lot of junk messages that build up. In the dashboard, I changed the number of comments displayed from 25 to 200 and now I cant get back to it(I get the server 500 when I try to display the comments).

The Mambo site was taken offline using its backend (it still exists just offline).

The new Mtype upgrade is a security fix so it doesn't affect performance.

Are there any performance scripts or plugins that can help determine where the high usage is coming from?

1) Footer

2) HTML Head

3) Most of your sidebar widgets that don't display page-specific information, such as any archive listing widgets, your creative commons widget and stuff like that.

I'm pretty sure that it's included with 4.2, but you should make sure that you have TypePad Anti-Spam installed on your server once you upgrade. It's very good at catching comment spam before it can cause too much of a performance issue by preventing it from triggering a rebuild.

My blog stats:

-1,600 entries with about 5,500 some comments

-30-50 pages

-Several additional index templates ranging from a sitemap, to index templates for folders managed by MT.

Rebuild on 4.1: 30-35 minutes
Rebuild on 4.2: 7-10 minutes on average.

1) Log in to 1and1's server for your account via SSH (all good hosts provide this option, even Dreamhost...)

2) run wget, passing it the full URL to MT open source's latest zip file or gzipped archive.

3) With zip, just run "`unzip MT-4.2*zip`" for the gz file, run "`tar -zxvf MT-4.2*gz`"

4) cd into that MT-4.2 directory.

5) `cp -Rv * /path/to/movable/type` (for me it's `cp -Rv * /home/mike/public_html/mt/`)

Works like a charm. Faster and more reliable than FTP any day of the week!

Already dumped the sql database and downloaded a copy of the original website.

The whole site is statically built except I think one template. I've cached a few modules, but the error 500 persists.

We're running MTOS 4.261, and otherwise everything is working fine. Can you (anyone?) suggest ways to reduce the load during publishing? I've not figured out how to set a cron job on 1and1, so Publish Queue may not be an option (I'm pretty ignorant on setting up cron jobs).

Thanks!