Recently we pushed out a new Easyapache build on all of our servers. Everything appears to have went fine, and I believe the only change was an upgrade to ioncube and zend. We kept the original template, so I know that no changes were made in that regard. Our servers are running CentOS 5.4, with Apache 2.2.14 and Cpanel::Easy::Apache v3.2.0 rev4899. The PHP configuration varies a bit depending on the server, but we run both PHP4 and PHP5, one as a DSO, the other as suPHP. Everything will run fine for a random amount of time, then suddenly (within a couple minutes) the load will spike up to over 100. After ssh'ing in and looking, there are many apache processes running, and quite a few of them are using ~ 10% CPU. What I gather is the CPU usage spikes from apache, then the requests just start backing up which causes more child processes to spawn. This eventually leads to the server eating all its available CPU, RAM, and swap space if not dealt with. Has anyone else seen this happen recently? The last time we saw something like this was when wordpress pushed out an update with some bad code and cause apache to eat 100% CPU, though I'm not sure if thats the case here. Please let me know if you need any additional diagnostic information. We are seeing this on around 80 or so servers at the moment.