Posted on Sunday, July 29th, 2012 at 12:25 pm.
If you’re running cPanel server on a OpenVZ hardware node, you might face issues with quota for few reasons:
1. Secondary quota might not have been enabled on hardware node.
You can verify by checking for “DISK_QUOTA=yes” in /etc/vz/conf/vz.conf
Also, QUOTAUGIDLIMIT needs to be set for the VPS in
/etc/sysconfig/vz-scripts/CT_ID.conf (PS: CT_ID is the container id of the VPS)
2. You should have initialized the quota via WHM.
If you continue to face problem even after applying both fixes, re-initializing quota might help as per
http://wiki.openvz.org/Cpanel_quotas Here is the excerpt:
WHM/Cpanel, a popular commercial web-based control panel for Linux, has a tendency to overwrite the special quota files in the VE context. I am referring to:
lrwxr-xr-x 1 root root 39 Jun 8 17:27 aquota.group -> /proc/vz/vzaquota/00000073/aquota.group
lrwxr-xr-x 1 root root 38 Jun 8 17:27 aquota.user -> /proc/vz/vzaquota/00000073/aquota.user
The result of these being overwritten will be WHM showing “unlimited” quota reports for all users in the system. An quick solution to this is to run these commands from within the VE as root:
rm -rf /aquota.user 2>/dev/null
rm -rf /aquota.group 2>/dev/null
unlink /aquota.user 2>/dev/null
unlink /aquota.group 2>/dev/null
for x in `find /proc/vz/vzaquota/ | tail -2 `; do ln -s $x / ; done
journled quota support warning didn’t get resolved even after this. Yet to check for the core reason for the same.
Posted on Monday, March 26th, 2012 at 3:42 am.
If you want to run virtual machines of different ip subnets from your
OpenVZ node you will have to enable a parameter in /etc/vz/vz.conf.
Following is the remedy for those who are facing issues working with multiple subnet ip’s
# Controls which interfaces to send ARP requests and modify ARP tables on.
Posted on Friday, June 3rd, 2011 at 8:15 pm.
Following error is noticed when you are running
apf in the OpenVZ VM.
iptables: Unknown error 4294967295
Main reason for this error iptables support missing in OpenVZ.
Here are the quick steps to resolve this issue permanently:
1. Define which iptables modules are available for VEs.
/etc/sysconfig/iptables-config file on a OpenVZ hardware node:
IPTABLES_MODULES=”ipt_REJECT ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp”
/etc/sysconfig/vz file on a OpenVZ hardware node:
ipt_tos ipt_TOS ipt_LOG ip_conntrack ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_state iptable_nat ip_nat_ftp”
Note:- iptables modules list in IPTABLES and IPTABLES_MODULES parameters in
/etc/sysconfig/iptables-config files should be placed in one single line, no linebreaks is allowed in this parameter.
Restart OpenVZ server
# service vz restart
2. Increase ‘numiptent’ parameter for the VE you need to install APF into. This parameter limits the amount of iptables rules available for a VE. Default APF configuration requires ~400 rules. Lets set it to 400 in the example below for VE #101:
# vzctl set 101 --numiptent 400 --save
3. Start APF inside the VE:
# /etc/init.d/apf start
apf, iptables, OpenVZ