Cannot start OpenVZ container: Unable to apply new quota values: ugid quota not initialized

Have more questions? Submit a request

Applicable to:

  • SolusVM

Symptoms

The container on the OpenVZ node fails to start:

# vzctl start 101
Removing stale lock file /vz/lock/101.lck
Starting container...
vzquota : (warning) Quota is running for id 101 already
Container is mounted
Adding IP address(es): 203.0.113.2
Setting CPU limit: 700
Setting CPU units: 1800
Setting CPUs: 6
Unable to apply new quota values: ugid quota not initialized
Container start failed (try to check kernel messages, e.g. "dmesg | tail")
Killing container ...
Container was stopped

Cause

The container shutdown was interrupted or quota file was corrutped.

Resolution

  1. Connect to the node server via SSH
  2. Drop the quota for the container:

    # vzquota drop 101

  3. Start the container:

    # vzctl start 101

Note: Container ID in the examples above should be changed from 101 to the actual container ID

Warning: It can take a significant time to initialize the quota for the container, do not interrupt the process.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Please sign in to leave a comment.