[Dovecot] v2.1.10: Director director_servers order issue

[Bertrand Jacquin]

D'ar gwener 23 a viz Du 2012 e 08 eur 23, « Bertrand Jacquin » he deus skrivet :
> D'ar gwener 23 a viz Du 2012 e 08 eur 20, « Timo Sirainen » he deus skrivet :
> > On 20.11.2012, at 22.56, Bertrand Jacquin wrote:
> > 
> > > # ring status on node1
> > > director ip port type last failed
> > > 10.0.50.50  9090 self never
> > > 10.0.50.51  9090      never
> > > 
> > > # ring status on node2
> > > director ip port type last failed
> > > 10.0.50.50  9090 self never
> > > 10.0.50.51  9090      never
> > > 
> > > self is the same on both nodes, and that generate some cases that can
> > > be observed on logs :
> > ..
> > > It seems that first sorted entry in director_servers is considered as
> > > "self".
> > 
> > No, Dovecot tries to find the self by bind()ing to all the listed IPs, and assuming that the first one that succeeds is self. Apparently in your system bind() succeeds for non-self IPs as well. Any idea why?
> 
> Yes ! I have the following sysctl :
> 
> net.ipv4.ip_nonlocal_bind    = 1

Anyway, with net.ipv4.ip_nonlocal_bind = 0 it's OK.

-- 
Beber
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://dovecot.org/pipermail/dovecot/attachments/20121123/35162392/attachment-0004.bin>