On 09/08/11 02:36, Bobbie Lind wrote:
I have 6 servers with three sets of 2 failover pairs. So 2 servers for
one pair, 2 servers for another pair etc. I am trying to configure this
under one pacemaker instance.
I changed from using Resource groups because the resources are not
dependent on each
Could it be that the user that mysql runs as (mysql??) does not have permission
to write to the folder /var/run/mysqld? Can you do the following in the system
as root and report back?
su -
touch /var/run/mysqld/test
Prakash
On Aug 9, 2011, at 6:17 PM, Michael Szilagyi wrote:
> I've recently
I've recently started taking a look at pacemaker to get some kind of HA in a
mysql test environment. The grouping has a ocf:heartbeat:IPaddr2 and a
ocf:heartbeat:mysql monitor in it. The IP monitor spins up fine and
properly jumps around the cluster depending on which node is active. I'm
having
Hi,
I do not know if this is related, but I've just seen something "similar"
on a different two-node cluster. For some reason (out of scope here)
corosync ring was broken, one cluster node was fenced, then resources
began to start on the another node (s01-0). Then I see the following:
Hi Andrew, all,
Just found little bit strange crmd behaviour - DC timed out stop
operation (which lead to node fencing) by itself, without even waiting
for lrmd (on another node) to finish that operation.
Here is what it did:
===
Aug 9 07:30:07 mgmt01 crmd: [15781]: WARN: action_time
