[Pacemaker] Change in meta clone-max result in resource restart everywhere
When updating the meta attribute clone-max all instances of the clone are terminated and immediately restarted. Following configuration (not symmetric cluster): primitive resMux_gw ocf:heartbeat:Dummy op start interval="0" timeout="10" op stop interval="0" timeout="10" op monitor interval="10" timeout="3" on-fail="restart" start-delay="10" meta failure-timeout="15m" migration-threshold="3" clone cloneMux_gw resMux_gw meta clone-max="2" target-role="Started" is-managed="true" location locMux_gwmanagement1 cloneMux_gw 1000: management1 crm resource status cloneMux_gw shows resource cloneMux_gw is running on: management1 which is correct, because there is location information only present for node management1. When clone-max is now updated by crm resource meta cloneMux_gw set clone-max 1 resMux_gw is immediately restarted on management1. I see in pacemaker log a stop call to the resource agent and after a few milliseconds a start. My question, is there any reason for stopping all instances during update of clone-max ? After update of clone-max in the above case, the same resources run on the same nodes as before. Pacemaker version is 1.1.5 Thanks, Rainer -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] ERROR: te_graph_trigger: Transition failed: terminated pacemaker's problem or mine?
On Mon, Apr 30, 2012 at 01:00:11PM +1000, Andrew Beekhof wrote: > On Sat, Apr 28, 2012 at 5:40 AM, Lars Ellenberg > wrote: > > On Fri, Apr 27, 2012 at 11:31:23AM +0100, Tim Small wrote: > >> Hi, > >> > >> I'm trying to get to the bottom of a problem I'm seeing with a cluster. > >> At this stage I'm unclear as to whether the issue is with the config or > >> not - the generated error messages seem unclear. So I'm not sure > >> whether I should be staring at the config or the source code at this > >> point, and would appreciate a clue! > >> > >> I'm running with some of the (live) resources in an unmanaged state > >> whilst testing fail-over with other (non-dependant) resources. > >> > >> The managed resources are a number of OpenVZ virtual machines (each > >> comprising 3 primitives - file-system + OpenVZ VE + SendArp). The > >> filesystems are on LVM volume groups, and the single LVM PV for each > >> volume group resides on a DRBD volume. There are n virtual machines per > >> DRBD volume. > >> > >> I'm running pacemaker 1.0.9.1+hg15626-1 on Debian 6.0. Here are some of > >> the messages (configuration follows at the end of the email): > > > > Upgrading to 1.0.12, or 1.1.7, may get you a little further. > > It would not solve the "I need to stop that resource first, but I can > > not as it is unmanaged" dependency problem you apparently have here. > > There's really not a lot the cluster can do in this situation, there's > a 50% chance of getting it wrong no matter what we do. > In the most recent versions we now log as loudly as possible > (LOG_CRIT) that we cant shutdown because something depends on an > unmanaged resource. That's in fact what I meant ;-) Not only the cryptic "ERROR: te_graph_trigger: Transition failed: terminated" but "Hey you fool, I cannot do that because you told me not to manage that resource, but the other ones depend on it". Though, you still have to spot that line in the flood... -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] CentOS pacemaker heartbeat
Hi, I´ve just installed a CentOS 6.2 and also installed via epel-repo heartbeat-3.0.4-1.el6.x86_64 and pacemaker-1.1.6-3.el6.x86_64. I try to start heartbeat (crm respawn in ha.cf) and I get this error: crmd: [2462]: CRIT: get_cluster_type: This installation of Pacemaker does not support the 'heartbeat' cluster infrastructure. Terminating. Did I missed something ? I thought heart 3x and pacemaker 1x won´t be a problem ? Any suggestions are welcome. Kind regards fatcharly -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] CentOS pacemaker heartbeat
What doe the log say? On 30/04/2012 16:37, "fatcha...@gmx.de" wrote: >Hi, > >I´ve just installed a CentOS 6.2 and also installed via epel-repo >heartbeat-3.0.4-1.el6.x86_64 and >pacemaker-1.1.6-3.el6.x86_64. >I try to start heartbeat (crm respawn in ha.cf) and I get this error: > >crmd: [2462]: CRIT: get_cluster_type: This installation of Pacemaker does >not support the 'heartbeat' cluster infrastructure. Terminating. > >Did I missed something ? I thought heart 3x and pacemaker 1x won´t be a >problem ? > >Any suggestions are welcome. > >Kind regards > >fatcharly > >-- >Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir >belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > >___ >Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >http://oss.clusterlabs.org/mailman/listinfo/pacemaker > >Project Home: http://www.clusterlabs.org >Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >Bugs: http://bugs.clusterlabs.org Bauer Corporate Services UK LP (BCS) is a division of the Bauer Media Group the largest consumer publisher in the UK, and second largest commercial radio broadcaster. BCS provides financial services and manages and develops IT systems on which our UK publishing, broadcast, digital and partner businesses depend. The information in this email is intended only for the addressee(s) named above. Access to this email by anyone else is unauthorised. If you are not the intended recipient of this message any disclosure, copying, distribution or any action taken in reliance on it is prohibited and may be unlawful. Bauer Corporate Services do not warrant that any attachments are free from viruses or other defects and accept no liability for any losses resulting from infected email transmissions. Please note that any views expressed in this email may be those of the originator and do not necessarily reflect those of this organisation. Bauer Corporate Services UK LP is registered in England; Registered address is 1 Lincoln Court, Lincoln Road, Peterborough, PE1 2RF. Registration number LP13195 ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] CentOS pacemaker heartbeat
On 04/30/2012 05:37 PM, fatcha...@gmx.de wrote: > Hi, > > I´ve just installed a CentOS 6.2 and also installed via epel-repo > heartbeat-3.0.4-1.el6.x86_64 and > pacemaker-1.1.6-3.el6.x86_64. > I try to start heartbeat (crm respawn in ha.cf) and I get this error: > > crmd: [2462]: CRIT: get_cluster_type: This installation of Pacemaker does not > support the 'heartbeat' cluster infrastructure. Terminating. > > Did I missed something ? I thought heart 3x and pacemaker 1x won´t be a > problem ? > The pacemaker version shipped with CentOS 6.2 is compiled without heartbeat support ... you don't need epel-repo to get Pacemaker, it's already included in RHEL (as technology preview). Use corosync instead of Hearbeat. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > Any suggestions are welcome. > > Kind regards > > fatcharly > signature.asc Description: OpenPGP digital signature ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] CentOS pacemaker heartbeat
+1 I'll try to get my notes up with installing and basic setup on 6.2 Sent from my iPhone On Apr 30, 2012, at 11:47 AM, "Andreas Kurz" wrote: > On 04/30/2012 05:37 PM, fatcha...@gmx.de wrote: >> Hi, >> >> I´ve just installed a CentOS 6.2 and also installed via epel-repo >> heartbeat-3.0.4-1.el6.x86_64 and >> pacemaker-1.1.6-3.el6.x86_64. >> I try to start heartbeat (crm respawn in ha.cf) and I get this error: >> >> crmd: [2462]: CRIT: get_cluster_type: This installation of Pacemaker does >> not support the 'heartbeat' cluster infrastructure. Terminating. >> >> Did I missed something ? I thought heart 3x and pacemaker 1x won´t be a >> problem ? >> > > The pacemaker version shipped with CentOS 6.2 is compiled without > heartbeat support ... you don't need epel-repo to get Pacemaker, it's > already included in RHEL (as technology preview). > > Use corosync instead of Hearbeat. > > Regards, > Andreas > > -- > Need help with Pacemaker? > http://www.hastexo.com/now > >> Any suggestions are welcome. >> >> Kind regards >> >> fatcharly >> > > > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] HAproxy resource not moving
Hey guys, I recently started testing out Pacemaker + Corosync for a clustering solution for HA proxy. My configuration is as follows crm(live)configure# show node node1.local node node2.local primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="" cidr_netmask="32" \ op monitor interval="30s" primitive test lsb:haproxy \ op monitor interval="10s" colocation haproxy-with-public-IPs inf: test ClusterIP order haproxy-after-IP inf: ClusterIP test property $id="cib-bootstrap-options" \ dc-version="1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558" \ cluster-infrastructure="openais" \ expected-quorum-votes="2" \ stonith-enabled="false" If both my nodes are up, the VIP responds as requested to the HA proxy requests.. and seems to always stick to node2. Online: [node2.local node1.local ] ClusterIP (ocf::heartbeat:IPaddr2): Started node2.local test(lsb:haproxy): Started node2.local However, if i break HA proxy on node 2 or reboot that machine, the cluster dies and doest move over to node 1 and the crm_mon displays: Online: [node1.local ] OFFLINE: [ node2.local ] Not sure what im missing here, however i would assume that both resources should move over to Node1.. Thanks in advance for any help you can provide. -- Regards, Mark Busuttil ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] HAproxy resource not moving
- Original Message - > From: "Mark Busuttil" > To: pacemaker@oss.clusterlabs.org > Sent: Monday, April 30, 2012 2:06:42 PM > Subject: [Pacemaker] HAproxy resource not moving > Hey guys, > I recently started testing out Pacemaker + Corosync for a clustering > solution for HA proxy. My configuration is as follows > crm(live)configure# show > node node1.local > node node2.local > primitive ClusterIP ocf:heartbeat:IPaddr2 \ > params ip="" cidr_netmask="32" \ > op monitor interval="30s" > primitive test lsb:haproxy \ > op monitor interval="10s" > colocation haproxy-with-public-IPs inf: test ClusterIP > order haproxy-after-IP inf: ClusterIP test > property $id="cib-bootstrap-options" \ > dc-version="1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558" \ > cluster-infrastructure="openais" \ > expected-quorum-votes="2" \ > stonith-enabled="false" Might be because you've lost quorum and the cluster has no directions without quorum... this might fix: crm configure property no-quorum-policy="ignore" HTH Jake > If both my nodes are up, the VIP responds as requested to the HA > proxy requests.. and seems to always stick to node2. > Online: [node2.local node1.local ] > ClusterIP (ocf::heartbeat:IPaddr2): Started node2.local > test (lsb:haproxy): Started node2.local > However, if i break HA proxy on node 2 or reboot that machine, the > cluster dies and doest move over to node 1 and the crm_mon displays: > Online: [node1.local ] > OFFLINE: [ node2.local ] > Not sure what im missing here, however i would assume that both > resources should move over to Node1.. > Thanks in advance for any help you can provide. -- > Regards, > Mark Busuttil > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > Project Home: http://www.clusterlabs.org > Getting started: > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] HAproxy resource not moving
Hmm unfortunately seems to be the same issue... the cluster IP seems to remain... however the ha proxy resource just goes offline and does not move.. thanks On Apr 30, 2012 8:16 PM, "Jake Smith" wrote: > > - Original Message - > > > From: "Mark Busuttil" > > To: pacemaker@oss.clusterlabs.org > > Sent: Monday, April 30, 2012 2:06:42 PM > > Subject: [Pacemaker] HAproxy resource not moving > > > Hey guys, > > > I recently started testing out Pacemaker + Corosync for a clustering > > solution for HA proxy. My configuration is as follows > > > crm(live)configure# show > > node node1.local > > node node2.local > > primitive ClusterIP ocf:heartbeat:IPaddr2 \ > > params ip="" cidr_netmask="32" \ > > op monitor interval="30s" > > primitive test lsb:haproxy \ > > op monitor interval="10s" > > colocation haproxy-with-public-IPs inf: test ClusterIP > > order haproxy-after-IP inf: ClusterIP test > > property $id="cib-bootstrap-options" \ > > dc-version="1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558" \ > > cluster-infrastructure="openais" \ > > expected-quorum-votes="2" \ > > stonith-enabled="false" > > Might be because you've lost quorum and the cluster has no directions > without quorum... this might fix: > > crm configure property no-quorum-policy="ignore" > > > HTH > > Jake > > > If both my nodes are up, the VIP responds as requested to the HA > > proxy requests.. and seems to always stick to node2. > > > Online: [node2.local node1.local ] > > > ClusterIP (ocf::heartbeat:IPaddr2): Started node2.local > > test (lsb:haproxy): Started node2.local > > > However, if i break HA proxy on node 2 or reboot that machine, the > > cluster dies and doest move over to node 1 and the crm_mon displays: > > > Online: [node1.local ] > > OFFLINE: [ node2.local ] > > > Not sure what im missing here, however i would assume that both > > resources should move over to Node1.. > > > Thanks in advance for any help you can provide. -- > > Regards, > > Mark Busuttil > > > ___ > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > Project Home: http://www.clusterlabs.org > > Getting started: > > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > Bugs: http://bugs.clusterlabs.org > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] HAproxy resource not moving
What do you mean the cluster IP remains? No errors in the logs? Is the haproxy LSB compliant? see http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ap-lsb.html Output of crm_mon -fr1? Jake - Original Message - > From: "Mark Busuttil" > To: "Jake Smith" , pacemaker@oss.clusterlabs.org > Sent: Monday, April 30, 2012 3:44:55 PM > Subject: Re: [Pacemaker] HAproxy resource not moving > Hmm unfortunately seems to be the same issue... the cluster IP seems > to remain... however the ha proxy resource just goes offline and > does not move.. thanks > On Apr 30, 2012 8:16 PM, "Jake Smith" < jsm...@argotec.com > wrote: > > - Original Message - > > > > From: "Mark Busuttil" < markb...@gmail.com > > > > > To: pacemaker@oss.clusterlabs.org > > > > Sent: Monday, April 30, 2012 2:06:42 PM > > > > Subject: [Pacemaker] HAproxy resource not moving > > > > Hey guys, > > > > I recently started testing out Pacemaker + Corosync for a > > > clustering > > > > solution for HA proxy. My configuration is as follows > > > > crm(live)configure# show > > > > node node1.local > > > > node node2.local > > > > primitive ClusterIP ocf:heartbeat:IPaddr2 \ > > > > params ip="" cidr_netmask="32" \ > > > > op monitor interval="30s" > > > > primitive test lsb:haproxy \ > > > > op monitor interval="10s" > > > > colocation haproxy-with-public-IPs inf: test ClusterIP > > > > order haproxy-after-IP inf: ClusterIP test > > > > property $id="cib-bootstrap-options" \ > > > > dc-version="1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558" > > > \ > > > > cluster-infrastructure="openais" \ > > > > expected-quorum-votes="2" \ > > > > stonith-enabled="false" > > > Might be because you've lost quorum and the cluster has no > > directions > > without quorum... this might fix: > > > crm configure property no-quorum-policy="ignore" > > > HTH > > > Jake > > > > If both my nodes are up, the VIP responds as requested to the HA > > > > proxy requests.. and seems to always stick to node2. > > > > Online: [node2.local node1.local ] > > > > ClusterIP (ocf::heartbeat:IPaddr2): Started node2.local > > > > test (lsb:haproxy): Started node2.local > > > > However, if i break HA proxy on node 2 or reboot that machine, > > > the > > > > cluster dies and doest move over to node 1 and the crm_mon > > > displays: > > > > Online: [node1.local ] > > > > OFFLINE: [ node2.local ] > > > > Not sure what im missing here, however i would assume that both > > > > resources should move over to Node1.. > > > > Thanks in advance for any help you can provide. -- > > > > Regards, > > > > Mark Busuttil > > > > ___ > > > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > > Project Home: http://www.clusterlabs.org > > > > Getting started: > > > > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > > > Bugs: http://bugs.clusterlabs.org > > > ___ > > > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > > Project Home: http://www.clusterlabs.org > > > Getting started: > > http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > > > Bugs: http://bugs.clusterlabs.org > ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] CentOS pacemaker heartbeat
http://clusterlabs.org/wiki/RHEL has some info On Tue, May 1, 2012 at 1:56 AM, Steven Bambling wrote: > +1 I'll try to get my notes up with installing and basic setup on 6.2 > > Sent from my iPhone > > On Apr 30, 2012, at 11:47 AM, "Andreas Kurz" wrote: > >> On 04/30/2012 05:37 PM, fatcha...@gmx.de wrote: >>> Hi, >>> >>> I´ve just installed a CentOS 6.2 and also installed via epel-repo >>> heartbeat-3.0.4-1.el6.x86_64 and >>> pacemaker-1.1.6-3.el6.x86_64. >>> I try to start heartbeat (crm respawn in ha.cf) and I get this error: >>> >>> crmd: [2462]: CRIT: get_cluster_type: This installation of Pacemaker does >>> not support the 'heartbeat' cluster infrastructure. Terminating. >>> >>> Did I missed something ? I thought heart 3x and pacemaker 1x won´t be a >>> problem ? >>> >> >> The pacemaker version shipped with CentOS 6.2 is compiled without >> heartbeat support ... you don't need epel-repo to get Pacemaker, it's >> already included in RHEL (as technology preview). >> >> Use corosync instead of Hearbeat. >> >> Regards, >> Andreas >> >> -- >> Need help with Pacemaker? >> http://www.hastexo.com/now >> >>> Any suggestions are welcome. >>> >>> Kind regards >>> >>> fatcharly >>> >> >> >> >> >> ___ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
