Changes

Jump to: navigation, search

Resource shortage

40 bytes added, 22:49, 13 July 2006
reworked UBC settings
There are two ways to fix the situation: reconfugure (in some cases recompile) the application, or change the resource management settings.
== [[UBC ]] parameters ==
Here is the example of current [[UBC]] stands for [[User Beancounters|'''u'''ser '''b'''ean'''c'''ounters]] &mdash; this is a set of limits and guarantees contolled per VE. You can see the current usage values and limits by examining the output of obtained from <code>/proc/user_beancounters</code> file. Here is the example of /proc/user_beancounters inside in VE with ID of 123:
<pre>
# cat /proc/user_beancounters
</pre>
Note You can see if you hit the limits for some [[UBC]] parameters by analyzing the last column (named <code>failcnt</code>) &mdash; it . It shows a number of fails for this counter, i.e. a number of times the a parameter hit the limit. Usually what you need to do is to increase the parameter in question. But you need to do it carefully, and here is how.
<ol>
<li>Get the current values for the parameter's barrier and limit. For example, we want to increase kmemsize values from the above exampleat . From Say, from <code>/proc/user_beancounters </code> example given [[UBC|here]] we see that kmemsize barrier is 2752512, and its limit is 2936012.
</li>
# vzctl set 123 --kmemsize $((2752512*1.5)):$((2936012*1.5)) --save
</pre>
By using <ttcode>--save</tt> flag, we denote we want to both apply the new settings to the running VE, and save them in the configuration file (from which they will be taken during next VE start).
</li>
</li>
</ol>
 
For more in-depth explanation of different parameters, their meaning and how to set them properly, see [[setting UBC parameters]].
== Disk quota ==

Navigation menu