Re: [Pacemaker] problem about move node from one clusterto another cluster

2010-10-11 Thread jiaju liu
Message: 2 Date: Tue, 12 Oct 2010 10:40:18 +0800 (CST) From: jiaju liu To: pacemaker@oss.clusterlabs.org Subject: [Pacemaker] problem about move node from one cluster to     another    cluster Message-ID: <765547.4759...@web15704.mail.cnb.yahoo.com> Content-Type: text/plain; charset="iso-8859-1

Re: [Pacemaker] [Problem]The monitor that start-delay is long does not stop.

2010-10-11 Thread renayama19661014
Hi Andrew, > > Funnily enough I was just looking at that message and saw that the > > code relevant to this one looked wrong too. > > > > I believe this should fix the issue: > >http://hg.clusterlabs.org/pacemaker/1.1/rev/e06810256413 > > > > > > > > I registered log and more with Bugzilla.

Re: [Pacemaker] stonith pacemaker problem

2010-10-11 Thread Andrew Beekhof
On Mon, Oct 11, 2010 at 9:51 PM, Vladislav Bogdanov wrote: > 11.10.2010 09:14, Andrew Beekhof wrote: >> strictly speaking you don't. >> but at least on fedora, the policy is that $x-libs always requires $x >> so just building against heartbeat-libs means that yum will suck in >> the main heartbeat

[Pacemaker] problem about move node from one cluster to another cluster

2010-10-11 Thread jiaju liu
hi everybody I use command service openais stop first to stop openais service and then use rm -rf /var/lib/heartbear/crm/*  clear all information. then change multicast address and  service openais start in another cluster. the problem is sometimes it works I can use crm_mon command. a

[Pacemaker] problem about move node from one cluster to another cluster

2010-10-11 Thread jiaju liu
hi everybody I use command crm openais stop first to stop openais service and then use rm -rf /var/lib/heartbear/crm/*  clear all information. then change multicast and start it in another cluster. the problem is sometimes it works I can use crm_mon command. and sometimes it doesn't work. I use

Re: [Pacemaker] stonith pacemaker problem

2010-10-11 Thread Vladislav Bogdanov
11.10.2010 09:14, Andrew Beekhof wrote: > strictly speaking you don't. > but at least on fedora, the policy is that $x-libs always requires $x > so just building against heartbeat-libs means that yum will suck in > the main heartbeat package :-( And this seem to be a bit incorrect statement btw: u

Re: [Pacemaker] stonith pacemaker problem

2010-10-11 Thread Vadym Chepkov
On Oct 11, 2010, at 2:14 AM, Andrew Beekhof wrote: > On Sun, Oct 10, 2010 at 11:20 PM, Shravan Mishra > wrote: >> Andrew, >> >> We were able to solve our problem. Obviously if no one else is having >> it then it has to be our environment. It's just that time pressure and >> mgmt pressure was ca

Re: [Pacemaker] resource is stuck

2010-10-11 Thread Pavlos Parissis
On 11 October 2010 11:12, Pavlos Parissis wrote: > Hi, > > Cluster got an error on monitor and stop action on a resource and > since then I can't do stop/start/manage/unmanage that resource. > For some strange reason the actions monitor/stop failed, manually > worked, but i can't figure out why th

Re: [Pacemaker] Migrate resources based on connectivity

2010-10-11 Thread Lars Ellenberg
On Mon, Oct 11, 2010 at 03:50:01PM +0300, Dan Frincu wrote: > Hi, > > Dejan Muhamedagic wrote: > >Hi, > > > >On Sun, Oct 10, 2010 at 10:27:13PM +0300, Dan Frincu wrote: > >>Hi, > >> > >>I have the following setup: > >>- order drbd0:promote drbd1:promote > >>- order drbd1:promote drbd2:promote > >>

Re: [Pacemaker] Migrate resources based on connectivity

2010-10-11 Thread Dan Frincu
Hi, Dejan Muhamedagic wrote: Hi, On Sun, Oct 10, 2010 at 10:27:13PM +0300, Dan Frincu wrote: Hi, I have the following setup: - order drbd0:promote drbd1:promote - order drbd1:promote drbd2:promote - order drbd2:promote all:start - collocation all drbd2:Master - all is a group of resources,

Re: [Pacemaker] Migrate resources based on connectivity

2010-10-11 Thread Dejan Muhamedagic
Hi, On Sun, Oct 10, 2010 at 10:27:13PM +0300, Dan Frincu wrote: > Hi, > > I have the following setup: > - order drbd0:promote drbd1:promote > - order drbd1:promote drbd2:promote > - order drbd2:promote all:start > - collocation all drbd2:Master > - all is a group of resources, drbd{0..3} are drbd

Re: [Pacemaker] unpack_rsc_op: Hard error

2010-10-11 Thread Pavlos Parissis
On 10 October 2010 17:39, Andrew Beekhof wrote: > On Sat, Oct 9, 2010 at 11:20 PM, Pavlos Parissis > wrote: >> Hi, >> >> Does anyone know why PE wants to unpack resources on nodes that will >> never run due to location constraints? > > Because part of its job is to make sure they dont run there.

Re: [Pacemaker] crmd thinks lsb returns error on monito

2010-10-11 Thread Pavlos Parissis
On 10 October 2010 17:40, Andrew Beekhof wrote: > On Sun, Oct 10, 2010 at 12:47 AM, Pavlos Parissis > wrote: >> Hi, >> >> My resource is not started because I get this >> >> 00:44:27 crmd: [3141]: WARN: status_from_rc: Action 16 >> (pbx_02_monitor_0) on node-02 failed (target: 7 vs. rc: 5): Error

Re: [Pacemaker] crm resource move doesn't move the resource

2010-10-11 Thread Pavlos Parissis
On 8 October 2010 09:29, Andrew Beekhof wrote: > On Fri, Oct 8, 2010 at 8:34 AM, Pavlos Parissis > wrote: >> On 8 October 2010 08:29, Andrew Beekhof wrote: >>> On Thu, Oct 7, 2010 at 9:58 PM, Pavlos Parissis >>> wrote: On 7 October 2010 09:01, Andrew Beekhof wrote: > > O

Re: [Pacemaker] Infinite fail-count and migration-threshold after node fail-back

2010-10-11 Thread Dan Frincu
Hi all, I've managed to make this setup work, basically the issue with a symmetric-cluster="false" and specifying the resources' location manually means that the resources will always obey the location constraint, and (as far as I could see) disregard the rsc_defaults resource-stickiness valu