ACK
Sadly I didn't tried build with removed libraries so build doesn't fail
(because libsam.so. depends on needed libraries).
But MOCK seems to be ultra simple to use, so this situation shouldn't
appear again.
Angus Salkeld napsal(a):
> Signed-off-by: Angus Salkeld
> ---
> cts/agents/Mak
Hi Steven,
I've git it a try :
the values of token=45000 and token_retransmits_before_loss_const=45 leads
to also set consensus=54000 (at least 1,2 * token) otherwise corosync
start fails.
With these values, when I do ifdown eth0 on one node, in fact it takes
around 98s
for this node to appear
On Fri, May 21, 2010 at 09:20:50AM +0200, Jan Friesse wrote:
> ACK
Committed.
>
> Sadly I didn't tried build with removed libraries so build doesn't
> fail (because libsam.so. depends on needed libraries).
>
> But MOCK seems to be ultra simple to use, so this situation
> shouldn't appear ag
Included is patch with SAM confdb integration. This should be last piece
to quorum + confdb + watchdog puzzle integration (from SAM point).
I decided to NOT include policy WATHCDOG, but rather much stronger
CONFDB policy, which is only flag for existing policies. WATCHDOG can be
simulated by C
Hi
These new releases of corosync do not start successfully on RHEL5 :
corosync-1.2.2-1.1.el5
corosynclib-1.2.2-1.1.el5
I 've joined the messages trace.
whereas on same machines, these old ones works fine :
corosync-1.2.1-1.el5
corosynclib-1.2.1-1.el5
I've reinstalled these old ones and it work
Did you build your release, or use the clusterlabs rpms?
We have RHEL 5.5, the 1.2.2-1.1 rpms installed and ran just fine
here...
-kent
___
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listi
On Fri, 2010-05-21 at 16:19 +0200, Alain.Moulle wrote:
> Hi
>
> These new releases of corosync do not start successfully on RHEL5 :
> corosync-1.2.2-1.1.el5
> corosynclib-1.2.2-1.1.el5
> I 've joined the messages trace.
>
> whereas on same machines, these old ones works fine :
> corosync-1.2.1-1.
On Thu, 2010-05-20 at 10:17 -0700, Alan Jones wrote:
> I have a prototype of this working. However, I have some questions
> about the 1.2.1 code:
> Why is broadcast_use an attribute of totem_config and not
> totem_interface?
With broadcast, it would be possible for a cross connected switch from
t
We are using the following to create a 2-node highly-available cluster:
Disk device - fusion-io cards (PCIe SSD's)
DRBD/Corosync/Pacemaker
[r...@motest16 log]# rpm -qa | egrep "drbd|corosync|pacemaker"
drbd-pacemaker-8.3.7-1
drbd-8.3.7-1
drbd-bash-completion-8.3.7-1
drbd-xen-8.3.7-1
drbd-km-debug
