On Thu, 3 Mar 2011 15:48:03 +0000 (GMT) MJ Ray mjr@phonecoop.coop allegedly wrote:
mick wrote:
I am having a lot of trouble with one of my VPSs - a new one I bought for threepence halfpenny from ThrustVPS.
It's a shame, but if you pay peanuts, you usually get monkeys. ThrustVPS appear to be externalising their support costs onto users and so onto LUGs?
I agree. I run three other VPSs,
- Bytemark - fantastic service, but its not needed because I never have a problem. I'd use them for my tor nodes, I can't get the bandwidth I want at a price I can afford simply to run tor. - daily - equally good, but 750 GB pcm for my tor server - thrust - crap OpenVZ, but cheap and 1000 GB pcm for second tor node
The new thrust VPS was supposed to be on Xen and I could (supposedly) load any of a huge range of distros. I wanted debian 6, but that wouldn't load, nor would debian 5. I ended up with ubuntu as hobson's choice. Nothing but trouble since. Massive packet loss. Hugely unresponsive. I'm only persevering because they won't give money back.
Stay away from them.
[...]
The only process I can see which may be responsible is a kernel process called events/1 which is chewing silly amounts of cpu - see top display below.
I have a vague memory of a server at a client site that was going something similar because of a race between something like hald and the kernel, but I can't lay my hand on the right logbook to say how it was cured or if it was a software or hardware fault. I'd be slightly surprised if a hardware fault affected a VPS, though.
If I were you, I'd be checking all logs, trying to turn up kernel logging verbosity and maybe reading the fine source to see what appears in ps as events/1.
Good luck and please let ALUG know the answer to your riddle when you find it!
Interestingly I notice that none of my logs have been updated since about two and half hours after the time I last rebooted in (yet another) attempt to get a clean load and complained to "support". Some further furtling (during which time I found that root couldn't write and files) showed me that whole system was loaded readonly. Now that may cause a problem.
A reboot cured the RO problem, but unfortunately not the load problem. But at least I now have some up to date logs.....
Mick
---------------------------------------------------------------------
The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this?
Douglas E Comer - Internetworking with TCP/IP Volume 1
http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------