[Samba] Problem after update version 4.15.0

[Andrew Bartlett]

Yes, you start from 4.14.0rc1 as this is the branch point where master
split into 4.14 (working) and what would eventually be 4.15.

If you do it on a new test DC then the paths will all line up with the
source based install, otherwise an existing test DC is fine as long as
you fix Samba up to find the DBs etc.  A new DC may be simpler.

Thanks,

Andrew

On Sun, 2021-10-10 at 22:30 +0200, Ingo Asche via samba wrote:
> Hi Andrew,
> 
> I will try that tomorrow. I hope I can get you the needed
> information, 
> never done something like that before.
> 
> Just one question: Samba 4.14.0rc1 is really correct? Not 4.15.0rc1?
> 
> And, that may be a dumb question, should I do that on the existing
> test 
> DC or should I install it new?
> 
> Regards
> Ingo
> 
> Andrew Bartlett via samba schrieb am 10.10.2021 um 21:35:
> > On Sat, 2021-10-09 at 16:37 +0200, Ingo Asche via samba wrote:
> > > To be on the sure side: I joined the test workstation to my
> > > 4.14.8
> > > 
> > > domain and tried to login. This worked without problem. So it
> > > seems
> > > on
> > > 
> > > the first sight that the Windows installation is not the problem.
> > > By
> > > the
> > > 
> > > way it's an actual Windows 10 21H1.
> > > 
> > > 
> > > 
> > > Rejoining to the test domain worked but again no longer login is
> > > possible.
> > So, what we really need is for a git bisect in a git
> > checkout.  Build
> > Samba from source on Samba 4.14.0rc1 with:
> > 
> > git clone https://git.samba.org/samba.git
> > cd samba
> > ./configure.developer && make -j && make install
> > (join to your domain or point at your existing DB)
> > 
> > Confirm this fails (if it works then we will instead bisect back to
> > find where it started working, but for now I assume it fails), then
> > run:
> > 
> > git checkout samba-4.14.0rc1
> > 
> > ./configure.developer && make -j && make install
> > (join to your domain or
> > point at your existing DB)
> > 
> > Confirm this works (if it fails we have bigger problems), then run:
> > 
> > git bisect good HEAD
> > git bisect bad origin/master
> > 
> > The run
> > 
> > ./configure.developer && make -j && make install
> > for each step, answering with
> > 
> > git bisect [good|bad]
> > 
> > for each decision point.
> > 
> > Use 'git bisect skip' if it all blows up, but do 'rm -rf bin' first
> > and
> > perhaps blow away the binaries in your install.  You should also,
> > after
> > the first join, be able to run 'bin/samba' rather than the slower
> > 'make
> > install' step.
> > 
> > You don't need to re-join each time as the DB is upgrade/downgrade
> > compatible on these versions.
> > 
> > Looking into this for us would save us a lot of time, we are quite
> > busy
> > on some other things and need your help.
> > 
> > Andrew Bartlett
> > 
> > > Regards
> > > 
> > > Ingo
> 
> 
-- 
Andrew Bartlett (he/him)       https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Team Lead, Catalyst IT   https://catalyst.net.nz/services/samba

Samba Development and Support, Catalyst IT - Expert Open Source
Solutions