Failure to Start a ContainerAn attempt to start a Container fails. Solution 1
If there is a message on the system console:
Solution 2
If there is a message on the system console:
pctl set CT_ID --ipadd IP_addr --save
where
Solution 3
Poor UBC parameters might prevent the Container from starting. Try to validate the Container configuration (see
Validating Container Configuration
). See what configuration parameters have caused the error and set appropriate values using the
Solution 4 The Container might have used all its disk quota (either disk space or disk inodes). Check the Container disk quota (see the Managing Disk Quotas section and Chapter 4 for details) and increase the quota parameters if needed (see Setting Up Per-Container Disk Quota Parameters ). Solution 5
Run the
vzfsutil --call –t /vz/template /vz/private/<
The complete reference on the
Solution 6
The Container administrator might have inadvertently modified, replaced, or deleted any file that is part of an application or OS template, which has brought about the Container malfunction. In this case, restore the file(s) with the
Solution 7
Restore the latest operable copy of the Container by means of the
|
||||
|