> Hi,
>
> you have to decide: heartbeat OR corosync. It makes no sense to install both
> cluster stacks.
I will use corosync -as recommended in your book which I have on my
table here :-) ;
I just followed the clusterlabs install directives for CentOS:
"And finally, install Pacemaker:
yum install -y pacemaker corosync heartbeat"
This ends up in the packages
pacemaker-1.0.10-1.4.el5.x86_64 (from clusterlabs repo)
heartbeat-3.0.3-2.3.el5.x86_64 (")
corosync-1.2.7-1.1.el5.x86_64 (")
The epel repository yields only version 2 packages.
Maybe the heartbeat rpm contains something that is always needed? Not sure why
they would recommend to install it otherwise.
But I cannot find the mgmtd, or how else do I start a server that the GUI can
connect to?
(I cannot even find the GUI, perhaps the packages were built without it?)
I have no problem compiling this, even providing an rpm when done, but I have
no clue why make complains abount missing files in the mgmtd directory.
Am I using the wrong source perhaps? I used the source from
http://hg.clusterlabs.org/pacemaker/pygui/archive/tip.tar.bz2
as indicated on the clusterlabs website.
Any hints welcome, Jakob Curdes
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
