ctdb - public ip is assigned to us but not on an interface - error

[lejeczek]

On 25/01/17 20:11, lejeczek wrote:
>
>
> On 25/01/17 19:40, Martin Schwenke wrote:
>> On Wed, 25 Jan 2017 10:30:33 +0000, lejeczek 
>> <peljasz at yahoo.co.uk>
>> wrote:
>>
>>> I had a working cluster, very basic, standard. I'm not sure
>>> if recent updates broke it.
>>> I see these:
>>>
>>> 2017/01/24 22:20:05.025164 [recoverd: 3474]: Public IP
>>> '10.5.10.51' is assigned to us but not on an interface
>>> 2017/01/24 22:20:05.027571 [recoverd: 3474]: Trigger
>>> takeoverrun
>>> 2017/01/24 22:20:05.053386 [recoverd: 3474]: Takeover run
>>> starting
>>> 2017/01/24 22:20:05.106044 [ 3309]: Takeover of IP
>>> 10.5.10.51/28 on interface eth0
>>>
>>> and I wonder if anybody also has come across it?
>>>
>>> cluster reports:
>>>
>>> ~]$ ctdb status
>>> Number of nodes:3
>>> pnn:0 10.5.10.55       OK
>>> pnn:1 10.5.10.56       OK (THIS NODE)
>>> pnn:2 10.5.10.57       OK
>>> Generation:91773797
>>> Size:3
>>> hash:0 lmaster:0
>>> hash:1 lmaster:1
>>> hash:2 lmaster:2
>>> Recovery mode:NORMAL (0)
>>> Recovery master:1
>>>
>>> yes seems does not create/assign that public IP.
>>>
>>> ~]$ ctdb ip -v
>>> Public IPs on node 1
>>> 10.5.10.51 node[1] active[eth0] available[eth0] 
>>> configured[eth0]
>> Can you please tell us what version you are running?  
>> Without that it is
>> hard to know if this is the result of a "recent 
>> update"...  ;-)
>>
>> For example, there is 
>> https://bugzilla.samba.org/show_bug.cgi?id=12511
>> in 4.6.0rc1.  However, that message was changed between 
>> 4.4 and 4.5.
>>
>> Also, does the message loop forever?  If so, are there 
>> error messages
>> after "Takeover of IP"?  Or does it just appear once and 
>> then the
>> address is assigned?
>>
>> Thanks...
>>
>> peace & happiness,
>> martin
>>
> hi,
> Cluster runs on Centos 7.x
> I believe it worked with distro's ctdb-4.4.4-9.el7.x86_64.
> Now when it fails it is ctdb-4.4.4-12.el7_3.x86_64.
> It loops forever:
>
> 2017/01/25 20:09:43.763947 [recoverd:17247]: Trigger 
> takeoverrun
> 2017/01/25 20:09:43.765976 [recoverd:17247]: Takeover run 
> starting
> 2017/01/25 20:09:43.777047 [17145]: Takeover of IP 
> 10.5.10.51/28 on interface eth0
> 2017/01/25 20:09:45.360099 [recoverd:17247]: Takeover run 
> completed successfully
> 2017/01/25 20:09:45.371403 [recoverd:17247]: Public IP 
> '10.5.10.51' is assigned to us but not on an interface
> 2017/01/25 20:09:45.371436 [recoverd:17247]: Trigger 
> takeoverrun
> 2017/01/25 20:09:45.371824 [recoverd:17247]: Takeover run 
> starting
> 2017/01/25 20:09:45.372434 [17145]: Takeover of IP 
> 10.5.10.51/28 on interface eth0
> 2017/01/25 20:09:47.136951 [recoverd:17247]: Takeover run 
> completed successfully
> 2017/01/25 20:09:47.152961 [recoverd:17247]: Public IP 
> '10.5.10.51' is assigned to us but not on an interface
> 2017/01/25 20:09:47.152987 [recoverd:17247]: Trigger 
> takeoverrun
> 2017/01/25 20:09:47.154833 [recoverd:17247]: Takeover run 
> starting
> 2017/01/25 20:09:47.156935 [17145]: Takeover of IP 
> 10.5.10.51/28 on interface eth0
>
> thanks
>

another thought - what role here may libvirt play? I should 
have mentioned(I realize now) that this cluster runs off 3 
VMs on:
qemu-kvm-ev-2.6.0-27.1.el7.x86_64
kernel-ml-4.9.4-1.el7.elrepo.x86_64
libvirt-2.0.0-10.el7_3.4.x86_64