Hi, Andrew
I was going to confirm the suicide function by STONITH implemented by
the following changes.
https://github.com/ClusterLabs/pacemaker/commit/1a26605e1b5840f49d44b47a1f083c2cdb6f673b
The environment is as follows.
Pacemaker-1.1.6(commit 31f6ca36cca57b8c08f7cf89a205331ab8c292ad)
Heartbea
On Mar 13, 2012, at 2:21 PM, Jake Smith wrote:
>> From: "Phillip Frost"
>> Subject: [Pacemaker] getting started - crm hangs when adding resources,
>> even "crm ra classes" hangs
>>
>> more interestingly, even "crm ra classes" never terminates, again
>> with no output, and nothing appended
- Original Message -
> From: "Phillip Frost"
> To: pacemaker@oss.clusterlabs.org
> Sent: Tuesday, March 13, 2012 1:21:00 PM
> Subject: [Pacemaker] getting started - crm hangs when adding resources,
> even "crm ra classes" hangs
>
> I'm trying to set up pacemaker for the first time
I'm trying to set up pacemaker for the first time, following the instructions
in clusters from scratch, on Debian squeeze, using pacemaker and corosync from
squeeze-backports. I seem to have gotten as far as getting two nodes in the
cluster:
# crm status
Last updated: Tue Mar 13 13
Le 07/03/2012 22:08, Lars Ellenberg a écrit :
Did you also time it as
time /etc/init.d/firewall>out.txt 2>err.txt
Yes, it's the same, 65 seconds vs 24 from Pacemaker.
It only prints ~250 lines.
Other than above suggestion,
did you verify that it ends up doing the same thing
when started f
On Tue, Mar 13, 2012 at 9:44 PM, wrote:
> Hi,
>
> I'm running Fedora 16 and I have the following error at the startup of my
> server:
>
> systemctl status pacemaker.service
>> pacemaker.service - Pacemaker High Availability Cluster Manager
>> Loaded: loaded (/lib/systemd/system/pacemaker.se
Hi,
I'm running Fedora 16 and I have the following error at the startup of my
server:
systemctl status pacemaker.service > pacemaker.service - Pacemaker High
Availability Cluster Manager > Loaded: loaded
(/lib/systemd/system/pacemaker.service; enabled) > Active: failed since Mon, 05
Dec 201
