1.2.4 just came out, perhaps that will help.
I'll kick off a rebuild shortly
On Thu, Jun 10, 2010 at 4:48 AM, Devin Reade wrote:
> Andrew Beekhof wrote:
>
>> Do any other children start up?
>
> None.
>
>> Where is the mgmtd binary installed to?
>
> /usr/lib64/heartbeat/mgmtd
>
>
>
>
Andrew Beekhof wrote:
> Do any other children start up?
None.
> Where is the mgmtd binary installed to?
/usr/lib64/heartbeat/mgmtd
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Pro
On 06/08/2010 11:20 PM, Andrew Beekhof wrote:
On Wed, Jun 9, 2010 at 7:27 AM, Devin Reade wrote:
I was following the instructions for a new installation of corosync
and was wanting to make use of hb_gui so, following an installation
via yum per the docs, built Pacemaker-Python-GUI-pacemaker-mgm
On Wed, Jun 9, 2010 at 7:27 AM, Devin Reade wrote:
> I was following the instructions for a new installation of corosync
> and was wanting to make use of hb_gui so, following an installation
> via yum per the docs, built Pacemaker-Python-GUI-pacemaker-mgmt-2.0.0
> from source.
>
> Starting corosyn
I was following the instructions for a new installation of corosync
and was wanting to make use of hb_gui so, following an installation
via yum per the docs, built Pacemaker-Python-GUI-pacemaker-mgmt-2.0.0
from source.
Starting corosync works normally without mgmtd in the picture, but as
soon as *
