[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Linux-cluster] manual fencing -- issues



On Wed, 2008-01-30 at 03:23, Terry wrote:
> On Jan 29, 2008 11:18 AM, Bryn M. Reeves <breeves redhat com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Terry wrote:
> > > Hello,
> > >
> > > I know that manual fencing is not supported.  However, I don't have
> > > anything else with the hardware I am testing at this time.  When (if)
> > > we go live with this, I'll be using Dell DRACs to handle the fencing.
> > > At any rate, I am trying manual fencing to test proof of concept.  I
> > > am using RHEL5.1 with Conga to configure it.  My config is at the
> > > bottom of this email.   Shouldn't there be a nodename paramater in
> > > this block:
> > >                         <fence>
> > >                                 <method name="1">
> > >                                         <device name="fence00"
> > > nodename="dss01.foobar.local"/>
> > >                                 </method>
> > >                         </fence>
> > >
> > > ??  If so, why isn't Conga configuring this correctly?  If not, why am
> > > I getting this error during a crash of the node with the service on
> >
> > Sounds like you hit:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=238655
> >
> > The bugzilla is in the status ON_QA while the fixes are verified. In the
> > meantime you should be able to work around this by manually editing the
> > generated cluster.conf.
> >
> > Kind regards,
> > Bryn.
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.7 (GNU/Linux)
> > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> >
> > iD8DBQFHn1/I6YSQoMYUY94RAkMJAJ0eVRl/EJSpDDBGAajpN3RJceZdfgCbBiKo
> > KheIW7o60T5a3QfElLtTtWA=
> > =eotz
> > -----END PGP SIGNATURE-----
> 
> Along that note, what do I need to do when updating the cluster.conf
> manually?  Any commands to let the cluster know what I did.

after you've run the command below you also need to run cman_tool to let
the cluster know that the config version changed.

ccs_tool update /etc/cluster/cluster.conf

cman_tool version -r <new_config_version>

Check with "cman_tool status" on all nodes to see if the changes (config
version) have propagated to the other nodes

Michael

> Unfortunately, I am learning through the GUI, haha.  I may as well go
> get my MCSE now.
> 
> --
> Linux-cluster mailing list
> Linux-cluster redhat com
> https://www.redhat.com/mailman/listinfo/linux-cluster


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]