[Samba] Samba 4.2.0 fails to start if domain was provisioned by classicupgrade

Tom Sampson tsml412101 at gmail.com
Mon Mar 23 08:49:46 MDT 2015


I am trying to upgrade our domain controller to 4.2.0 from 4.1.16, however
samba will not start after the upgrade. It appears to be related to the
fact that this AD domain was created by running classicupgrade. My test
environment, which was originally provisioned from 4.0 does not have this
problem. This server was originally deployed back in 2004 using Samba3 and
OpenLDAP. We upgraded to 4.0 shortly after it's release and have been
regularly upgrading it through all of the 4.0 and 4.1 releases. After
upgrading to 4.2, when I start Samba, I only see 2-3 process running. There
is very little in the way of logged information, even with the level set to
3 or higher. The only thing I can find is a reference to winbindd
failing. "Failed
to fetch our own, local AD domain join password for winbindd's internal use"
The problem appears to be the same as this bug.


In fact, If I set "server services = +winbind -winbindd", Samba does start
and appears to function correctly. That said, I am very leery of deploying
4.2 at this time, knowing this bug exists. Our goal this past weekend was
to upgrade our DC to 4.2 and deploy a secondary here at our main site. I am
also tasked with deploying 3 more DCs at our remote sites in the very near
future. I have major concerns about moving forward with this deployment at
this time. It appears that there is something wrong with our AD data that
is preventing a default install of 4.2.0 from starting and we do not have
full-time IT staff available at these sites, so small problems could easily
escalate. Unfortunately, I don't even know where to start. Apart from the
few complaints from Winbindd the logs seem unhelpful.

More information about the samba mailing list