Web-Setup nach Installation im Textmode bleibt bei 05univention-bind hängen

Hallo,

nach dem ich nach einer komplizierten Installation im Textmode das System installiert hatte, und das System per Webserver (Setup) ansprechbar ist, bleibt das Setup beim einrichten im Befehl:
/usr/lib/univention-install/05univention-bind.inst ohne Fehlermeldung hängen.

Ein Anmelden per SSH ist möglich.
Wird der Prozess abgebrochen (Kill) bleibt auch noch der Befehl:
/usr/lib/univention-install/10univention-ldap-server.inst hängen.

Folgende Dienste laufen beim mir: (systemctl list-units -all --full -t service) [Liste gekürzt]
UNIT LOAD ACTIVE SUB JOB
apache2.serloaded active running
atd.serviceloaded active running
bind9.serviloaded activating start-post start
console-setloaded active exited
containerd.loaded active running
cron.servicloaded active running
dbus.servicloaded active running
docker.servloaded active running
getty@tty1.loaded active running
heimdal-kdcloaded active exited
ifplugd.serloaded active exited
inetd.serviloaded active running
kdm.serviceloaded active exited
keyboard-seloaded active exited
kmod-staticloaded active exited
lvm2-lvmetaloaded active running
lvm2-monitoloaded active exited
memcached.sloaded active running
nagios-nrpeloaded active running
networking.loaded active exited
nfs-blkmap.loaded active running
nfs-idmapd.loaded active running
nfs-mountd.loaded active running
nfs-server.loaded active exited
nmbd.servicloaded active exited
nscd.servicloaded active running
ntp.serviceloaded active exited
postfix.serloaded active exited
postfix@-.sloaded active running
postgresql.loaded active exited
postgresql@loaded active running
quota.serviloaded active exited
rpcbind.serloaded active running
rsyslog.serloaded active running
samba-ad-dcloaded active exited
samba.serviloaded active exited
saslauthd.sloaded active exited
● slapd.serviloaded failed failed
smbd.servicloaded active exited
ssh.serviceloaded active running
stunnel4.seloaded active exited
sysstat.serloaded active exited
systemd-bacloaded active exited
systemd-fscloaded active exited
systemd-jouloaded active exited
systemd-jouloaded active running
systemd-logloaded active running
systemd-modloaded active exited
systemd-ranloaded active exited
systemd-remloaded active exited
systemd-sysloaded active exited
systemd-tmploaded active exited
systemd-tmploaded active exited
systemd-udeloaded active exited
systemd-udeloaded active running
systemd-updloaded active exited
systemd-useloaded active exited
● univention-loaded failed failed
univention-loaded active running
● univention-loaded failed failed
univention-loaded active exited
univention-loaded active exited
● univention-loaded failed failed
univention-loaded active running
univention-loaded active running
univention-loaded active exited
univention-loaded active running
● univention-loaded failed failed
● univention-loaded failed failed
univention-loaded active running
univention-loaded activating auto-restar
univention-loaded active running
● univention-loaded failed failed
upower.servloaded active running
winbind.serloaded active exited

Der Dienst slapd bringt folgende Fehlermeldung: (systemctl status slapd.service)
● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol)
Loaded: loaded (/etc/init.d/slapd; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-10-29 15:35:12 CET; 2h 24min ago
Docs: man:systemd-sysv-generator(8)
Process: 31929 ExecStart=/etc/init.d/slapd start (code=exited, status=1/FAILURE)
CPU: 203ms

Okt 29 15:35:06 hpes ldapsearch[31961]: DIGEST-MD5 common mech free
Okt 29 15:35:08 hpes slapd[31929]: ldap_sasl_bind(SIMPLE): Can’t contact LDAP server (-1)
Okt 29 15:35:10 hpes slapd[31929]: ldap_sasl_bind(SIMPLE): Can’t contact LDAP server (-1)
Okt 29 15:35:12 hpes slapd[31929]: ldap_sasl_bind(SIMPLE): Can’t contact LDAP server (-1)
Okt 29 15:35:12 hpes ldapsearch[32018]: DIGEST-MD5 common mech free
Okt 29 15:35:12 hpes slapd[31929]: Failed to search schema
Okt 29 15:35:12 hpes systemd[1]: slapd.service: Control process exited, code=exited status=1
Okt 29 15:35:12 hpes systemd[1]: Failed to start LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol).
Okt 29 15:35:12 hpes systemd[1]: slapd.service: Unit entered failed state.
Okt 29 15:35:12 hpes systemd[1]: slapd.service: Failed with result ‘exit-code’.

Der Samba Dienst läuft nicht und ist auch vermutlich nicht richtig konfiguriert (systemctl status samba-ad-dc.service)
● samba-ad-dc.service - LSB: Samba daemons for the AD DC
Loaded: loaded (/etc/init.d/samba-ad-dc; generated; vendor preset: enabled)
Active: active (exited) since Thu 2020-10-29 15:50:15 CET; 2h 12min ago
Docs: man:systemd-sysv-generator(8)
Process: 5415 ExecStop=/etc/init.d/samba-ad-dc stop (code=exited, status=0/SUCCESS)
Process: 5426 ExecStart=/etc/init.d/samba-ad-dc start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Memory: 0B
CPU: 0
CGroup: /system.slice/samba-ad-dc.service

Okt 29 15:50:14 hpes systemd[1]: Stopped LSB: Samba daemons for the AD DC.
Okt 29 15:50:14 hpes systemd[1]: Starting LSB: Samba daemons for the AD DC…
Okt 29 15:50:15 hpes samba-ad-dc[5426]: Starting Samba AD DC daemon: samba
Okt 29 15:50:15 hpes samba-ad-dc[5426]: Warning: Fake start-stop-daemon called, doing nothing.
Okt 29 15:50:15 hpes samba-ad-dc[5426]: .
Okt 29 15:50:15 hpes systemd[1]: Started LSB: Samba daemons for the AD DC.

Welche Einstellung fehlt noch oder ist falsch?

Viele Dank im Voraus,

Knut Jähnig