OpenVZ Forum


Home » General » Support » Troubleshooting VE start failure
Re: Troubleshooting VE start failure [message #32562 is a reply to message #32556] Sat, 16 August 2008 04:44 Go to previous messageGo to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

There are a lot of approaches...

First of all, check dmesg | tail for any erorrs. Then run vzctl start with --verbose.

Check VE config (/etc/vz/conf/$VEID.conf) -- there should be a usual set of parameters. From what I see you do not have OSTEMPLATE parameter specified -- not a problem since vzctl falls to default which happen to be RedHat/Fedora and this is what you're actually running but for the sake of completeness set it to fedora-8 or smth.

If that won't help, issue vzctl mount $VEID and cd to /vz/root/$VEID. There you can see the VE filesystem. It should look like a normal Linux/UNIX filesystem, i.e. stuff like /bin /lib /sbin /usr /proc etc.

Now you can chroot into it and run some checks:
chroot /vz/root/$VEID
# check all RPM packages, there should be a number of warnings but not too much
rpm -Va
# (if rpm won't start that something really bad happened to your VE)
# check /dev, there should be some basic stuff
ls -l /dev
# check logs, they might give you a clue what happened
less /var/log/messages
# check /sbin/init
ls -l /sbin/init
ldd /sbin/init # see that all libraries are resolved
# check /etc/inittab
less /etc/inittab


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [solved] x86_64 Kernel: 2.6.18-92.1.1.el5.028s won't boot
Next Topic: VE fails to startx
Goto Forum:
  


Current Time: Sun Sep 15 20:29:44 GMT 2024

Total time taken to generate the page: 0.04392 seconds