On Sun, Oct 10, 2010 at 11:20 PM, Shravan Mishra
shravan.mis...@gmail.com 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 causing us to go really bonkers.
We had
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
On 8 October 2010 09:29, Andrew Beekhof and...@beekhof.net wrote:
On Fri, Oct 8, 2010 at 8:34 AM, Pavlos Parissis
pavlos.paris...@gmail.com wrote:
On 8 October 2010 08:29, Andrew Beekhof and...@beekhof.net wrote:
On Thu, Oct 7, 2010 at 9:58 PM, Pavlos Parissis
pavlos.paris...@gmail.com wrote:
On 10 October 2010 17:40, Andrew Beekhof and...@beekhof.net wrote:
On Sun, Oct 10, 2010 at 12:47 AM, Pavlos Parissis
pavlos.paris...@gmail.com 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
On 10 October 2010 17:39, Andrew Beekhof and...@beekhof.net wrote:
On Sat, Oct 9, 2010 at 11:20 PM, Pavlos Parissis
pavlos.paris...@gmail.com 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
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 ms
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
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
- order drbd2:promote
On 11 October 2010 11:12, Pavlos Parissis pavlos.paris...@gmail.com 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
On Oct 11, 2010, at 2:14 AM, Andrew Beekhof wrote:
On Sun, Oct 10, 2010 at 11:20 PM, Shravan Mishra
shravan.mis...@gmail.com 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
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:
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
On Mon, Oct 11, 2010 at 9:51 PM, Vladislav Bogdanov
bub...@hoster-ok.com 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
13 matches
Mail list logo
