Univention Bugzilla – Bug 39795
udm cli should try again in case Master slapd is not available while join script runs
Last modified: 2019-02-06 11:38:40 CET
During UCS 4.1 product tests the join of a UCS memberserver failed like this: ========================================================================== Configure 26univention-nagios-common.inst Thu Nov 5 12:57:22 CET 2015 2015-11-05 12:57:22.112421245+01:00 (in joinscript_init) Object exists: cn=nagios,dc=ar41s4pt1i2,dc=qa Object exists: cn=24x7,cn=nagios,dc=ar41s4pt1i2,dc=qa Object exists: cn=WorkHours,cn=nagios,dc=ar41s4pt1i2,dc=qa Object exists: cn=NonWorkHours,cn=nagios,dc=ar41s4pt1i2,dc=qa Object exists: cn=UNIVENTION_PING,cn=nagios,dc=ar41s4pt1i2,dc=qa Object exists: cn=UNIVENTION_DISK_ROOT,cn=nagios,dc=ar41s4pt1i2,dc=qa Object exists: cn=UNIVENTION_DNS,cn=nagios,dc=ar41s4pt1i2,dc=qa Object exists: cn=UNIVENTION_SWAP,cn=nagios,dc=ar41s4pt1i2,dc=qa authentication error: {'desc': 'Connect error'} Thu Nov 5 12:57:24 CET 2015: finish /usr/share/univention-join/univention-join ========================================================================== Syslog on the master shows that slapd just restarted: ========================================================================== Nov 5 12:57:24 master105 logger: /etc/init.d/slapd graceful-restart (pid: 5196, ppid: 3536 univention-dire) Nov 5 12:57:24 master105 logger: /etc/init.d/slapd graceful-stop (pid: 5204, ppid: 5196 slapd) Nov 5 12:57:24 master105 logger: /etc/init.d/slapd start (pid: 5217, ppid: 5196 slapd) Nov 5 12:57:24 master105 slapd[5228]: @(#) $OpenLDAP: slapd (Oct 31 2015 11:02:56) $#012#011root@ladda:/var/build/temp/tmp.kxy0SdLe0n/pbuilder/openldap-2.4.42+dfsg/debian/build/servers/slapd Nov 5 12:58:00 master105 named[2459]: received control channel command 'reload' ========================================================================== I think in this case (authentication error: {'desc': 'Connect error'}) it would be possible to try again.
My situation may have been special, because another slave might have been joining at the same time. I still have the logs. Felix observed a similar issue during his tests of AD Takeover.
Happened again in a customer scenario while joining a DC backup: Ticket #2016012721000469
See Bug #43975 for a possible duplicate.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.