On Wed, 14 Oct 2009 17:50:34 +0200, carlopmart wrote
> Jan Friesse wrote:
> > Carlopmart,
> > it's not problem of fence_vmware_ng and definitively not malfunction.
> > Cluster is trying to keep all possible nodes going. So what will happend:
> > - You will boot node01
> > - This will start fencing, and finds out, that node02 isn't running (is
> > falled, ...) -> fence node2
you may change post_join_delay to something bigger than 3sec to delay the
fencing of node2 or to start fenced with -c (clean start) if you want to avoid
fencing of node2 completely
> > - Node2 is fenced and starts
> >
> > Regards,
> > Honza
> >
> Thanks Jan for your explanation.
>
> --
> CL Martinez
> carlopmart {at} gmail {d0t} com
>
> --
> Linux-cluster mailing list
> Linux-cluster@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
