On Thu, Nov 8, 2012 at 2:56 PM, Paul Archer wrote:
> I don't really know when the trouble started.
> I ended up restarting pacemaker on all nodes, and it cleared things
> up. I'm not sure why, though.
You /may/ have been experiencing a known membership issue in older
versions of pacemaker and cor
I don't really know when the trouble started.
I ended up restarting pacemaker on all nodes, and it cleared things
up. I'm not sure why, though.
If I have the same issue come up, I'll run the crm_report and open a bug.
Thanks,
Paul
On Wed, Nov 7, 2012 at 9:22 PM, Andrew Beekhof wrote:
> On Thu,
On Thu, Nov 8, 2012 at 1:55 PM, Paul Archer wrote:
> I'm fairly new to pacemaker, and this is hurting my head.
> I have a four-node cluster, and one of my nodes (for no reason that I
> can discern) has gone offline, and I can't get it to come back online.
>
> Offline node:
> root@vmhost2:/var/lib/
I'm fairly new to pacemaker, and this is hurting my head.
I have a four-node cluster, and one of my nodes (for no reason that I
can discern) has gone offline, and I can't get it to come back online.
Offline node:
root@vmhost2:/var/lib/heartbeat# crm_mon -1
Last updated: Wed Nov 7 20:
