El 08/02/10 16:04, Andrew Beekhof escribió:
> [snip]
>> checking for ll_cluster_new in -lhbclient... no
>>
> looks like you dont have the heartbeat development libs/headers installed
>
This is the log in the machine that compilation is working:
configure: Using installed ltdl
checking bzli
Greetings All,
This is to announce version 0.2.0 of Hawk, a web-based GUI for
Pacemaker HA clusters. The major item of note for this version
is that we now have reasonable feature parity with crm_mon, and
there are SLES/openSUSE packages available from the openSUSE
Build Service:
http://software
On Mon, 2010-02-08 at 20:48 +0100, Sander van Vugt wrote:
> Hi,
>
> After it has been working for a while, the cluster I've installed to
> create a Xen HA solution, dropped dead on the floor a few days ago. I
> completely stripped it, deciding to build it up from scratch (based on
> the xml files
On Mon, Feb 8, 2010 at 4:59 PM, jimbob palmer wrote:
> 2010/2/8 Andrew Beekhof :
>> On Mon, Feb 8, 2010 at 4:36 PM, jimbob palmer wrote:
>> I've searched the mailing lists for qdisk, quorum disk and quorum
>> partition but found nothing.
>>
>> How can I configure a two node cluste
Hi,
On Fri, Feb 05, 2010 at 06:33:25PM -0600, D. J. Draper wrote:
>
> I haven't been able to find any documentation outside of the man pages to
> help troubleshoot this, so I've come to the experts...
>
> I'm attempting to setup the following:
>
> Services: NFS and Samba
>
Hi
Today Ubuntu removed libuuid.la from uuid-dev package. That's a result
of merge from Debian and Debian's policy
http://wiki.debian.org/ReleaseGoals/LAFileRemoval, so this problem might
affect Debian and other distributions.
make trows error after libtool commits suicide:
libtool: link: r
2010/2/8 Andrew Beekhof :
> On Mon, Feb 8, 2010 at 4:36 PM, jimbob palmer wrote:
> I've searched the mailing lists for qdisk, quorum disk and quorum
> partition but found nothing.
>
> How can I configure a two node cluster to use
a quorum disk so that the node that can se
On Mon, Feb 8, 2010 at 4:36 PM, jimbob palmer wrote:
I've searched the mailing lists for qdisk, quorum disk and quorum
partition but found nothing.
How can I configure a two node cluster to use
>>>
>>> a quorum disk so that the node that can see the disk will keep resources?
>>
>>> I've searched the mailing lists for qdisk, quorum disk and quorum
>>> partition but found nothing.
>>>
>>> How can I configure a two node cluster to use
>>
>> a quorum disk so that the node that can see the disk will keep resources?
>
> We dont have support for qdisk.
> Check out no-quorum-poli
On Mon, Feb 8, 2010 at 4:24 PM, jimbob palmer wrote:
> 2010/2/8 jimbob palmer :
>> Hello,
>>
>> I've searched the mailing lists for qdisk, quorum disk and quorum
>> partition but found nothing.
>>
>> How can I configure a two node cluster to use
>
> a quorum disk so that the node that can see the
2010/2/8 jimbob palmer :
> Hello,
>
> I've searched the mailing lists for qdisk, quorum disk and quorum
> partition but found nothing.
>
> How can I configure a two node cluster to use
a quorum disk so that the node that can see the disk will keep resources?
Thanks.
_
Hello,
I've searched the mailing lists for qdisk, quorum disk and quorum
partition but found nothing.
How can I configure a two node cluster to use
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pac
On Mon, Feb 8, 2010 at 3:25 PM, Adrian Chapela
wrote:
> Hello,
>
> I am trying to reinstall a compilation of Pacemaker+Corosync but I can't
> compile Corosync on one machine. For me is very strange because the
> other can compile without any problem.
>
> The problem is at configuration time, I don
Hello,
I am trying to reinstall a compilation of Pacemaker+Corosync but I can't
compile Corosync on one machine. For me is very strange because the
other can compile without any problem.
The problem is at configuration time, I don't know which file is looking
for, I don't want to compile with ope
2010/2/8 jimbob palmer :
>> I get this message, but I don't think the pacemaker part is working at all.
>>
>> If I run crm_mon, I get "Attemping connection to the cluster.."
>> So it looks broken - but the logs show successful node joining and
>> exiting as I start and stop openais on b
Am Montag, 8. Februar 2010 10:35:41 schrieb Andrew Beekhof:
> On Sun, Feb 7, 2010 at 6:24 PM, Michael Schwartzkopff
wrote:
> > Hi,
> >
> > I tried on amd64 and had no problems. Same setup:
> > plain debian on virtual box with
> > apt-get install pacemaker
> >
> > from people.debian.org/~madkiss/h
> I get this message, but I don't think the pacemaker part is working at all.
>
> If I run crm_mon, I get "Attemping connection to the cluster.."
> So it looks broken - but the logs show successful node joining and
> exiting as I start and stop openais on both nodes. So something is
> w
On Fri, Feb 05, 2010 at 12:44:53PM -0800, Alan Jones wrote:
> The answer is to use configure options to get the different projects to
> agree where var is.
Yes :)
And don't forget to install resource-agents. Please use release
1.0.3 for cluster-glue.
Thanks,
Dejan
> Alan
>
> On Fri, Feb 5, 20
>> pacemaker kind of starts. Using your guide (well written btw - the use
>> of environment variables is clever) Clusters From Scratch*, everything
>> looks like it's working apart from "AIS Executive Service" missing
>> from /var/log/messages - is this normal?
>
> Should be fine, corosync has a di
On Mon, Feb 08, 2010 at 10:35:41AM +0100, Andrew Beekhof wrote:
> On Sun, Feb 7, 2010 at 6:24 PM, Michael Schwartzkopff
> wrote:
> > Hi,
> >
> > I tried on amd64 and had no problems. Same setup:
> > plain debian on virtual box with
> > apt-get install pacemaker
> >
> > from people.debian.org/~mad
On Mon, Feb 8, 2010 at 10:37 AM, jimbob palmer wrote:
Maybe its right, does it run?
>>>
>>> Yum? Unless I force architecture to 64-bit the packages conflict with
>>> each other.
>>
>> I meant pacemaker ;-)
>
> pacemaker kind of starts. Using your guide (well written btw - the use
> of enviro
On Thu, Feb 4, 2010 at 5:24 PM, Yan Gao wrote:
>> And put exclusions for things like passwords before the read for the whole
>> cib?
> Yes. We should specify any "deny" and "write" objects before it.
I like the syntax now, but my original concern (that all the
validation occurs in the client li
On Fri, Feb 5, 2010 at 8:17 PM, Koch, Sebastian
wrote:
> Thanks for your replay Mr. Beekhof
>
> Here ist he stack trace:
> ./CTSlab.py --nodes 'cluster01-node1 cluster01-node2' --benchmark --stack ais
> --logfile /var/log/messages --schema pacemaker-1.0 3
> Feb 05 20:16:40 Random seed is: 1265397
>>> Maybe its right, does it run?
>>
>> Yum? Unless I force architecture to 64-bit the packages conflict with
>> each other.
>
> I meant pacemaker ;-)
pacemaker kind of starts. Using your guide (well written btw - the use
of environment variables is clever) Clusters From Scratch*, everything
look
On Sat, Feb 6, 2010 at 12:21 AM, D. J. Draper wrote:
> Bad news is that Pacemaker on corosync or openais does not appear to work on
> fedora/arm.
You might want to bring this up on the openais list.
They'd probably be interested in getting that fixed (presumably its
the IPC pieces from corosync t
On Sun, Feb 7, 2010 at 6:24 PM, Michael Schwartzkopff wrote:
> Hi,
>
> I tried on amd64 and had no problems. Same setup:
> plain debian on virtual box with
> apt-get install pacemaker
>
> from people.debian.org/~madkiss/ha
>
> only the i386 compile has the problems. Very strange...
Actually this
26 matches
Mail list logo
