Re: [Pacemaker] CentOS pacemaker heartbeat

2012-04-30 Thread Andrew Beekhof
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

Re: [Pacemaker] HAproxy resource not moving

2012-04-30 Thread Jake Smith
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

Re: [Pacemaker] HAproxy resource not moving

2012-04-30 Thread Mark Busuttil
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

Re: [Pacemaker] HAproxy resource not moving

2012-04-30 Thread Jake Smith
- 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

[Pacemaker] HAproxy resource not moving

2012-04-30 Thread Mark Busuttil
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 m

Re: [Pacemaker] CentOS pacemaker heartbeat

2012-04-30 Thread Steven Bambling
+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.el

Re: [Pacemaker] CentOS pacemaker heartbeat

2012-04-30 Thread Andreas Kurz
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_clus

Re: [Pacemaker] CentOS pacemaker heartbeat

2012-04-30 Thread Bensch, Kobus
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]:

[Pacemaker] CentOS pacemaker heartbeat

2012-04-30 Thread fatcharly
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 '

Re: [Pacemaker] ERROR: te_graph_trigger: Transition failed: terminated pacemaker's problem or mine?

2012-04-30 Thread Lars Ellenberg
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'

[Pacemaker] Change in meta clone-max result in resource restart everywhere

2012-04-30 Thread Rainer Brestan
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" t