Re: [Pacemaker] Lot of errors after update

Hello, Can somebody tell the status of this issue? Regards, Vlad. On 06/10/14 04:23, renayama19661...@ybb.ne.jp wrote: Hi Andrew, lrmd[1632]:error: crm_abort: crm_glib_handler: Forked child 1840 to record non-fatal assert at logging.c:73 : Source ID 51 was not found when attempting to r

[Pacemaker] Multiple live cib in one pacemaker

Hello, I am using Pacemaker 1.1.12 together with Corosync 2.4.3 in my cluster environment. I have two nodes in cluster that are in different LAN locations. It may be situation that nodes will not be able to connect with each other because of network failure. In that situation split brain can occur

Re: [Pacemaker] Multiple live cib in one pacemaker

Fixed by using a third node. On Thu, Feb 19, 2015 at 8:26 AM, Adam Błaszczykowski < adam.blaszczykow...@gmail.com> wrote: > Hello, > I am using Pacemaker 1.1.12 together with Corosync 2.4.3 in my cluster > environment. I have two nodes in cluster that are in different LAN > locations. It may be s

[Pacemaker] Unsubscribe

Mit freundlichen Grüßen Gerhard Milerski Schenker Deutschland AG Service Center IT Rechenzentrum Coburg Virchowstraße 16 96450 Coburg Telefon +49 9561 839 - 245 Telefax +49 9561 18606 www.dbschenker.com/de Wir arbeiten ausschließlich auf Grundlage der Allgemeine

Re: [Pacemaker] Multiple live cib in one pacemaker

Adam Błaszczykowski writes: > Hello, > I am using Pacemaker 1.1.12 together with Corosync 2.4.3 in my cluster > environment. I have two nodes in cluster that are in different LAN > locations. It may be situation that nodes will not be able to connect with > each other because of network failure.

Re: [Pacemaker] Multiple live cib in one pacemaker

> On 20 Feb 2015, at 1:52 am, Kristoffer Grönlund wrote: > > Adam Błaszczykowski writes: > >> Hello, >> I am using Pacemaker 1.1.12 together with Corosync 2.4.3 in my cluster >> environment. I have two nodes in cluster that are in different LAN >> locations. It may be situation that nodes will

Re: [Pacemaker] RHEL 6 to RHEL 7 upgrade

> On 11 Feb 2015, at 9:36 pm, Alex Samad - Yieldbroker > wrote: > > Hi > > I am doing some planning for a Centos 6 to Centos 7 upgrade. Just wondering > if there are any gotchas with pacemaker/cman? There is no cman in 7 You'll need to configure corosync2 directly (instead of via cluster.con

Re: [Pacemaker] [Linux-HA] Announcing the Heartbeat 3.0.6 Release

> On 11 Feb 2015, at 8:24 am, Lars Ellenberg wrote: > > > TL;DR: > > If you intend to set up a new High Availability cluster > using the Pacemaker cluster manager, > you typically should not care for Heartbeat, > but use recent releases (2.3.x) of Corosync. > > If you don't care for Hear

Re: [Pacemaker] pacemaker does not start after cman config

> On 10 Feb 2015, at 11:53 pm, Lukas Kostyan wrote: > > Hi all, > > was following the guide from clusterlab but use debian wheezy. > corosync 1.4.2-3 > > pacemaker 1.1.7-1 > cman 3.0.12-3.2+deb7u2 > > configured the active/passive with no problems but a

[Pacemaker] This mailing list will go away soon

One of the things that was agreed at the recent cluster summit was a consolidation cluster related irc channels, mailing lists, and websites. In keeping with this, the pacemaker mailing list should now be considered deprecated and will no longer accept messages as of March 1st 2015. We still wan