An attempt to start a Virtual Private Server 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
vzctl set --save command. Try to start the
VPS Hosting 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
VPS Hosting numeric identifier,
VPS Hosting class, number of
VPS Hosting’s processes and
VPS Hosting IP address shall be displayed for each running
VPS Hosting. This shall also demonstrate that your
VPS Hosting is up, i.e. it must be running without any IP address assigned. Set its IP address using the command:
Quote:
|
vzctl set ve_id --ipadd addr --save
|
where
ve_id represents the
VPS Hosting numeric identifier and addr represents an actual IP address.
Solution 3
Poor UBC parameters might prevent the
VPS Hosting from starting. Try to validate the
VPS Hosting configuration. See what configuration parameters have caused the error and set appropriate values using the
vzctl set --save command.
Solution 4
The
VPS Hosting might have used all its disk quota (either disk space or disk inodes). Check the
VPS Hosting disk quota and increase the quota parameters if needed.
Solution 5
Run the
vzfsutil utility to make sure that the
vzfs symlinks inside the
VPS Hosting work correctly.
Quote:
For example:
vzfsutil --call –t /vz/template /vz/private/<VPS Hosting_ID>
|
Solution 6
The
VPS Hosting administrator might have inadvertently modified, replaced, or deleted any file that is part of an application or OS template, which has brought about the
VPS Hosting malfunction. In this case, restore the file(s) with the vzctl recover command.
Solution 7
Restore the latest operable copy of the
VPS Hosting by means of the vzrestore utility.
-----------------------------
Best Regards,
UKShane
http://www.eukhost.com