Univention Bugzilla – Bug 48521
Rejoin with failed.ldif not possible
Last modified: 2021-05-14 16:34:26 CEST
If a rejoin of a UCS system (here 4.3-3 DC Slave) is tried where a failed.ldif file exists locally, then the join is going to fail. univention-join stops and starts the slapd at the very beginning of the join process (before the join scripts!). /etc/init.d/slapd tries to import the failed.ldif at startup of slapd. If this does not work, the failed.ldif remains and no PID file for the slapd was created in the affected system. systemd is then apparently unable to restart the slapd without a PID file, which leads to errors in the subsequent join scripts. At the latest when 01univention-ldap-server-init.inst is executed, the LDAP directory is emptied and at the latest now the failed.ldif cannot be imported. If the slapd is not restarted, it runs on all 4 ports (389, 636, 7389, 7636) on UCS@school systems to be installed, which is not compatible with Samba. Possible solution: univention-join should put aside a possibly existing failed.ldif and then try to restart the slapd.
Reported from development and professional services independently (in both cases UCS@school systems). If there are any additional information on why this failed.ldif happened, please attach it to this bug if appropriate or create a new one.
This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.