[Pacemaker] parse error in config: The consensus timeout parameter (1200 ms) must be atleast 1.2 * token (1200 ms)

I am using Corosync 1.2.0 that comes with Fedora 12 and have this error when trying to start corosync service. If I set it to anything above 1200 the error goes away. Is this a bug or something intended for? Thanks, Daniel ___ Pacemaker mailing li

[Pacemaker] [PATCH] Small fixes to the controld RA

Hi, This patch contains two small fixes. One is to remove the configuration option for SCTP protocol. The reason is before dlm_controld.pcmk starts up, the directory /sys/kernel/config/dlm/cluster/protocol doesn't exist, so the original code can't work as expected. Also, as dlm_controld.pcmk for

Re: [Pacemaker] Migrate/run resource only if m/s resource is master/promoted on target node

Hi, On Mon, Dec 28, 2009 at 03:45:28PM +0100, Martin Gombač wrote: > > Michael Schwartzkopff wrote: >> Am Montag, 28. Dezember 2009 15:30:05 schrieb Martin Gombač: >> >>> Michael Schwartzkopff wrote: >>> Am Montag, 28. Dezember 2009 14:36:11 schrieb Martin Gombač: > Hi

Re: [Pacemaker] Migrate/run resource only if m/s resource is master/promoted on target node

Am Montag, 28. Dezember 2009 15:45:28 schrieb Martin Gombač: > Michael Schwartzkopff wrote: > > Am Montag, 28. Dezember 2009 15:30:05 schrieb Martin Gombač: > >> Michael Schwartzkopff wrote: > >>> Am Montag, 28. Dezember 2009 14:36:11 schrieb Martin Gombač: > Hi, > > i have mostly wo

Re: [Pacemaker] Migrate/run resource only if m/s resource is master/promoted on target node

Michael Schwartzkopff wrote: Am Montag, 28. Dezember 2009 15:30:05 schrieb Martin Gombač: Michael Schwartzkopff wrote: Am Montag, 28. Dezember 2009 14:36:11 schrieb Martin Gombač: Hi, i have mostly working Xen + DRBD + Live migration + Resource fencing, but here is a slight is

Re: [Pacemaker] Migrate/run resource only if m/s resource i s master/promoted on target node

Am Montag, 28. Dezember 2009 15:30:05 schrieb Martin Gombač: > Michael Schwartzkopff wrote: > > Am Montag, 28. Dezember 2009 14:36:11 schrieb Martin Gombač: > >> Hi, > >> > >> i have mostly working Xen + DRBD + Live migration + Resource fencing, > >> but here is a slight issue with my crm config. >

Re: [Pacemaker] Migrate/run resource only if m/s resource is master/promoted on target node

Michael Schwartzkopff wrote: Am Montag, 28. Dezember 2009 14:36:11 schrieb Martin Gombač: Hi, i have mostly working Xen + DRBD + Live migration + Resource fencing, but here is a slight issue with my crm config. I want for resource Hosting to migrate to other node only when the drbd resource

Re: [Pacemaker] Migrate/run resource only if m/s resource is master/promoted on target node

Am Montag, 28. Dezember 2009 14:36:11 schrieb Martin Gombač: > Hi, > > i have mostly working Xen + DRBD + Live migration + Resource fencing, > but here is a slight issue with my crm config. > > I want for resource Hosting to migrate to other node only when the drbd > resource there is primary. I di

[Pacemaker] Migrate/run resource only if m/s resource is master/promoted on target node

Hi, i have mostly working Xen + DRBD + Live migration + Resource fencing, but here is a slight issue with my crm config. I want for resource Hosting to migrate to other node only when the drbd resource there is primary. I did try to achieve this using ordering (see config below). Currently i

Re: [Pacemaker] What is the best way to find out master node?

Hi, On Wed, Dec 23, 2009 at 10:19:00AM -0700, hj lee wrote: > Hi, > > I have two-node cluster with a simple multi-state clone. I am using "crm_mon > -1 | grep Masters: | awk '{print $3}' " to find out which node is a master. > Is there a better way doing this? I don't like relying on the output o

Re: [Pacemaker] corosync init script broken

Dejan, thanks for your quick answer. > There has been recently an update to the corosync init script. I > think that it was actually written from scratch. It should be > included in release 1.2.0. Do you have that version? # rpm -qa|grep coro libcorosync-1.1.2-1 corosync-1.1.2-1 That's what cam

Re: [Pacemaker] corosync init script broken

Am Montag, 28. Dezember 2009 13:22:34 schrieb Dominik Klein: > Hi cluster people > > been a while, couldn't really follow things. Today I was tasked to > install a new cluster, went for 1.0.6 and corosync as described on the > wiki and hit this: > > New cluster with pacemaker 106 and latest availab

Re: [Pacemaker] pacemaker with corosync does not support communication via Serial Devic ?

Hi, On Mon, Dec 28, 2009 at 01:29:02PM +0100, Raoul Bhatia [IPAX] wrote: > On 12/28/2009 01:21 PM, Michael Schwartzkopff wrote: > > I don't think this is possible because the amount of data are too high for > > a > > serial link of max 56 kbaud. > > i always thought that serial connections can

Re: [Pacemaker] pacemaker with corosync does not support communication via Serial Devic ?

On 12/28/2009 01:21 PM, Michael Schwartzkopff wrote: > I don't think this is possible because the amount of data are too high for a > serial link of max 56 kbaud. i always thought that serial connections can handle 115.2k or even more? see http://tldp.org/HOWTO/Serial-HOWTO-13.html cheers, raoul

Re: [Pacemaker] corosync init script broken

Hi Dominik, On Mon, Dec 28, 2009 at 01:22:34PM +0100, Dominik Klein wrote: > Hi cluster people > > been a while, couldn't really follow things. Today I was tasked to > install a new cluster, went for 1.0.6 and corosync as described on the > wiki and hit this: > > New cluster with pacemaker 106 a

[Pacemaker] corosync init script broken

Hi cluster people been a while, couldn't really follow things. Today I was tasked to install a new cluster, went for 1.0.6 and corosync as described on the wiki and hit this: New cluster with pacemaker 106 and latest available corosync from the clusterlabs.org/rpm opensuse 11.1 repo. This instal

Re: [Pacemaker] pacemaker with corosync does not suppo rt communication via Serial Devic ?

Am Montag, 28. Dezember 2009 12:59:05 schrieb Dejan Muhamedagic: > Hi, > > On Fri, Dec 25, 2009 at 04:24:10PM +0800, xin.li...@cs2c.com.cn wrote: > > hi,all:    Can pacemaker with corosync support > > communication via Serial device ? I know > > heartbeat can do this.    Will this pattern be in

Re: [Pacemaker] 1.0.5 to 1.0.6 update on Fedora

Hi, On Sat, Dec 26, 2009 at 01:22:31PM -0500, E-Blokos wrote: > Hello, > > is it risky to update from 1.0.5 Fedora 10 to 1.0.6 Fedora 12 ? > since my system works well I hesitate to update There shouldn't be any risks, apart from the usual ;-) Any software upgrade can go wrong. Best to have

Re: [Pacemaker] Help with Pacemaker 2-node Router Setup

Hi, On Sun, Dec 27, 2009 at 01:33:05AM -0500, Eric Renfro wrote: > Eric Renfro wrote: [...] > Aha! > The problem is in the Route script itself somewhere. In doing the > same tests you exampled earlier, the very first monitor attempt on > Route, while the net0 interface is empty and offline, I get

Re: [Pacemaker] pacemaker with corosync does not support communication via Serial Devic ?

Hi, On Fri, Dec 25, 2009 at 04:24:10PM +0800, xin.li...@cs2c.com.cn wrote: > hi,all:    Can pacemaker with corosync support > communication via Serial device ? I know > heartbeat can do this.    Will this pattern be in the > corosync's road map?    Or, does corosync have plan for > some none-i

Re: [Pacemaker] coroync not able to exec services properly

Hi, On Thu, Dec 24, 2009 at 02:35:01PM -0500, Shravan Mishra wrote: > Hi Guys, > > I had a perfectly running system for about 3 weeks now but now on reboot I > see problems. > > Looks like the processes are being spawned and respawned but a proper exec > is not happening. According to the logs,

Re: [Pacemaker] Too many open files

Hi, On Thu, Dec 24, 2009 at 02:59:13PM +0500, vita...@mail.ru wrote: > > Hi all! > > When create any resource, i have: > > Dec 24 12:28:44 cluster1-node1 lrmd: [25907]: info: RA output: > (Public-IP:monitor:stderr) .: 44: 3: Too many open files > Dec 24 12:28:44 cluster1-node1 lrmd: [25907]: W