On 31 Jul 2014, at 2:48 am, Cédric Dufour - Idiap Research Institute
wrote:
> Hello,
>
> After packaging pacemaker 1.1.12 for Debian/Wheezy (along corosync 1.4.6 and
> libqb 0.17.0), I have successfully initialized a new cluster.
>
> The CIB processing improvement is amazing indeed! :-)
>
>
Hello,
After packaging pacemaker 1.1.12 for Debian/Wheezy (along corosync 1.4.6 and
libqb 0.17.0), I have successfully initialized a new cluster.
The CIB processing improvement is amazing indeed! :-)
Back to a very simple test cluster, the only problem I have is with fencing,
which fails altog
On Wed, Jul 30, 2014 at 02:59:31PM +0200, Machiel wrote:
> Hi Guys
>
> We are trying to setup the following, however we can not seem to
> find any references on the internet which will explain on how to
> configure it.
>
> We have 3 machines, and we need to setup load balancing on the
> m
Hi Guys
We are trying to setup the following, however we can not seem to
find any references on the internet which will explain on how to
configure it.
We have 3 machines, and we need to setup load balancing on the
machines as follows:
- Load balancer and apps running o
On Tue, 29 Jul 2014 17:10:06 +0200 wrote Michael Schwartzkopff:
> Am Dienstag, 29. Juli 2014, 14:52:05 schrieb Thomas Müller:
>> Hi
>>
>> I've got a 2 node cluster with 4 VM's. If a node fails 2 of them should
>> be stopped (the dev machines) to prevent the physical machine from
>> swap'ing.
>>
Von:Andrew Beekhof
An: The Pacemaker cluster resource manager
Datum: 30.07.2014 10:54
Betreff:Re: [Pacemaker] Pacemaker 1.1.12 - crm_mon email
notification
On 30 Jul 2014, at 6:08 pm, philipp.achmuel...@arz.at wrote:
>> hi,
>>
>> found several threads about that in archi
On 30 Jul 2014, at 6:08 pm, philipp.achmuel...@arz.at wrote:
> hi,
>
> found several threads about that in archive - no solution for me.
There was a bug: https://github.com/beekhof/pacemaker/commit/3df6aff
> ---
> i'm running pacemaker 1.1.12 (+corosync 2.3.3 on sles 11.3). compiled
> inc
hi,
found several threads about that in archive - no solution for me.
---
i'm running pacemaker 1.1.12 (+corosync 2.3.3 on sles 11.3). compiled
including esmtp support for crm_mon.
crm_mon help shows mailing parameters. i tried 2 ClusterMon Agent
implementations for notification:
-T/-F/-H and -E
Apologies for the delayed response. Well i am using IPAddr2 resource.
I don't configure the addresses statically. It gets configured when
pacemaker starts this resource.Failure handling of this link(when i
manually bring the link down ) also works. It's just that even though
the IP has moved.
If yo
