If you start receiving such type of error messages on VPS then you are running short of some of resources that are allocated to your VE, you can check which resource is causing problems by running following command from shell of VE you are facing problems with or from Node.
HTML Code:
root@master [/]# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
110: kmemsize 4646467 6826885 12752512 22752512 815
lockedpages 0 0 32 32 0
privvmpages 89524 102297 98304 107150 35698
shmpages 219 987 8192 8192 0
dummy 0 0 0 0 0
numproc 67 98 130 130 0
physpages 34938 45456 0 2147483647 0
vmguarpages 0 0 98304 2147483647 0
oomguarpages 34938 45456 6144 2147483647 0
numtcpsock 25 73 80 80 0
numflock 9 17 100 110 0
numpty 1 1 16 16 0
numsiginfo 0 16 256 256 0
tcpsndbuf 0 319748 319488 524288 3
tcprcvbuf 0 220260 638976 1048576 0
othersockbuf 24596 134300 132096 336896 8822
dgramrcvbuf 0 8380 264192 264192 0
numothersock 24 48 80 80 0
dcachesize 0 0 1048576 1097728 0
numfile 1263 1832 2048 2048 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 10 57 128 128 0
root@master [/]#
check failcnt colum it will display number of failures due to inappropriate allocation of particular resource to VPS
you can increase particular resource by editing configuration file for particular VE, you can find configuration fle at /etc/vz/conf/VEID.conf replace VEID with actual VE ID in our case it would be 110.conf, find resurce that is having maximum of failure count increase it to some higher extent and then restart VE.
Or you can run following command to increase resource
vzctl set <VEID> --<resource name> barrier:limit --save
for eg.
vzctl set 110 --privvmpage 107150:117150 --save
poof
06-22-2007, 01:39 AM
Linear Mode
Similar Threads
