[Samba] Upgrade From 4.0.16 To 4.0.17+ Breaks

[Andrew Bartlett]

On Fri, 2014-06-27 at 11:43 +1000, David Minard wrote:
> On 27/06/14 09:07, Andrew Bartlett wrote:
> > On Tue, 2014-06-24 at 22:02 +1000, David Minard wrote:
> >> G'day Guys,
> >>
> >> 	I've hit a snag.  After using S4 from Alpha, beta, rc, 4.0.1..16 with success, I wanted to upgrade to the 4.1 series.  However, after compiling, installing, and provisioning, with no errors, samba4 won't start correctly.  I did a few tests by installing from scratch, on the same server each of the following versions (4.0.17, 4.0.18, 4.0.19, and 4.1.9), and got the same errors in log.samba.  Samba4.0.16, on the same server runs flawlessly.  I'm running on Centos6.5_64 with the latest updates as of today.  I've spend a few days with Google, but I couldn't find anything helpful.
> >> 	It all points to samba trying to set up IPv6 bindings, but it cannot.  Any ideas why this might be?  How can I resolve it?  What changed from beyond version 4.0.16 that would cause this issue?
> > Try 'interfaces = 127.0.0.1 192.168.1.1' (or whatever your address is).
> > I think I saw a patch for this (IPv6 found but not running) on the
> > samba-technical list recently.
> 
> No change.  I'm still getting the same errors.

Also add 'bind interfaces only = yes'

-- 
Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba