[PDF] Parallels Server 5 Bare Metal

Troubleshooting
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. 34) for instructions). Try to start the Container once
again.
Solution 2
If there is 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. 153)). See what configuration
parameters 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. 116) and Chapter 4 for details)
and increase the quota parameters if needed (see Setting Up Per-Container Disk Quota
Parameters (p. 119)).
Solution 5
Run the vzfsutil utility to make sure that the VZFS symlinks inside the Container work correctly.
For example:
vzfsutil --call –t /vz/template /vz/private/
The complete reference on the vzfsutil utility is provided in the Parallels Command Line
Reference Guide.
Solution 6
252