I think now that this solution is not good:-))) The better way is
fully restart cluster. before you restart it you mast set it in
maintenance mode (in this mode pacemaker will not try manage already
started service, so you doesn't get downtime):
property maintenance-mode=true
2012/11/8 Carlos Mol
ruslan usifov writes:
>
>
> I solve this problem!On one node in log i found follow error message.slv009
peer is not p art of our clusterSo i stop pacemaker in that host (i use
v1 for pacemaker):/etc/pacemaker stop
> /etc/corosync stop Then remove all cib info from /var/lib/heatbeat/crm a
2012/2/27 Andrew Beekhof
> On Sat, Feb 25, 2012 at 8:28 AM, ruslan usifov
> wrote:
> > I solve this problem!
> >
> >
> > On one node in log i found follow error message.
> >
> > slv009 peer is not p art of our cluster
> >
> > So i stop pacemaker in that host (i use v1 for pacemaker):
> >
On Sat, Feb 25, 2012 at 8:28 AM, ruslan usifov wrote:
> I solve this problem!
>
>
> On one node in log i found follow error message.
>
> slv009 peer is not p art of our cluster
>
> So i stop pacemaker in that host (i use v1 for pacemaker):
>
> /etc/pacemaker stop
> /etc/corosync stop
>
>
>
I solve this problem!
On one node in log i found follow error message.
slv009 peer is not p art of our cluster
So i stop pacemaker in that host (i use v1 for pacemaker):
/etc/pacemaker stop
/etc/corosync stop
Then remove all cib info from /var/lib/heatbeat/crm and cleanup
/var/lib/pen
Hello
I have 3 nodes cluster setup. After upgrade OS, i get that one node
parmanently on OFFLINE state.
OS: ubuntu 10.0.4
pacemaker: 1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c
on OFFLINE node i see in log follow:
Feb 24 20:27:45 slv009 crmd: [9125]: info: do_dc_release: DC role released
