Serverwide problems caused by Movable Type are getting worse by the day. There is no solid reason for why it happens or real solution to resolve the issues. We have extensively researched and also inquired to the makers. They report that the problems are caused by plug-in programs that users add to MT. To us it seems that it cannot be true if we also see mt.cgi with high usage, which is the main MT file to my knowledge. However, that reason surrounding user modifications does make sense in a way because this does not happen to all installs of MT, only a certain few. Strangely, many of those certain few are normal installs, without any plug-ins. So, we are back to square one.
If you currently use Movable Type on your website, we urge you to change your program to avoid any problems.
I want to state again how strange of a situation it is, because not every installation of Movable Type causes problems and it is not always the same scripts that cause the issues.
For example:
Crash 1: %CPU 99.9 /usr/bin/perl -w mt-comments.cgi
Crash 2: %CPU 93.3 /usr/bin/perl -w mt-something.cgi
Crash 3: %CPU 86.5 /usr/bin/perl -w mt-blacklist.cgi
From now on if a Movable Type related script causes an issue on a server, you will not be able to use the program again in most circumstances. (It will depend on the file(s) that caused the issue.) We hate that it has come to this, but we cannot continue the current cycle of suspending/unsuspending that we are in now. We have to finally handle this in a uniform fashion.
On the other hand, you may have Movable Type installed for months now and never have caused an issue, and may never will. These issues are completely random.
I hope that everyone can understand why we have finally decided to do this. Half of all server burps are caused by MT and suspending/unsuspending/suspending these sites over and over again is not truly helping and certainly not helping everyones' websites stay online 24/7.