Hi all!
I'm writing a domain-specific frontend for Pacemaker, which can set up
a few different pre-configured "stacks" of resources, and provide
simplified monitoring and administration of those stacks.
One thing I'm wondering about is the correct way to query for the
current status of a particul
I feel like I've looked at every board about this and have yet to see a fix.
I've tried to setup both Heartbeat and Corosync on my freshly installed Ubuntu
14.04 system. Both Heartbeat and Corosync will not connect. CRM_MON gives me
an error about Connection Refused (111). There are no firew
Hi,
On Thu, Feb 05, 2015 at 09:18:50AM +0100, Digimer wrote:
> That is the problem that makes geo-clustering very hard to nearly
> impossible. You can look at the Booth option for pacemaker, but that
> requires two (or more) full clusters, plus an arbitrator 3rd
A full cluster can consist of one
Hi Michael.
I mean this, when I reboot the server., pacemaker starts automatically but
I do no see the VIP in the eth0, sorry I used the word alias which may have
lead to a confision.
ip addr show
1: lo: mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00
writes:
> > If the pingnode became not visible on node2, I will see pingd attribute
> > on
> > node2 set to 0 and dummy resources stop on node2.
> > If I cut off nentire network on node2, I will see pingd attribute on
> > node2
> > set to 0 bud dummy resource never stop.
> > During network fai