Greg Woods wo...@ucar.edu schrieb am 24.04.2013 um 18:27 in Nachricht
1366820838.16523.112.ca...@anathem.gregandeva.net:
On Wed, 2013-04-24 at 08:48 +0200, Ulrich Windl wrote:
Greg Woods wo...@ucar.edu schrieb am 23.04.2013 um 21:20 in Nachricht
Apr 19 17:02:22 vmn2 kernel: block drbd0:
On Wed, Apr 24, 2013 at 10:27:18AM -0600, Greg Woods wrote:
On Wed, 2013-04-24 at 08:48 +0200, Ulrich Windl wrote:
Greg Woods wo...@ucar.edu schrieb am 23.04.2013 um 21:20 in Nachricht
Apr 19 17:02:22 vmn2 kernel: block drbd0: Terminating asender thread
Apr 19 17:02:22 vmn2 kernel:
Hi Alain,
could you doublecheck, if the effect in your second test also happens, when you
set a stickness/default-stickyness tobe something like 1000?
In your case when NOT setting default stickyness a running resource does not
get a higher score than a stopped one, which is requested to be
Hi All,
We encountered an issue when starting/stopping lsb resources (crm resource
start test_agent_clone) in our 3 node cluster setup as per the log extract
below.
There is no issue starting the service manually i.e.. service testservice
start/stop and also ran compatibility check on the
Hi Alan,
On Fri, Apr 19, 2013 at 03:01:51PM -0600, Alan Robertson wrote:
Hi all,
This announcement is likely to be of interest to people like you who are
concerned about availability.
I founded the Linux-HA project in 1998 and led it for nearly 10 years.
Back in about November 2010, I
We are installing corosync and pacemaker on a brand new RHEL 6.3 cluster today.
When we installed using yum, here are the versions that pulled down from the
repos.
pacemaker-libs-1.1.9-1512.el6.x86_64
pacemaker-1.1.9-1512.el6.x86_64
corosync-1.4.3-26.2.x86_64
On 26/04/2013, at 8:08 AM, Robinson, Eric eric.robin...@psmnv.com wrote:
We are installing corosync and pacemaker on a brand new RHEL 6.3 cluster
today. When we installed using yum, here are the versions that pulled down
from the repos.
pacemaker-libs-1.1.9-1512.el6.x86_64
On 25/04/2013, at 6:52 PM, fabian.herschel fabian.hersc...@arcor.de wrote:
So, this seems to mean that the order of the resources for a -inf:
collocation is important and has an impact on the behavior.
Absolutely.
I wonder if it is a normal behavior ? and so we have to really take in
I have followed up on the equivalent pacemaker mailing list thread.
Essentially I asked if the latest http://www.clusterlabs.org/rpm-next packages
helped and if someone could open up the core file and print the contents of
the input passed to string2xml()
On 26/04/2013, at 2:00 AM, Jimmy
On 24/04/2013, at 8:49 PM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
Hi!
I remember a complaint from my side that colocation should be symmetrical.
Unfortunately many things are much easier to ask for than to implement.
I
guess you'll find the responses via Google. Maybe the
10 matches
Mail list logo
