noetical

I’ve had this problem with several other WordPress sites, even when I moved it to a VPS:
MemTotal: 2096128 kB
8 x 312.507 MHz i686
/proc/cpuinfo
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
model name : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz

The only way I’ve been able to resolve the problem is to move to an extremely expensive server with tons of memory:
MemTotal: 8166676 kB
total used free shared buffers cached
Mem: 7975 1628 6347 0 358 588
-/+ buffers/cache: 680 7294
Swap: 2047 0 2047

model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
model name : Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz

There has to be a way to run medium to high volume WordPress sites on shared servers, or WordPress cannot be the used for low-income independent sites…which seems crazy.

I’ve tried using various caching plugins, APC, various hacks, and at the end of the day, throwing money at it was the only thing that worked.

I’ve had the same problem and was hoping someone here had the solution. While trying to write up this reply, I went through my plugins to list here. Long story short, I discovered that the problem stopped when I deactivated Live Countdown Timer (Version 2.0.0.1 | By Turcu Ciprian | Visit plugin site)

If you aren’t using that plugin, I can’t help you, but if you are…deactivate it and you should be good to go!

I’d love to know what code in that plugin caused the problem, both so that it might be fixed and so that I can avoid other plugins in the future that have the same problem. Anyone have a clue?

Thanks!

I got the same error too, but once I deactivated my plugins, I had no trouble upgrading after that. No need to change themes. I have a very complicated theme (ATAHUALPA) with multiple customizations (including lots of header images) and leaving it activated during the upgrade didn’t cause me any trouble. After the upgrade, I just reactivated all my plugins and everything seems to be running smoothly now.