Hi,
On 09/15/10 03:36, Luana C. Rocha wrote:
> *I'm also having problems to start heartbeat:*
>
> r...@squid01:/home/luana/Pacemaker-Python-GUI-pacemaker-mgmt-2.0.0#
> /etc/init.d/heartbeat start
> Starting High-Availability services: Heartbeat failure [rc=6]. Failed.
> heartbeat[7735]: 2010/09
Hi Andrew,
> Perfect. Pushed. Thanks!
>
>http://hg.clusterlabs.org/pacemaker/1.1/rev/d932da0b886b
Thanks!!
Hideo Yamauchi.
--- Andrew Beekhof wrote:
> Perfect. Pushed. Thanks!
>
>http://hg.clusterlabs.org/pacemaker/1.1/rev/d932da0b886b
>
> 2010/9/14 :
> > Hi Andrew,
> >
> > Thank
Perfect. Pushed. Thanks!
http://hg.clusterlabs.org/pacemaker/1.1/rev/d932da0b886b
2010/9/14 :
> Hi Andrew,
>
> Thank you for comment.
>
>> Thanks for the explanation, I think you're right that we shouldn't be
>> showing these failed actions.
>> I think we want to do it in the PE though, eg. s
*I'm also having problems to start heartbeat:*
r...@squid01:/home/luana/Pacemaker-Python-GUI-pacemaker-mgmt-2.0.0#
/etc/init.d/heartbeat start
Starting High-Availability services: Heartbeat failure [rc=6]. Failed.
heartbeat[7735]: 2010/09/14_16:14:18 ERROR: Client child command
[/usr/lib/hea
This patch is far too invasive to consider including.
On Tue, Sep 14, 2010 at 12:12 PM, Florian Haas wrote:
> # HG changeset patch
> # User Florian Haas
> # Date 1283778895 -7200
> # Branch stable-1.0
> # Node ID 4341d047ac9d29f7125f58e5957ac58b60771a5e
> # Parent 878dfd58396ca7e2de2999ffe52583
On Mon, Sep 13, 2010 at 5:40 PM, Vladislav Bogdanov
wrote:
> Hi Andrew, hi all,
>
> Upgraded to todays tip and see bunch of assertion messages in logs
> (together with some segfaults from pengine).
tip? From the 1.1 repo?
>
> Here is what I see:
>
> Sep 13 16:53:43 s01-1 pengine: [4120]: ERROR:
On Tue, Sep 14, 2010 at 1:51 PM, Alisson Landim wrote:
>> Odd, thats what I did for the clusters from scratch doc and it all worked
>> fine.
>
> You did the "beginning" for the Fedora 13.
>
> As we can see beginning at section 6, here:
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clus
Hi There,
I have setup a pair of primary/secondary servers for services such as web, ftp,
samba and nfs with pacemaker 1.1.1, drdb-pacemaker 8.3.7, corosync 1.2.7 on
Fedora 13. Things work well except for an old Solaris 2.7 client. The Solaris
system can't mount to the nfs server because it can
> Odd, thats what I did for the clusters from scratch doc and it all
worked fine.
You did the "beginning" for the Fedora 13.
As we can see beginning at section 6, here:
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch06.html
your guide is from Fedora 12. Just lo
Hi Andrew,
> I'd probably summarize it as:
> "resources are frozen to their current _partition_"
>
> They can only move around within their partition. So if the partition
> does not have quorum and
> * a node shuts down, the partition can reallocate any services on
> that node, but
> * a node
2010/9/14 :
> Hi Andrew,
>
> Thank you for comment.
>
> As a conclusion in case of the freeze setting
>
> * At the divided point in time, the resource maintains it.
> * When a node shuts it down, in divided constitution, the resource does
> migrate.
> -> Maintaining a resource in divided
# HG changeset patch
# User Florian Haas
# Date 1283778895 -7200
# Branch stable-1.0
# Node ID 4341d047ac9d29f7125f58e5957ac58b60771a5e
# Parent 878dfd58396ca7e2de2999ffe52583e24e425594
xml: allow upstart primitives in resources.rng
Since cluster-glue has added support for upstart resources, all
12 matches
Mail list logo
