are set to -17,
yet the sshd user instances on the working server, are not :S
Any input from anyone on the below would be VERY much appreciated.
Cal
Original Message
Subject: Re: Fwd: cgroup OOM killer loop causes system to lockup
(possible fix included)
Date: Sun, 2
oblem after each change) and will report back
once I've found the step it kicks in at.
Hopefully, my hours of frustration will prevent someone else from going
through the same thing :/
Cal
On 29/05/2011 23:41, Cal Leeming [Simplicity Media Ltd] wrote:
After submitting this problem to Kern
05/2011 21:25, Ben Hutchings wrote:
On Mon, 2011-05-30 at 21:03 +0100, Cal Leeming [Simplicity Media Ltd]
wrote:
More strangeness..
If I keep the kernel module loaded, but disable the entry
in /etc/network/interfaces for eth0, the oom_adj problem disappears.
But then ofc, I'm left with no ne
It's extremely strange.. :S
Cal
On 30/05/2011 21:31, Cal Leeming [Simplicity Media Ltd] wrote:
Thanks for the response. I have sent this across to the guys at
openssh-server.
Although, I did check the openssh source code myself, and from what I
could tell, everything was being done c
+1 on this problem, im experiencing the same thing :(
Server swaps out, and I get this for 10+ minutes..
top - 22:44:01 up 22:52, 10 users, load average: 20.62, 12.75, 6.58
Tasks: 394 total, 2 running, 392 sleeping, 0 stopped, 0 zombie
Cpu0 : 24.7%us, 27.0%sy, 0.0%ni, 0.0%id, 31.9%wa,
5 matches
Mail list logo
