Is there anything in the code of any of the versions for reporting or even
fixing any records on the DB which violate these new security constraints?
________________________________
From: samba <samba-bounces at lists.samba.org> on behalf of Peter
Mittermayer via samba <samba at lists.samba.org>
Sent: Saturday, December 14, 2024 7:01:30 AM
To: samba at lists.samba.org <samba at lists.samba.org>
Subject: Re: [Samba] Error when joining new DC
Hi Douglas,
I did join a DC (let's say DC2) with 4.14.9 and in place upgrade to 4.10.
but still I'm unable to join another DC with higher version when using
'--server DC2'.
Unfortunately I had a medical emergency in the family and wasn't able to do
any work on verifying the DB.
Peter
________________________________
From: Douglas Bagnall <douglas.bagnall at catalyst.net.nz>
Sent: Friday, December 13, 2024 11:13:33 PM
To: Peter Mittermayer <samba.lists at outlook.com>; samba at
lists.samba.org <samba at lists.samba.org>
Subject: Re: [Samba] Error when joining new DC
On 13/12/24 18:43, Peter Mittermayer via samba wrote:> Hi Douglas,
> Doing an online backup is running the same checks as during join? I noted
the same behavior. I already went up to debug level 9 without seeing any
additional information. But will try 10 too.
> This is only about sam.ldb or any of the other DB files as well?
> Thanks
Yes, an online backup is like a join that doesn't actually join.
There are some files in the sam.ldb.d/ directory that are effectively
part of sam.ldb from Samba's point of view, but otherwise nothing
else matters.
Have you tried a join with 4.14.9, then do an in-place upgrade?
cheers,
Douglas
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba