User`s guide

Troubleshooting 201
Failure to Start a Container
An attempt to start a Container fails.
Solution 1
If there is a message on the system console: parameters missing, and the list of missed
parameters follows the message, set these parameters using the pctl set --save command
(see Performing Initial Configuration (p. 30) for instructions). Try to start the Container once
again.
Solution 2
If there i
s a message on the system console: IP address is already used, issue the
cat /proc/vz/veinfo command. The information about the Container numeric identifier,
Container class, number of Container’s processes and Container IP address shall be displayed
for each running Container. This shall also demonstrate that your Container is up, i.e. it must be
running without any IP address assigned. Set its IP address using the command:
pctl set CT_ID --ipadd IP_addr --save
where CT_ID represents the Container numeric identifier and IP_addr represents an actual IP
address.
Solution 3
Poor UBC parameters might prevent the Container from starting. Try to validate the Container
configuration (see Validating Container Configuration (p. 121)). See what configuration
param
eters have caused the error and set appropriate values using the pctl set --save
command.
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 (p. 92) and Chapt
er 4 for details)
and increase the quota parameters if needed (see Setting Up Per-Container Disk Quota Parameters
(p. 95)).
Solution 5
Run the vzf
sutil utility to make sure that the VZFS symlinks inside the Container work
correctly. For example:
vzfsutil --call –t /vz/template /vz/private/<CT_ID>
The complete reference on the vzfsutil utility is provided in the Parallels Command Line
Reference Guide.
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 pctl recover command (see the
Reinstalling Container section (p. 67) for details).