With CentOS 5.3 released on 1st April of this year, more udev related issues crops in. I don’t know when OpenVZ support will get better in its thinking. Issue is there in every VPS who has got the udev upgraded as a result of no excludes in yum.conf entries. Two solutions exists as per http://wiki.openvz.org/Container_enter_failed
Editing the rc.sysinit is the solution which will work here. But when I explained to one of our customers that we edited rc.sysinit, he thought it is /etc/rc.sysinit in the node. Be warned : Don’t do that! Instead from the node edit the etc/sysinit of the VPS, like vi /vz/private/VPSID/etc/rc.sysinit.
However the proper solution, we believe is to
yum remove udev
go ahead with yes to remove dependencies as well. It will also remove ImageMagick, which you have to later install it manually from source. Follow the how to for the installation of ImageMagick below, since the yum based installation of ImageMagick has dependency on hal and udev packages.
/me wonders why are they dependent though..
yum install ghostscript
wget ftp://ftp.imagemagick.org/pub/ImageMagick/ImageMagick.tar.gz
tar xvzf ImageMagick.tar.gz
rm -rf ImageMagick.tar.gz
cd ImageMagick*
./configure –enable-shared –with-modules –with-freetype=yes –with-gs-font-dir=default –with-perl=yes –with-xml=yes –with-zlib=yes –with-jpeg=yes –with-png=yes –without-x
make
make install
After the udev is removed, edit the /etc/yum.conf and make sure that the exclude= line has udev* mkinitrd module-init-tools and kernel* added to it. cPanel usually adds kernel*, but I guess its our responsibility to add udev* in a VPS, till cPanel’s upcp does it for us in a VPS ð
We have a OpenVZ support team and if you need any assistance on OpenVZ, SupportSages can help you in various ways ð
