Open main menu

OpenVZ Virtuozzo Containers Wiki β

Changes

UBC failcnt reset

10 bytes removed, 10:40, 21 December 2007
Grammar, misc cleanup
You do not need to, and this would be an incorrect thing to do.
There can be many application who reads applications that read <code>/proc/user_beancounters</code>, and thus if you will reset it , you gonna may have problems with those other apps. Consider what happens if you will reset you your sent/received packets/bytes statistics on the a network interface — programs which reads will be screwed uptrack it may not function properly.
SoTherefore, the proper procedure usage of checking failcnt is not to check whether it is zero or not, but to check whether it is increased since the previous readout. In other words, check the difference, not the absolute value. It is easy to write a simple script to do just that.
== OK, I understand, but I still want to clear failcnt! ==
OK, you can do so by restarting UBC failcnts are stored for the duration of the uptime of your VE. Since fail counters are for VE lifetimeThus, they will be cleared after restarting the VE stopresets the counts.
The problem here is tcp time wait buckets can still there after a VE is stopped. You can check that by seeing the <code>held</code> column for <code>kmemsize</code> parameter. If it is not zero, that means you have to wait about 5 minutes in order to time wait buckets to expire, and the corresponding beancounter to be uncharged.
4
edits