Problem: Join Script 97univention-s4-connector Fails

Knowledge Base Community
, , ,
#1

Problem

The join status of the s4-connector reports fails:

root@master:~# univention-run-join-scripts --force --run-scripts 97univention-s4-connector
univention-run-join-scripts: runs all join scripts existing on local computer.
copyright (c) 2001-2019 Univention GmbH, Germany

Running pre-joinscripts hook(s):                           done
Running 97univention-s4-connector.inst
                                                           failed (exitcode: 1)
Running post-joinscripts hook(s):                          done

Environment

Checking /var/log/univention/join.log shows lines like this:

Wait for bind9: .Restarting bind9 (via systemctl): bind9.service.
Restarting samba-ad-dc (via systemctl): samba-ad-dc.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.
Restarting samba-ad-dc (via systemctl): samba-ad-dc.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.
Restarting samba-ad-dc (via systemctl): samba-ad-dc.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.
Restarting samba-ad-dc (via systemctl): samba-ad-dc.service.
Setting connector/s4/poll/sleep
Setting connector/s4/retryrejected
 failed
Setting dns/backend
File: /etc/systemd/system/bind9.service.d/10-configure-backend.conf
File: /etc/init.d/bind9
Restarting bind9 (via systemctl): bind9.service.
**************************************************************
* ERROR: Failed to configure Samba4 as backend for bind.     *
*        Please check the samba and the s4-connector logfile.*
**************************************************************
EXITCODE=1

Additionally a command to identify the IP address of the master fails:

root@ucs:~# host $(ucr get ldap/master)
Host ucs.multi.ucs not found: 3(NXDOMAIN)

Solution

Make sure your DNS Settings are set corretly.

Once fixed, the above command should be successful:

root@ucs:~# host $(ucr get ldap/master)
ucs.multi.ucs has address 10.0.0.10

And then the join script should be successful, too:

root@ucs:~# univention-run-join-scripts 
univention-run-join-scripts: runs all join scripts existing on local computer.
copyright (c) 2001-2019 Univention GmbH, Germany

Running pre-joinscripts hook(s):                           done
Running 01univention-ldap-server-init.inst                 skipped (already executed)
Running 02univention-directory-notifier.inst               skipped (already executed)
[...]
Running 97univention-s4-connector.inst                     skipped (already executed)
Running 98univention-pkgdb-tools.inst                      skipped (already executed)
Running 98univention-samba4-dns.inst                       skipped (already executed)
Running 98univention-samba4-saml-kerberos.inst             skipped (already executed)
Running post-joinscripts hook(s):                          done
Mastodon