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

[lejeczek]

On 27/01/17 08:02, Martin Schwenke wrote:
> On Wed, 25 Jan 2017 20:11:03 +0000, lejeczek <peljasz at yahoo.co.uk>
> wrote:
>
>> 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
> It might be worth seeing the changelog for the RPM to see what has
> changed, since it is actually the same CTDB version, perhaps with
> distro patches on top.
>
> The other thing to check is whether the IP address is actually on the
> interface.   If not, are you able to add it using:
>
>    ip addr add 10.5.10.51/28 dev eth0
>
> or similar?
>
> If CTDB can't add it then there should be an error from the
> 10.interface event script... but we're not seeing an error.
>
> The relevant code has seen some improvement in recent versions but I
> don't remember it failing like this...
>
> peace & happiness,
> martin

I'm afraid it is the case, bare-metal same ctdb versions(all 
rest of samba suite) runs it just fine, at least here for me.
Well.. I'd have question, I've been just introduced to ctdb 
and learning, trying samba list first but not much feedback 
on ctdb there, so I'd hope here, so..

this - https://wiki.samba.org/index.php/CTDB_Setup - gives 
out an impression that ".. These are the addresses that the 
SMBD daemons will bind to.."
But - before I share software versions - it does not. My 
smbd attaches to and listens on all interfaces: is this 
normal, expected?
And if it is, then how to tell/force smdb(under CTDB) to 
bind to only specific NICs?
I try usual:

   bind interfaces only = yes
   interfaces = 127.0.0.1 em1(which is the NIC used in 
public_addresses)

I put there public IP(s) too, but to no avail, smbd would 
not go to that public IP, daemon does not respond on that 
IP(unless of course these directives are absent, or... I 
restart smbd manually later)... which, seems loco to me.

How does one make samba run off only those public IPs?
many thanks,
L.