Comments for internal error

internal error

2008-12-04T23:52:34Z

I host the site with Dreamhost. Everything is OK for almost two years, until last month. I met so many internal errors when I login, publish or rebuild. Sometimes I just click the link in the back.

The error.log has something like below:

[Tue Dec 02 14:50:54 2008] [error] [client 64.180.100.153] Premature end of script headers: mt.cgi, referer: http://www.yinfor.com/mtcgi/mt.cgi [Tue Dec 02 14:50:54 2008] [error] [client 64.180.100.153] script ‘/home/davidyin/yinfor.com/internal_error.html’ not found or unable to stat, referer: http://www.yinfor.com/mtcgi/mt.cgi

Any one has similar problems?

Comment from Mike T on 2008-12-04

2008-12-05T02:09:25Z

Does this happen randomly, or does it happen mainly on certain things?

Comment from DavidYin on 2008-12-04

2008-12-05T05:56:07Z

It happens very often during last 20 days.
I can not publish any post now.

Comment from Mike T on 2008-12-05

2008-12-05T14:48:25Z

And you didn't recently install any new plugins or updates that would affect the code?

Comment from DavidYin on 2008-12-05

2008-12-05T17:19:36Z

No new plugins installed.
Based on the hosting support's answer, it is because of the cpu / memory usage is over the limit. Then it is killed.
How to reduce the memory or cpu cost?
I use fastcgi already.

Comment from Mike T on 2008-12-05

2008-12-05T17:35:12Z

Well... you can make heavy use of template module caching to reduce the amount of time that a rebuild takes, but this is more of an issue with your host being cheap. I had similar problems when I used Dreamhost. They compete with others by overselling their resources.

Comment from Jay Allen on 2008-12-10

2008-12-11T01:08:31Z

DavidYin, you should also look into using PubilshingQueue for the templates that are most problematic. Unlike web-based requests, PublishingQueue processes (which are executed by cronjob) are usually left alone by hosting providers.

You may also want to invest some time into profiling your templates to figure out which ones are problematic. Pages like Google Sitemaps and any published using the Paginate plugin are common causes for timeouts (or process reaping by overinvasive hosting providers) during rebuilds.