- Original Message -
From: hj lee
To: pacemaker@oss.clusterlabs.org ; Daniel Qian
Sent: Wednesday, December 30, 2009 12:16 AM
Subject: Re: [Pacemaker] parse error in config: The consensus timeout
parameter (1200 ms) must be atleast 1.2 * token (1200 ms)
On Tue, Dec 29, 20
On Tue, Dec 29, 2009 at 11:09 AM, Daniel Qian wrote:
>
>> On Mon, Dec 28, 2009 at 07:05:24PM -0500, Daniel Qian wrote:
>>
>>> I am using Corosync 1.2.0 that comes with Fedora 12 and have this
>>> error when trying to start corosync service. If I set it to anything
>>> above 1200 the error goes awa
- Original Message -
From: "Dejan Muhamedagic"
To: ; "Daniel Qian"
Sent: Tuesday, December 29, 2009 4:53 AM
Subject: Re: [Pacemaker] parse error in config: The consensus timeout
parameter (1200 ms) must be atleast 1.2 * token (1200 ms)
Hi,
On Mon, Dec 28, 2009 at 07:05:24PM -050
Kees wrote:
> I seems corosync.conf has to be the same on all nodes, is that true?
> if so, is there a way to let the drdb work on is own link?
>
Yes, the DRBD replication link is independent of corosync and specified
in drbd.conf. A 1Gb/s crossover connection is recommended for ethernet
replicati
Hi,
Maybe this is related to no-quorum-policy. What is no-quorum-policy? You can
check no-quorum-policy in "crm configure show" command. If you can not see
in "crm configure show" command, then it is "stop" by default. If that is
your case, then please set it to ignore by "crm configure property
n
Hi all,
I'm testing heartbeat/corosync. I've been able to make a simple
two-node-cluster with drbd. Now i want to build a 3-node cluster.
Two nodes for storage with drbd. The third node as to become a webserver
getting his data via NFS from the master storge-node.
Sounds simple. But i ran into
Hi guys once again :-)
my resource Hosting on top of ms_drbd_r0 keeps restarting even if the
changes aren't local to the node.
By that, i mean Hosting get's restarted on node1 even if i restart or
outdate and demote node 2.
My constrains:
colocation Hosting_on_ms_drbd_r0 inf: Hosting ms_drbd_
Hi,
On Mon, Dec 28, 2009 at 07:05:24PM -0500, Daniel Qian wrote:
> I am using Corosync 1.2.0 that comes with Fedora 12 and have this
> error when trying to start corosync service. If I set it to anything
> above 1200 the error goes away. Is this a bug or something intended
> for?
Does it happen r
