Implement New Theme: Runaway Apache processes
-
I am trying to implement a custom theme that a vendor has created on our WordPress Multisite. Basically, it’s just a more feature-rich version of the theme we are already running there.
I swap in the code, and then…
All hell breaks loose: Apache starts spawning all these processes until all the RAM is chewed up and the server freezes.
I should mention, this is all on a plain vanilla CentOS, Apache, mod-php WP Multisite that’s been running several sites for years.
As far as I can tell there is nothing wrong with this new Theme. It runs fine on our Development Multisite. It runs fine on a copy of one of our sites that I’ve duplicated to my local workstation.
At first I thought there might be some kind of pre-caching happening, but we disabled our problematic cache plugin a while back.
Any idea why a new Theme might trigger an out of control spawning of Apache processes?
We tried switching to php-fpm. No Joy. (Plus, when on php-fpm all our Admin pages were screwed up, like styles missing, etc.)
I am not seeing any Clues in the logs.
Vexed,
Mark
The topic ‘Implement New Theme: Runaway Apache processes’ is closed to new replies.