Re: [Pacemaker] Searching for a viable Debian solution

On Sat, 24 Apr 2010, Paul Gear wrote: On 24/04/10 15:05, Quentin Smith wrote: Hi Paul, Current clvm actually supports multiple locking schemes, including both the old redhat cluster stack and modern corosync/openais. We use Ubuntu Hardy with backported corosync and clvm packages, and it works

Re: [Pacemaker] Searching for a viable Debian solution

On 24/04/10 15:05, Quentin Smith wrote: Hi Paul, Current clvm actually supports multiple locking schemes, including both the old redhat cluster stack and modern corosync/openais. We use Ubuntu Hardy with backported corosync and clvm packages, and it works pretty well. Hand-backporting is not for

Re: [Pacemaker] Searching for a viable Debian solution

Hi Paul, Current clvm actually supports multiple locking schemes, including both the old redhat cluster stack and modern corosync/openais. We use Ubuntu Hardy with backported corosync and clvm packages, and it works pretty well. Hand-backporting is not for the faint of heart, though. --Quent

[Pacemaker] Searching for a viable Debian solution

Hi folks, Over the last several days i've been reading, asking questions (special thanks to beekhof, tserong, fghass and the other kind folks on #linux-ha putting up with my questions), and experimenting with my test setup, and i'm yet to find a viable combination of options for creating a VM

Re: [Pacemaker] About influence of resouce-stickiness which used colocation for limitation.

Hi Andrew, > Fixed in: >http://hg.clusterlabs.org/pacemaker/1.1/rev/4c775a4abc87 Thanks! Best Regards, Hideo Yamauchi. --- Andrew Beekhof wrote: > Fixed in: >http://hg.clusterlabs.org/pacemaker/1.1/rev/4c775a4abc87 > > 2010/4/22 : > > Hi, > > > > We tested the cluster constitution

Re: [Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

On 2010-04-23, at 5:11 PM, Raoul Bhatia [IPAX] wrote: > On 23.04.2010 22:22, daniel qian wrote: >> I found there is a function called check_binary in >> /usr/lib/ocf/resource.d/heartbeat/IPaddr2. the error message "Couldnt fnd >> utility ip" is probably produced by this function. But I was not

[Pacemaker] logging to a certain file

Hello group I wonder how can I raise pacemaker's log level and make it log to a certain file like /var/log/pacemaker.log ? I don't want to go grep stuff from /var/log/messages. Thanks in advance :) -- All the best, Angie T. Muhammad Linux Systems Engineer Al Masry Alyoum

Re: [Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

On 23.04.2010 22:22, daniel qian wrote: I found there is a function called check_binary in /usr/lib/ocf/resource.d/heartbeat/IPaddr2. the error message "Couldnt fnd utility ip" is probably produced by this function. But I was not able to locate this function. Any one knows which file this fun

Re: [Pacemaker] Compiling Resource Agents

Thanks, Florian No longer complaining. Ryan -Original Message- From: Florian Haas [mailto:florian.h...@linbit.com] Sent: Friday, April 23, 2010 3:51 AM To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] Compiling Resource Agents On 2010-04-22 22:15, Ruiyuan Jiang wrote

Re: [Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

On 2010-04-23, at 12:13 PM, daniel qian wrote: > > On 2010-04-23, at 12:04 PM, Dejan Muhamedagic wrote: > >> Hi, >> >> On Fri, Apr 23, 2010 at 11:44:16AM -0400, daniel qian wrote: >>> We have a simple two-node cluster with apache running together with two >>> floating IPs as shown below: >>>

Re: [Pacemaker] Email notification

Paul Graydon wrote: > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/#ch-notification > > > The documentation for this section is totally blank.. is it actually > possible to get an e-mail notification send by pacemaker when things > change? > > I've got a few id

[Pacemaker] Email notification

http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/#ch-notification The documentation for this section is totally blank.. is it actually possible to get an e-mail notification send by pacemaker when things change? I've got a few ideas how I can do this from our

Re: [Pacemaker] primitive dlm ocf:pacemaker:controld --> WARNING: dlm: default-action-timeout 20s for start is smaller than the advised 90

Hello, On 04/23/2010 09:35 AM, Andrew Beekhof wrote: On Thu, Apr 22, 2010 at 12:28 AM, Roberto Giordani wrote: Thank you Andrew, I've replaced the incorrect packages installed from SLES HA cd with opensuse repository. Yeah, don't do that. Could you please describe the main step

Re: [Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

On 2010-04-23, at 12:12 PM, Michael Schwartzkopff wrote: > Am Freitag, 23. April 2010 18:04:30 schrieb Dejan Muhamedagic: >> Hi, >> >> On Fri, Apr 23, 2010 at 11:44:16AM -0400, daniel qian wrote: >>> We have a simple two-node cluster with apache running together with two >>> floating IPs as show

Re: [Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

On 2010-04-23, at 12:04 PM, Dejan Muhamedagic wrote: > Hi, > > On Fri, Apr 23, 2010 at 11:44:16AM -0400, daniel qian wrote: >> We have a simple two-node cluster with apache running together with two >> floating IPs as shown below: >> >> node gamma >> node sql >> primitive ClusterIP ocf:heartbe

Re: [Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

Am Freitag, 23. April 2010 18:04:30 schrieb Dejan Muhamedagic: > Hi, > > On Fri, Apr 23, 2010 at 11:44:16AM -0400, daniel qian wrote: > > We have a simple two-node cluster with apache running together with two > > floating IPs as shown below: > > > > node gamma > > node sql > > primitive ClusterIP

Re: [Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

Hi, On Fri, Apr 23, 2010 at 11:44:16AM -0400, daniel qian wrote: > We have a simple two-node cluster with apache running together with two > floating IPs as shown below: > > node gamma > node sql > primitive ClusterIP ocf:heartbeat:IPaddr2 \ > params ip="x.x.x.x" cidr_netmask="32" \ >

[Pacemaker] Is it possible for ocf:heartbeat:IPaddr2 to be on different NICs?

We have a simple two-node cluster with apache running together with two floating IPs as shown below: node gamma node sql primitive ClusterIP ocf:heartbeat:IPaddr2 \ params ip="x.x.x.x" cidr_netmask="32" \ op monitor interval="30s" \ meta target-role="Started" primitive apa

Re: [Pacemaker] About influence of resouce-stickiness which used colocation for limitation.

Fixed in: http://hg.clusterlabs.org/pacemaker/1.1/rev/4c775a4abc87 2010/4/22 : > Hi, > > We tested the cluster constitution of four nodes. > > srv04 is a standby node, and others are active nodes. > > We use INIFINITY for resouce-stickiness well. > > But, there was a problem for resource place

Re: [Pacemaker] Failover after fail on Ethernet Fails (unSolved again)

On Wed, Apr 21, 2010 at 9:41 AM, Stefan Kelemen wrote: > So i madde a complete hb_report (attachment) over ten minutes in that i made > a deconnect of the ethernet without failover and a reconnect. Could you reproduce with "debug 1" in ha.cf please? There's not enough detail in the lrmd logs to

Re: [Pacemaker] long time to start

On Wed, Apr 21, 2010 at 5:07 PM, Schaefer, Diane E wrote: >>> Hi, > Yes, I am saying that if a resource (R1) is taking a long time to start and > another resource (R2) monitor action returns a not running, it will not be > restarted until the first stuck resource returns or in my case times out. >

Re: [Pacemaker] Compiling Resource Agents

On 2010-04-22 22:15, Ruiyuan Jiang wrote: > /usr/bin/xsltproc \ > --xinclude \ > > http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl > ocf_heartbeat_eDir88.xml > Writing ocf_heartbeat_eDir88.7 for refentry(re-ra-eDir88) > OCF_ROOT=. OCF_FUNCTIONS_DIR=../heart

Re: [Pacemaker] primitive dlm ocf:pacemaker:controld --> WARNING: dlm: default-action-timeout 20s for start is smaller than the advised 90

On Thu, Apr 22, 2010 at 12:28 AM, Roberto Giordani wrote: > Thank you Andrew, > I've replaced the incorrect packages installed from SLES HA cd with opensuse > repository. Yeah, don't do that. > Could you please describe the main steps to upgrade pacemaker from 1.02 to > 1.08 and openais 0.8 to c