From: <go...@bo...> - 2007-12-20 16:28:10
|
On Thu, 20 Dec 2007, Mark Hlawatschek wrote: >> However, mkinitrd seems to mangle and rewrite my cluster.conf and remove >> all the fencing devices. Is this normal? Is there anything special I have >> to do to get fencing to work? I am using fence_drac, if that makes any >> difference. > mkinitrd shouldn't do anything to your cluster.conf. mkinitrd will always use > the cluster.conf in /etc/cluster/cluster.conf. Please make sure, that the > version number of the latest cluster.conf is increased and it is deployed to > all cluster nodes using a "ccs_tool update /etc/cluster/cluster.conf". I rebuilt the initrd, and the cluster.conf that ends up in /var/comoonics/chroot/etc/cluster/cluster.conf is NOT the same as the one in /etc/cluster/cluster.conf It seems to me that cluster.conf ends up getting rebuilt and mangled by mkinitrd before it is folded into the initrd. > If you want to use fence_drac, you need to put all required perl stuff into > the chroot environment. This can be either done by > 1) adding all perl stuff into the initrd or > 2) adding the perl stuff only into the chroot environment during the boot > process. > > to do this, create a file called perl.list with the following content: > > -->snip > perl > perl-libwww-perl > perl-XML-Encoding > perl-URI > perl-HTML-Parser > perl-XML-Parser > perl-libxml-perl > perl-Net-Telnet > perl-HTML-Tagset > perl-Crypt-SSLeay > ##### > -->snap > and copy it into > > 1) /etc/comoonics/bootimage/rpms.initrd.d/ > and make a new rpm Not sure I follow what you mean. What rpm? > _or_ > 2) /etc/comoonics/bootimage-chroot/rpms.initrd.d/ > and run "service bootsr start" Run this on the booted system? What does the bootsr service do? Gordan |