Re: Disabling all limits [message #35642 is a reply to message #35624] |
Thu, 09 April 2009 22:21 |
divB
Messages: 79 Registered: April 2009
|
Member |
|
|
Thank you very much, I decided do not remove the limits but rather adapt the needed values manually.
But, please help me a little bit: What is the best (i.e. empiric) way to adopt the limits according to the "failcnt" value? It seems that just adding this value to the soft/hardlimit isn't enough...
What I do: I have written a small awk-script which monitors the sum of the failcnt-column in /proc/user_beancounters and if this value is >= 0 (i.e. some hosts have insufficient resources) send the output via cron.
I have a VE with the following content:
privvmpages 68769 90280 67536 71632 97
(and PRIVVMPAGES="87536:91632" in the config).
This means that this value is just ~100 too low; what to I do? vzctl set 201 --privvmpages 87536:91632 --save and restarting the VE. As you can see, I add 10000 (!) although only 97 are needed. But some time after restarting: same result. I adjusted the limit a few times now but failcnt becomes always nonzero for this specific limit after some time. So, what I am doing wrong?
There are other values in other VEs where I have the same problem, e.g.:
kmemsize 5122700 11059046 11055923 11377049 1434
And, one other thing. If I stop a VE, the entries in /proc/user_beancounters are not removed (only after some time). Why? This is especially problematic when I want to correct the limits, do "vzctl 201 restart" and check if the problems have gone.
I hope you can follow me
Regards,
divB
|
|
|