UBC failcnt reset - Revision history

Finist: bugzilla.openvz.org -> bugs.openvz.org

2017-02-16T10:25:05Z

bugzilla.openvz.org -> bugs.openvz.org

2015-07-08T19:42:41Z

‎Alternative bash script: collapse script text by default

2012-12-14T16:24:02Z

‎OK, I understand, but I still want to clear failcnt!

2012-06-29T12:09:14Z

1298 is a different bug

2012-06-29T12:08:46Z

+vzubc

2011-10-17T20:10:26Z

‎External links: +yabeda

2011-07-11T13:15:20Z

‎How to clear failcnt?: link to vzubc

2011-07-08T14:46:12Z

‎Bash script

2011-07-08T14:45:06Z

‎Bash script

2011-07-08T14:39:48Z

@@ Line 19: / Line 19: @@
 If you still see failcnt not reset to 0 after more than 5 minutes after container is stopped, your kernel was likely compiled with CONFIG_UBC_KEEP_UNUSED=y, and in that case you'll have to switch off this option if you want to reset beancounters when container is restarted.
-If you're sure your kernel was NOT compiled with the above option and it's not resetting failcnt after 5 minutes, it means there is a bug in UBC code. Please file a detailed [[bug report]] to [http://bugzilla.openvz.org bugzilla.openvz.org]
+If you're sure your kernel was NOT compiled with the above option and it's not resetting failcnt after 5 minutes, it means there is a bug in UBC code. Please file a detailed [[bug report]] to [http://bugs.openvz.org bugs.openvz.org]
 == vzubc ==

@@ Line 66: / Line 66: @@
 === beanc source code ===
-<source lang=bash>
+<div class="mw-collapsible mw-collapsed">
 #!/bin/bash
 #####################################################################################################################
@@ Line 476: / Line 478: @@
 esac
 </source>
 == External links ==

@@ Line 15: / Line 15: @@
 UBC failcnts are stored for the duration of the uptime of your container. Thus, restarting the container resets the counts.
-The problem here is tcp time wait buckets can still there after a container 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.
+The problem here is tcp time wait buckets can still be there after a container 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.
 If you still see failcnt not reset to 0 after more than 5 minutes after container is stopped, your kernel was likely compiled with CONFIG_UBC_KEEP_UNUSED=y, and in that case you'll have to switch off this option if you want to reset beancounters when container is restarted.

@@ Line 476: / Line 476: @@
 esac
 </source>
 == External links ==

@@ Line 21: / Line 21: @@
 If you're sure your kernel was NOT compiled with the above option and it's not resetting failcnt after 5 minutes, it means there is a bug in UBC code. Please file a detailed [[bug report]] to [http://bugzilla.openvz.org bugzilla.openvz.org]
-== Bash script ==
+== vzubc ==
 This script can show the failcount deltas for one or all containers since last reset, and reset the failcounts for one or all containers.

@@ Line 480: / Line 480: @@
 * {{Forum|361}}
 * {{Forum|497}}
 [[Category:FAQ]]
 [[Category:UBC]]

@@ Line 9: / Line 9: @@
 There can be many applications that read <code>/proc/user_beancounters</code>, and thus if you will reset it, you may have problems with those other apps. Consider what happens if you reset your sent/received packets/bytes statistics on a network interface — programs which track it may not function properly.
-Therefore, the proper usage of 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.
+Therefore, the proper usage of 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. There is a utility {{Man|vzubc|8}} which can be used for that purpose. Also, see [[#Bash script]] below.
 == OK, I understand, but I still want to clear failcnt! ==

@@ Line 28: / Line 28: @@
 It uses only standard commands and programs that are usually included in all linux distro's:
-* bash
+bash, cat, grep, awk, head, tail, printf
 === Installation ===

@@ Line 26: / Line 26: @@
 This script can show the failcount deltas for one or all containers since last reset, and reset the failcounts for one or all containers.
 === Installation ===
@@ Line 36: / Line 45: @@
 === Show the beancounters ===
-    beanc show
+ beanc show
 this compares the contents of /proc/user_beancounters and the reference file, and shows you the delta value
 if no reference file exists, a copy of the user_beancounters file is used.
 to only show you the failcounts for 1 container, just add the ctid or container name to the command
-    beanc show mailserver
+ beanc show mailserver
-    beanc show 102
+ beanc show 102
 === Reset failcounters ===
-    beanc reset mailserver
+ beanc reset mailserver
-    beanc reset 102
+ beanc reset 102
-    beanc reset                   --> will reset failcounters for all containers
+ beanc reset                   --> will reset failcounters for all containers
 Confirmation will be asked.
 === Show only failcounts > 0 ===
-          beanc brief
+ beanc brief
 === Initialize reference file ===
-    beanc init
+ beanc init
 This will check if the app-directory exists (/var/lib/beanc) and create it if necessary
 It also creates a reference file (/var/lib/beanc/user_beancounters)
 BEWARE, this command will overwrite any existing reference file !