I have two clusters that are both running CentOS 5.6 and
heartbeat-3.0.3-2.3.el5 (from the clusterlabs repo). THey are running
slightly different pacemaker versions (pacemaker-1.0.9.1-1.15.el5 on the
first one and pacemaker-1.0.12-1.el5 on the other) They both have
identical ha.cf files except
I know it's tacky to reply to myself, but I can answer one of my
questions after another 15 minutes or so of poring through logs:
On Tue, 2013-05-28 at 10:37 -0600, Greg Woods wrote:
The questions are what do these messages actually mean, why is one
cluster logging them and not the other,
On Mon, 27 May 2013, Dejan Muhamedagic wrote:
Hi,
On Wed, May 22, 2013 at 01:20:06PM +, Tony Stocker wrote:
Version Info:
OS: CentOS 6.4
Kernel (current): 2.6.32-358.6.2.el6.x86_64
Pacemaker: 1.1.8-7.el6
Corosync: 1.4.1-15.el6_4
On 29/05/2013, at 2:37 AM, Greg Woods wo...@ucar.edu wrote:
I have two clusters that are both running CentOS 5.6 and
heartbeat-3.0.3-2.3.el5 (from the clusterlabs repo). THey are running
slightly different pacemaker versions (pacemaker-1.0.9.1-1.15.el5 on the
first one and
On Wed, 2013-05-29 at 07:50 +1000, Andrew Beekhof wrote:
respawn hacluster /usr/lib64/heartbeat/ipfail
crm respawn
I don't know about the rest, but definitely do not use both ipfail and crm.
Pick one :)
I guess I will have to look into what ipfail really does. I have a half
dozen
On 29/05/2013, at 8:05 AM, Greg Woods wo...@ucar.edu wrote:
On Wed, 2013-05-29 at 07:50 +1000, Andrew Beekhof wrote:
respawn hacluster /usr/lib64/heartbeat/ipfail
crm respawn
I don't know about the rest, but definitely do not use both ipfail and crm.
Pick one :)
I guess I will have
