Hi Dejan,
Thank you for reviewing it.
Commited the revised patch by Yamauchi-san (tomcat.patch-0225) as:
http://hg.linux-ha.org/dev/rev/6cbdca48bf88
Thanks,
Dejan Muhamedagic deja...@fastmail.fm writes:
Hi,
On Tue, Feb 24, 2009 at 12:20:22PM +0900, Keisuke MORI wrote:
Hi,
Will anybody
Hi,
I'm currently running Pacemaker 0.6.5 and I'm preparing an upgrade
toward 1.0-tip (currently 0de73ec89e02) with packages I compiled myself
on debian lenny amd64.
To check everything works before applying the upgrade on my production
environment, I created two VMs and (partly) replicated my
/etc/init.d/nfsserver works fine for stopping starting.
look like issue is that heartbeat is detecting that this is running on more
then one node. I can I restrict that to start only on one node and go to second
if it fails
Feb 25 11:08:49 hos002a nfsserver[14037]: [14073]: ERROR: IT FAILED
Hello,
I'm running heartbeat version 1.2.5 and drbd 8.3.0. I noticed a
strange behaviour. First, when the preferred-primary node comes up (in
a 2 nodes active/passive configuration), heartbeat starts shared
ressources immediately (even if initdead is set) while drbd is still
syncing.
On Wed, Feb 25, 2009 at 06:52:34PM +0100, Vianney Lejeune wrote:
Hello,
I'm running heartbeat version 1.2.5 and drbd 8.3.0. I noticed a
strange behaviour. First, when the preferred-primary node comes up (in
a 2 nodes active/passive configuration), heartbeat starts shared
See the following page for submitting bug
http://clusterlabs.org/wiki/Help:Contents
Be sure to include the backtrace
On Wed, Feb 25, 2009 at 18:03, Brice Figureau brice...@daysofwonder.com wrote:
Hi,
I'm currently running Pacemaker 0.6.5 and I'm preparing an upgrade
toward 1.0-tip
Hello,
I'm running heartbeat version 1.2.5 and drbd 8.3.0. I noticed a
strange behaviour. First, when the preferred-primary node comes up
(in
a 2 nodes active/passive configuration), heartbeat starts shared
ressources immediately (even if initdead is set) while drbd is still
On Wed, Feb 25, 2009 at 07:47:39PM +0100, Vianney Lejeune wrote:
I can assure you the daemons fail to start. Maybe my problem is only
related to the time to mount the drbd disk ?
Which daemons?
Usually DRBD's init script waits for it to be connected before
continuing and heartbeat starts
Check the heartbeat logs, though -- it should tell you exactly why it
failed. Set debugfile /var/log/ha-debug in /etc/ha.d/ha.cf and look
through that log while/after it tries to start.
In fact the node which is going to release the shared-ressources locks
the drbd ressource, which leads to
I found the site as soon as I sent it out.
http://clusterlabs.org/wiki/DRBD_HowTo_1.0
'Hope this helps others. :)
Regards,
Jerome
From: Jerome Yanga
Sent: Wednesday, February 25, 2009 2:40 PM
To: General Linux-HA mailing list
Subject: [Linux-HA] Call cib_create failed (-47): Update does not
I have been trying to add DRBD on my Pacemaker config using crm(live) but I
keep getting this message below:
Call cib_create failed (-47): Update does not conform to the configured
schema/DTD
Can someone show me the syntax for crm(live) to add my DRBD resource below?
master_slave
Hi all
I have a wee puzzle for you.
I have a 2 node cluster running DRBD to share out a volume that is used for
hosting a SAMBA share (Using ADS to query AD for account information), both
nodes of the cluster have been joined to AD and are testing fine (able to
add AD accounts to the share /
12 matches
Mail list logo
