Bug 39619

Summary:	AD Member: join fails "LDAP Error: Can't contact LDAP server" during admember.prepare_administrator
Product:	UCS	Reporter:	Felix Botner <botner>
Component:	AD Connector	Assignee:	Samba maintainers <samba-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	gohmann, michelsmidt
Version:	UCS 4.1
Target Milestone:	---
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=41837
What kind of report is it?:	Bug Report	What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	1: Will affect a very few installed domains	How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.171	Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:
Attachments:	syslog management-console-module-adconnector.log listener.log config-registry.replog

Description Felix Botner

2015-10-22 16:56:51 CEST

w2k12 de vs UCS 4.0-3 errata

* AD member initialization creates group mappings for several objects
* well-known-sid-name-mapping is triggered and runs slapd restart in postrun
* AD member initialization tries to set the UCS Administrator password, but
  the slapd server is now in its "postrun restart" phase

=> Workaround, reconnect in prepare_administrator() on LDAPServerDown

Comment 1 Felix Botner

2015-10-22 16:57:10 CEST

Created attachment 7220 [details]
syslog

Comment 2 Felix Botner

2015-10-22 16:57:35 CEST

Created attachment 7221 [details]
management-console-module-adconnector.log

Comment 3 Felix Botner

2015-10-22 16:57:50 CEST

Created attachment 7222 [details]
listener.log

Comment 4 Felix Botner

2015-10-22 16:58:01 CEST

Created attachment 7223 [details]
config-registry.replog

Comment 5 Felix Botner

2015-10-22 16:58:58 CEST

this is reproducible in my test setup

Comment 6 Stefan Gohmann

2019-01-03 07:23:03 CET

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.