OpenVZ Forum


Home » General » Support » [solved] Error: Unable to apply new quota values: quota not running
[solved] Error: Unable to apply new quota values: quota not running [message #51237] Sat, 15 March 2014 20:04 Go to previous message
postcd is currently offline  postcd
Messages: 73
Registered: April 2013
Member
[solved] - last post of this topic

Hello, i created VM and this is what i get: (it cant start)

Quote:

[root@icph conf]# vzctl start 720
Starting container...
Can't umount /vz/root/720: Invalid argument
Adding IP address(es): ***
Setting CPU limit: 100
Setting CPU units: 1000
Setting CPUs: 1
Error: Unable to apply new quota values: quota not running
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Killing container ...
Container was stopped
Error: Unable to apply new quota values: quota not running
Can't umount /vz/root/720: Invalid argument


[root@***~]# tail /var/log/vzctl.log -n80 | grep 720
2014-03-15T15:36:35-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:36:35-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:36:54-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:36:54-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:18-0400 vzctl : CT 720 : Starting container...
2014-03-15T15:37:18-0400 vzctl : CT 720 : Can't umount /vz/root/720: Invalid argument
2014-03-15T15:37:18-0400 vzctl : CT 720 : Adding IP address(es): ***
2014-03-15T15:37:19-0400 vzctl : CT 720 : Setting CPU limit: 100
2014-03-15T15:37:19-0400 vzctl : CT 720 : Setting CPU units: 1000
2014-03-15T15:37:19-0400 vzctl : CT 720 : Setting CPUs: 1
2014-03-15T15:37:19-0400 vzctl : CT 720 : Error: Unable to apply new quota values: quota not running
2014-03-15T15:37:19-0400 vzctl : CT 720 : Container start failed (try to check kernel messages, e.g. "dmesg | tail")
2014-03-15T15:37:19-0400 vzctl : CT 720 : Killing container ...
2014-03-15T15:37:20-0400 vzctl : CT 720 : Locked by: pid 137497, cmdline vzctl start 720
2014-03-15T15:37:20-0400 vzctl : CT 720 : Container already locked
2014-03-15T15:37:20-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:21-0400 vzctl : CT 720 : Container was stopped
2014-03-15T15:37:21-0400 vzctl : CT 720 : Error: Unable to apply new quota values: quota not running
2014-03-15T15:37:21-0400 vzctl : CT 720 : Can't umount /vz/root/720: Invalid argument
2014-03-15T15:37:25-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:30-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:35-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:39-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:39-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:40-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:37:45-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:38:24-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:38:24-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:38:30-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:38:30-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:38:38-0400 vzctl : CT 720 : Container is not running
2014-03-15T15:38:38-0400 vzctl : CT 720 : Container is not running


My control panel (hypervm) also says:
Alert: Could Not Start Vps, Reason: Can't umount /vz/root/720: Invalid argument: Error: Unable to apply new quota values: quota not running: Container start failed (try to check kernel messages, e.g. ...


[root@*** conf]# vi /etc/sysconfig/vz-scripts/720.conf
# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="102398976:102398976"
DISKINODES="51199488:51199488"
QUOTATIME="0"

# CPU fair scheduler parameter
CPUUNITS="1000"
VE_ROOT="/vz/root/$VEID"
VE_PRIVATE="/home/vps/720"
OSTEMPLATE="debian-6.0-x86"
ORIGIN_SAMPLE="basic"
IP_ADDRESS="***"
QUOTAUGIDLIMIT="10000"


Please any idea on what to check/do?


--
when i did "vzmigrate" from my old node server to this new node server, it succeeded, and im able to start stop, reboot change Plan for VM without issue, so i dont know why it failed..

Another tips:
Quote:
# vzctl set <CTID> --quotaugidlimit num

man page of vzctl, "Disk quota parameters":


Quote:
/etc/sysconfig/vz-scripts/xxx.conf

xxx node nr

setup it to QUOTAUGIDLIMIT="3000"


Quote:
http://forum.openvz.org/index.php?t=msg&th=5272&goto =36740&#msg_36740


Quote:
http://forum.openvz.org/index.php?t=msg&th=136&goto= 26250&#msg_26250



Man diskquota - http://openvz.org/Disk_quota
Quote:
If your host filesystem is not ext2/3/4 (like XFS) the disk quotas will not work inside containers.
Yellowpin.svg Note: ext4 is also fully supported in 2.6.32 kernels and in RHEL5-based kernels since 028stab066.7


df -h
Quote:
[root@***conf]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
1.8T 161G 1.5T 10% /
/dev/sda1 99M 38M 56M 41% /boot
tmpfs 12G 0 12G 0% /dev/shm


cat /etc/fstab
Quote:

/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0

[Updated on: Sat, 15 March 2014 22:24]

Report message to a moderator

 
Read Message
Read Message
Previous Topic: Database Server just to be reached internal
Next Topic: Public IP via VETH seen as the bridge interface IP
Goto Forum:
  


Current Time: Mon Jul 29 07:24:33 GMT 2024

Total time taken to generate the page: 0.02612 seconds