>>> schrieb am 19.12.2016 um 20:37 in Nachricht
:
>> 3 Nodes A B C.
>> If resource on:
>> A + B => ok
>> Only A => ok
>> Only B => ok
>> Only C => ok
>> A + C => random fail
>> B + C => random fail
>> A + B + C => random fail
>
> I use same corosync / pacemaker on three host, but:
> Host A & B h
I'm fairly new to Pacemaker and have a few questions about
The following log event and why resources was removed from my cluster
Right before the resources being killed SIGTERM I notice the following
message.
Dec 18 19:18:18 clusternode38.mf stonith-ng[10739]: notice: On loss of
CCM Quorum: Igno
I change my setting from clusterip_hash="sourceip-sourceport" to
clusterip_hash="sourceip".
And try to ping.
>From one host (not a node) on the network, I get no answer.
>From another host (not a node) on the network I get:
PING 10.0.0.97 (10.0.0.97) 56(84) bytes of data.
64 bytes from 10.0.0.97:
> On Dec 19, 2016, at 11:36 AM, al...@amisw.com wrote:
>
>> Maybe I'm missing something here, and if so, my apologies, but to me it
>> looks like you are trying to put the same IP address on three different
>> machines SIMULTANEOUSLY.
>
> Yes it what I do. But it's seem normal for me, I just
> ... For me, this work with arp multicast, who give same "virtual" arp
> to different hosts
Every hosts in the cluster get the request, and a modulo choose which one
answer. It's just how I understand this shared ip.
___
Users mailing list: Users@clu
> Maybe I'm missing something here, and if so, my apologies, but to me it
> looks like you are trying to put the same IP address on three different
> machines SIMULTANEOUSLY.
Yes it what I do. But it's seem normal for me, I just follow guide like
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-
Maybe I'm missing something here, and if so, my apologies, but to me it looks like you are trying to put the same IP address on three different machines SIMULTANEOUSLY. This will never work from a networking standpoint - it has nothing to do with pacemaker, etc, other than that it is responsibl
> 3 Nodes A B C.
> If resource on:
> A + B => ok
> Only A => ok
> Only B => ok
> Only C => ok
> A + C => random fail
> B + C => random fail
> A + B + C => random fail
I use same corosync / pacemaker on three host, but:
Host A & B have same kernel, C is different:
A & B : 3.7.10-1.45-desktop
C: 4.1
Hi,
My problem is still here. I search but don't find. I try to change network
cable to put the 3 hosts together on same switch, but same problem.
So with this:
primitive ip_apache_localnet ocf:heartbeat:IPaddr2 \
params ip="10.0.0.99" \
cidr_netmask="32" op monitor interval="30s"
clone cl_i
On Mon, 19 Dec 2016 13:37:09 +0100
Klaus Wenninger wrote:
> On 12/17/2016 11:55 PM, Jehan-Guillaume de Rorthais wrote:
> > On Wed, 14 Dec 2016 14:52:41 +0100
> > Klaus Wenninger wrote:
> >
> >> On 12/14/2016 01:26 PM, Jehan-Guillaume de Rorthais wrote:
> >>> On Thu, 8 Dec 2016 11:47:20 +0100
On 12/17/2016 11:55 PM, Jehan-Guillaume de Rorthais wrote:
> On Wed, 14 Dec 2016 14:52:41 +0100
> Klaus Wenninger wrote:
>
>> On 12/14/2016 01:26 PM, Jehan-Guillaume de Rorthais wrote:
>>> On Thu, 8 Dec 2016 11:47:20 +0100
>>> Jehan-Guillaume de Rorthais wrote:
>>>
Hello,
While s
Hi,
setup:
...
primitive sysinfo ocf:pacemaker:SysInfo \
params disks="/tmp /var" min_disk_free=100M disk_unit=M \
op monitor interval=15s
...
node-health-strategy=migrate-on-red
...
when event occurs cluster set #health_disk value from "green" to "red" ->
resources get moved fro
12 matches
Mail list logo
