You are here
Over the past week I've migrated a blog from a shared host to a VPS.NET 2 node VPS running the Turnkey Linux WordPress image. In general it seems to be running ok. (http://www.mgraves.org)
However, several times I've seen the CPU load spike up to 15 nodes! When this happens the site drops offline. It's unresponsive to any kind of connection; web, web admin, ssh, etc.
When I find the site in this state it will not respond to a graceful reboot of the VPS. I can only force a power-down, the a bit a bit and bring it back up.
When it comes back up it runs normally for a day or more, but it eventually encounters the CPU spike again.
Having just migrated from a shared host I'm not clear where to look in the TKL setup to determine if the problem is being caused by a local process or something else?
Any suggestion for which logs might reveal what's going on?
First time something like this is reported
In particular I would check the web server logs to see if anything unusual is happening which coincides with your load spike. It could be a misbehaving bot (e.g., search engine) that's hitting your unusually site hard. It could be spammers. It could be a problem at VPS.NET.
The support forum over at
The support forum over at VPS.Net has quite a few threads that reference this problem. It appears to be a problem with a memory leak in the Ubuntu kernel, but there is no consensus about the exact cause.
These threads date from mid-2009 to present. I'd post a link but their support forums require that you be a customer and logged into your account.
Here's a possible solution that has been suggested:
They even went so far as to update all the TKL images that they offer to include a new kernel. However, I am still seeing this problem.
This is a pity as I had though to used VPS.Net based upon their relationship with TKL. If there is is no solution to this trouble then I may end up migrating (again) to something completely different, not using TKL or VPS.NET.
It makes no sense to me that they offer images that they know present such problems. It might be very convenient to launch TKL into a VPS, but what value is there unless it can be kept running stablely?
I asked if the matter was
I asked if the matter was reported back to TKL project. Here's on response:
I'm not sure this is the same problem
And I may just be beating a dead horse but as I've said before way VPS.NET handled the issue with the kernels was far from ideal. It doesn't even seem to have been a problem with TKL so much as something specific to their Xen implementation. Other partners have been running TKL for over a year now and haven't run into anything like this. But who knows, there can be very complex interactions between a kernel and a hypervisor. That's why Amazon keep a tight control on what kernels are allowed to run on EC2.
BTW, are you sure that forum thread is private? Not all the forums on VPS.NET are...
TKL on VPS.Net
I tried another VPS provider, but tried to stay with TLK. However, I had the same issue with TKL at UnmeteredVPS.Net. The operator of that company was surprised and tried to help me sort it out. After some unsuccessful tweaks we decided to move to a CentOS based VPS.
The whole process was described here:
http://www.mgraves.org/2010/08/blogging-in-transition-a-host-of-issues-%E2%80%93-act-two/
Now that the base system of TKL has been updated I might like to try it again. It included some conveniences that are handy for someone who is not a linux expert.
Sorry to hear you had a bad experience
Anyhow, for what it's worth I left the following response on your blog:
Add new comment