samba - Dec 2023 - Failed to store repsFrom - Indexed and full searches both failed!

Thanks for the help, Rowland!!

if so, you do not 'provision', you 'join' a new
DC.
> Can you please post the exact command you used.

Yes, I misspelled it! It's domain join!!! :D
samba-tool domain join campus.sertao.ifrs.edu.br DC -U
"CAMPUS\Administrator" --option='idmap_ldb:use rfc2307 = yes'

Not sure why you are doing that, if you are going to use Bind9, why
not
> just join with '--dns-backend=BIND9_DLZ' ?

You're right. I forgot that I could have put that option in the command
above.

Provided that there are no records in AD for the DC, you should be
able
> to use the old hostname and IP.

The best thing then is to set up a new VM, right?



On Sat, Dec 9, 2023 at 1:57?PM Rowland Penny via samba <
samba at lists.samba.org> wrote:
> On Sat, 9 Dec 2023 13:20:39 -0300
> Elias Pereira via samba <samba at lists.samba.org> wrote:
>
> > hello,
> >
> > Using the same server, hostname, and IP, I performed an offline
> > demotion of dc4 because the online demotion resulted in an error.
> >
> > After the offline demotion, I checked via RSAT, and the entries had
> > been removed.
> >
> > Later...
> > - I deleted the .tdb and .ldb files.
> > - I executed the provisioning command.
>
> I thought that you were replacing one existing DC in a multi DC domain,
> if so, you do not 'provision', you 'join' a new DC.
> Can you please post the exact command you used.
>
> > - I backed up the idmap.ldb and copied it to dc4 using rsync.
> > - I performed rsync of the sysvol folder.
> > - I executed the command "samba-tool ntacl sysvolreset."
> > - I recreated the bind entries via "samba_upgradedns
> > --dns-backend=SAMBA_INTERNAL" and again with
"samba_upgradedns
> > --dns-backend=BIND9_DLZ."
>
> Not sure why you are doing that, if you are going to use Bind9, why not
> just join with '--dns-backend=BIND9_DLZ' ?
>
> >
> > I restarted bind and samba, tested "drs showrepl" and
> > "samba_dnsupdate," and they were okay.
> >
> > I left a tail running on the log, and after some time, the error
> > "Failed to store repsFrom - Indexed and full searches both
failed!"
> > returned.
> >
> > Is there still a chance to use the same hostname and IP, or do I need
> > to change everything?
>
> Provided that there are no records in AD for the DC, you should be able
> to use the old hostname and IP.
>
> Rowland
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

-- 
Elias Pereira

On Sat, 9 Dec 2023 14:10:40 -0300
Elias Pereira via samba <samba at lists.samba.org> wrote:
> Thanks for the help, Rowland!!
> 
> if so, you do not 'provision', you 'join' a new DC.
> > Can you please post the exact command you used.
> 
> 
> Yes, I misspelled it! It's domain join!!! :D
> samba-tool domain join campus.sertao.ifrs.edu.br DC -U
> "CAMPUS\Administrator" --option='idmap_ldb:use rfc2307 =
yes'
> 
> Not sure why you are doing that, if you are going to use Bind9, why
> not
> > just join with '--dns-backend=BIND9_DLZ' ?
> 
> 
> You're right. I forgot that I could have put that option in the
> command above.
> 
> Provided that there are no records in AD for the DC, you should be
> able
> > to use the old hostname and IP.
> 
> 
> The best thing then is to set up a new VM, right?
> 
Sorry to be late in replying to this, got a bit swamped.

If you are having problems with a single Samba AD DC in a multiple DC
domain i.e. the problem occurs only on one DC and the others have no
problems. Then it doesn't matter what Samba is running on, the easiest
fix is to fully demote the faulty DC and create a new one, you may be
able to fix the existing DC, but it will undoubtedly take longer.

Rowland