Re: [Pacemaker] Pacemaker failover problem

2010-03-23 Thread Andrew Beekhof
On Tue, Mar 9, 2010 at 4:04 PM, Erich Weiler wrote: > Thanks for the reply!  Yes, I have checked that my LSB scripts are > compliant. I'm pretty sure it fails step 3 of http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ap-lsb.html > If this can provide any insight,

Re: [Pacemaker] Pacemaker failover problem

2010-03-09 Thread Erich Weiler
Thanks for the reply! Yes, I have checked that my LSB scripts are compliant. If this can provide any insight, here is a clip from /var/log/messsages on genome-ldap2 when genome-ldap1 goes down (when the order constraint is in place): Mar 9 06:59:22 genome-ldap2 crmd: [2038]: info: handle_s

Re: [Pacemaker] Pacemaker failover problem

2010-03-08 Thread Andrew Beekhof
On Tue, Mar 9, 2010 at 12:27 AM, Erich Weiler wrote: > I think I may have found an answer.  I had this in my config: > > order LDAP-after-IP inf: LDAP-IP LDAP-clone > > And, according to the logs, it *looks* like what happens when genome-ldap1 > goes gown, the IP goes over to genome-ldap2, AND THE

Re: [Pacemaker] Pacemaker failover problem

2010-03-08 Thread Erich Weiler
I think I may have found an answer. I had this in my config: order LDAP-after-IP inf: LDAP-IP LDAP-clone And, according to the logs, it *looks* like what happens when genome-ldap1 goes gown, the IP goes over to genome-ldap2, AND THEN tries to start LDAP there, even though LDAP is already star

Re: [Pacemaker] Pacemaker failover problem

2010-03-08 Thread Erich Weiler
I tried that (after setting 'property symmetric-cluster="true"'), didn't seem to make a difference... Thanks for the suggestion though! hj lee wrote: I don't think it's a good idea to put location on clone. The clone is designed to run equally on every node. Please remove these and see that h

Re: [Pacemaker] Pacemaker failover problem

2010-03-08 Thread hj lee
I don't think it's a good idea to put location on clone. The clone is designed to run equally on every node. Please remove these and see that helps. location LDAP-IP-placement-2 LDAP-IP 50: genome-ldap2 location LDAP-placement-1 LDAP-clone 100: genome-ldap1 location LDAP-placement-2 LDAP-clone 100

[Pacemaker] Pacemaker failover problem

2010-03-08 Thread Erich Weiler
Hi All, I have a (hopefully) simple problem that I need to fix, but I feel like I'm missing a key concept here that is causing problems. I have 2 nodes, genome-ldap1 and genome-ldap2. Using latest corosync, pacemaker and openais from the epel and clusterlabs repos, CentOS 5.4. Both nodes a