A pretty common topic on here is Movable Type, a very cool weblogging tool. You can find Movable Type here:
Anyhow, I’ve been going through the support forum over there and have seen some messages by DreamHost users having problems with using MT with our services. Apparently during the update process, some users (particularly those with lots of content to update) are having problems with the script dying on them in the middle of writing their weblog entries.
Looking into it further, it sounds like it’s our procwatch utility that’s killing it. What procwatch does is look for any user processes that have been running for more than a few minutes. If these processes are causing the server to incur significant load, it kills them. This is done so that a single user process cannot impact other users on the server.
Possible fixes would include either incrementally handling the updates over several processes, or being more selective on what gets updated every time. Some people have said that recent Movable Type versions seem to fix the problem, but I’m a curious enough to ask the MT-using people here…
…if they’ve had this problem.
…what version of MT they are running.
The recent CGI problems (erm, outage…) has shown me just how many Movable Type users we have on our servers. It’d be nice to be sure that our systems are the best possible platform for running a MT based weblog.
- Jeff @ DreamHost
- DH Discussion Forum Admin