On 10/07/2015 04:46 PM, Ulrich Windl wrote:
zulucloud <[email protected]> schrieb am 07.10.2015 um 16:12 in Nachricht
<[email protected]>:
Hi,
i got a problem i don't understand, maybe someone can give me a hint.
My 2-node cluster (named ali and baba) is configured to run mysql, an IP
for mysql and the filesystem resource (on drbd master) together as a
GROUP. After doing some crash-tests i ended up having filesystem and
mysql running happily on one host (ali), and the related IP on the other
(baba) .... although, the IP's not really up and running, crm_mon just
SHOWS it as started there. In fact it's nowhere up, neither on ali nor
on baba.
Then it's most likely a bug in the resource agent. To make sure, try "crm resource
reprobe" and be patient after that for some seconds. Then recheck the displayed
status.
In the meantime i already did a "resource cleanup res_hamysql_ip". The
failcounts etc. disappeared. After that a "start gr_mysqlgroup" started
everything without a hassle on the correct node.
crm_mon shows that pacemaker tried to start it on baba, but gave up
after fail-count=1000000.
This could mean: Multiple start attempty failed, as did stop attempts, so the
cluster thinks it might be running. It looks very much like a configuration
problem to me.
Q1: why doesn't pacemaker put the IP on ali, where all the rest of it's
group lives?
See the log files in detail.
Well, they're quite verbose and a little bit cryptic...;) I didn't find
anything what could enlighten that for me...
Q2: why doesn't pacemaker try to start the IP on ali, after max
failcount had been reached on baba?
Do you have fencing enabled?
No. These are 2 virtual machines running together with some other vm's
on 2 physical VMWare servers. Could you give me a suggestion on how to
implement fencing in that situation?
thx
_______________________________________________
Users mailing list: [email protected]
http://clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
