"univention-samba4' is not configured" after upgrading to 5.2

UCS - Univention Corporate Server
, ,
1

Hello.

I have a master server and a backup server that showed no failures or errors before the update.

After updating the system to 5.2, the master server presented the following error.

“The following KDCs were unreachable: tcp srvad2.cnsd.local:88, udp srvad2.cnsd.local:88”

And the backup server had a critical error.

"“univention-check-join-status” returned a problem with the domain join.

STDOUT:
Warning: ‘univention-samba4’ is not configured.
Warning: ‘univention-samba4-dns’ is not configured.
Error: Not all install files configured: 2 missing

See Manual: Analysis of listener/notifier problems or run the join-scripts via “Domain join” module."

I reviewed the settings with the backup file and they are unchanged.

How can I check more details and resolve these errors?

Thanks

2

Please run univention-run-join-scripts and then tell the reported errors from the log file /var/log/univention/join.log.

3

Hello. Thanks for getting back to us.

I verified that the samba4 database was corrupt.

I carried out the procedures below and managed to make the backup server join the master server.

samba-tool dbcheck --cross-ncs --fix --yes
samba-tool dbcheck --reindex
samba-tool dbcheck --force-modules

Thanks for the help.

4

since I’m running in the same issue, two short questions:
1.) should the “univention-run-join-scripts” run on the primary node or the backup node?
2.) should the fix be executed on the primary or the secondary and then be followed by an additional join?

[EDIT]
The error message is as follows on the backup node:
2026-03-26 11:56:48.159337167+01:00 (in joinscript_init)
Samba4 backend database not available yet, exiting joinscript 98univention-samba4-dns.
EXITCODE=1

[EDIT2]
the following message is shown on the primary node:
samba-tool drs showrepl gibt ein Problem mit der Replikation zurück.
In eingehend ‘DC=ForestDnsZones,DC=domain,DC=de’: Fehler während der DRS Replikation von Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In eingehend ‘DC=DomainDnsZones,DC=domain,DC=de’: Fehler während der DRS Replikation von Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In eingehend ‘DC=domain,DC=de’: Fehler während der DRS Replikation von Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In eingehend ‘CN=Schema,CN=Configuration,DC=domain,DC=de’: Fehler während der DRS Replikation von Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In eingehend ‘CN=Configuration,DC=domain,DC=de’: Fehler während der DRS Replikation von Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In ausgehend ‘DC=ForestDnsZones,DC=domain,DC=de’: Fehler während der DRS Replikation nach Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In ausgehend ‘DC=DomainDnsZones,DC=domain,DC=de’: Fehler während der DRS Replikation nach Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In ausgehend ‘DC=domain,DC=de’: Fehler während der DRS Replikation nach Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).
In ausgehend ‘CN=Configuration,DC=domain,DC=de’: Fehler während der DRS Replikation nach Default-First-Site-Name/UCS5 (WERR_FILE_NOT_FOUND).

5

We solved this for the @pdiadmin in this way: