LDAP / RADIUS lassen sich nicht Starten

Hallo Zusammen,

seit heute morgen sind keine Anmeldungen an Memberservern mehr möglich.
Der Versuch die Dienste zu starten hatten keinen Erfolg.
Gestern waren die Dinste noch erreichbar.
Aufgrund der Informationen hier im Forum habe ich die Zertifikate nach Anleitung überprüft.
In einem der Beiträge wurde gesagt, dass ein gültiges Zertifikat erneuert wurde und danach
der Dienst wieder erreichbar war.

Leider konnte ich nicht herausfinden an welcher Stelle der Fehler liegt.

Aktuell noch UCS 4.4-8

Job for slapd.service failed because the control process exited with error code.
See "systemctl status slapd.service" and "journalctl -xe" for details.
● 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 Fri 2022-07-08 10:19:49 CEST; 1min 9s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 13988 ExecStart=/etc/init.d/slapd start (code=exited, status=1/FAILURE)
      CPU: 278ms

Jul 08 10:31:45 ad dhcpd[17517]: before submitting a bug.  These pages explain the proper
Jul 08 10:31:45 ad dhcpd[17517]: process and the information we find helpful for debugging..
Jul 08 10:31:45 ad dhcpd[17517]:
Jul 08 10:31:45 ad dhcpd[17517]: exiting.
Jul 08 10:31:47 ad nscd[499]: nss-ldap: do_open: do_start_tls failed:stat=-1
Jul 08 10:31:47 ad nscd[499]: nss_ldap: reconnecting to LDAP server...
Jul 08 10:31:47 ad nscd[499]: nss-ldap: do_open: do_start_tls failed:stat=-1
Jul 08 10:31:47 ad nscd[499]: nss_ldap: reconnecting to LDAP server (sleeping 1 seconds)...
Jul 08 10:31:48 ad systemd[1]: freeradius.service: Service hold-off time over, scheduling restart.
Jul 08 10:31:48 ad systemd[1]: Stopped FreeRADIUS multi-protocol policy server.
-- Subject: Unit freeradius.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit freeradius.service has finished shutting down.
Jul 08 10:31:48 ad systemd[1]: Starting FreeRADIUS multi-protocol policy server...
-- Subject: Unit freeradius.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit freeradius.service has begun starting up.
Jul 08 10:31:48 ad freeradius[17524]: FreeRADIUS Version 3.0.12
Jul 08 10:31:48 ad freeradius[17524]: Copyright (C) 1999-2016 The FreeRADIUS server project and contributors
Jul 08 10:31:48 ad freeradius[17524]: There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
Jul 08 10:31:48 ad freeradius[17524]: PARTICULAR PURPOSE
Jul 08 10:31:48 ad freeradius[17524]: You may redistribute copies of FreeRADIUS under the terms of the
Jul 08 10:31:48 ad freeradius[17524]: GNU General Public License
Jul 08 10:31:48 ad freeradius[17524]: For more information about these matters, see the file named COPYRIGHT
Jul 08 10:31:48 ad freeradius[17524]: Starting - reading configuration files ...
Jul 08 10:31:48 ad freeradius[17524]: No 'ipaddr' or 'ipv4addr' or 'ipv6addr' field found in client 192.168.xxx.xxx. Please fix your configuration
Jul 08 10:31:48 ad freeradius[17524]: Support for old-style clients will be removed in a future release
Jul 08 10:31:48 ad freeradius[17524]: No 'ipaddr' or 'ipv4addr' or 'ipv6addr' field found in client 192.168.xxx.xxx. Please fix your configuratio
Jul 08 10:31:48 ad freeradius[17524]: Support for old-style clients will be removed in a future release
Jul 08 10:31:48 ad freeradius[17524]: No 'ipaddr' or 'ipv4addr' or 'ipv6addr' field found in client 192.168.xxx.xxx. Please fix your configuratio
Jul 08 10:31:48 ad freeradius[17524]: Support for old-style clients will be removed in a future release
Jul 08 10:31:48 ad freeradius[17524]: No 'ipaddr' or 'ipv4addr' or 'ipv6addr' field found in client 192.168.xxx.xxx. Please fix your configuratio
Jul 08 10:31:48 ad freeradius[17524]: Support for old-style clients will be removed in a future release
Jul 08 10:31:48 ad freeradius[17524]: Debugger not attached
Jul 08 10:31:48 ad freeradius[17524]: Creating attribute Unix-Group
Jul 08 10:31:48 ad freeradius[17524]: Creating attribute LDAP-Group
Jul 08 10:31:48 ad freeradius[17524]: tls: Using cached TLS configuration from previous invocation
Jul 08 10:31:48 ad freeradius[17524]: rlm_detail (auth_log): 'User-Password' suppressed, will not appear in detail output
Jul 08 10:31:48 ad freeradius[17524]: rlm_mschap (mschap): authenticating by calling 'ntlm_auth'
Jul 08 10:31:48 ad freeradius[17524]: rlm_ldap: libldap vendor: OpenLDAP, version: 20445
Jul 08 10:31:48 ad freeradius[17524]: rlm_ldap (ldap): Initialising connection pool
Jul 08 10:31:48 ad freeradius[17524]: [/etc/freeradius/3.0/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay"
Jul 08 10:31:48 ad freeradius[17524]: [/etc/freeradius/3.0/mods-config/attr_filter/access_reject]:11 Check item "FreeRADIUS-Response-Delay-USec"
Jul 08 10:31:48 ad freeradius[17524]: rlm_cache (cache_eap): Driver rlm_cache_rbtree (module rlm_cache_rbtree) loaded and linked
Jul 08 10:31:48 ad freeradius[17524]: Ignoring "sql" (see raddb/mods-available/README.rst)
Jul 08 10:31:48 ad freeradius[17524]: radiusd: #### Skipping IP addresses and Ports ####
Jul 08 10:31:48 ad freeradius[17524]: Configuration appears to be OK
Jul 08 10:31:48 ad freeradius[17524]: rlm_ldap (ldap): Removing connection pool
Jul 08 10:31:48 ad systemd[1]: freeradius.service: Control process exited, code=exited status=1
Jul 08 10:31:48 ad systemd[1]: Failed to start FreeRADIUS multi-protocol policy server.
-- Subject: Unit freeradius.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit freeradius.service has failed.
--
-- The result is failed.
Jul 08 10:31:48 ad systemd[1]: freeradius.service: Unit entered failed state.
Jul 08 10:31:48 ad systemd[1]: freeradius.service: Failed with result 'exit-code'.
Jul 08 10:31:48 ad nscd[499]: nss-ldap: do_open: do_start_tls failed:stat=-1
Jul 08 10:31:48 ad nscd[499]: nss_ldap: could not search LDAP server - Server is unavailable
Jul 08 10:31:48 ad python2.7[680]: inexistant user ad$
Jul 08 10:31:48 ad python2.7[680]: saml_msg is too small: minlength = 128
Jul 08 10:31:48 ad python2.7[680]: pam_unix(univention-management-console:auth): check pass; user unknown
Jul 08 10:31:48 ad python2.7[680]: pam_unix(univention-management-console:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
Jul 08 10:31:48 ad python2.7[680]: pam_krb5(univention-management-console:auth): user ad$ authenticated as ad$@myserver.com
Jul 08 10:31:48 ad python2.7[680]: pam_unix(univention-management-console:account): could not identify user (from getpwnam(ad$))
Mastodon