Univention Bugzilla – Bug 40511
Rejoin of UCS Backup with Samba AD - Init of samba4-idmap listener module takes ages
Last modified: 2016-11-07 18:01:55 CET
I re-joined a UCS Backup (4 CPUs, 8 GB RAM) with Samba AD in a UCS@school Multi-Server-Environment with ~19.000 entires in /var/lib/samba/private/idmap.ldb using "univention-join". After more than 2 hours the join was still at 03univention-directory-listener and the initializing of the samba4-idmap listener module: > 26.01.16 09:20:19.476 LISTENER ( WARN ) : initializing module samba4-idmap > [...] > 26.01.16 11:35:35.227 LISTENER ( WARN ) : finished initializing module samba4-idmap I guess the listener module searches in the existing idmap.ldb and checks every single entry for changes. Also very little information is logged and you easily get the impression, that the whole join is stuck. I a second attempt, we moved the existing idmap.ldb: > mv /var/lib/samba/private/idmap.ldb /var/lib/samba/private/idmap.ldb.bak and run "univention-join" again. This time, the join was much faster and initializing the samba4-idmap listener module was done in less than 9 minutes: > 26.01.16 11:52:34.216 LISTENER ( WARN ) : initializing module samba4-idmap > [...] > 26.01.16 12:01:04.114 LISTENER ( WARN ) : finished initializing module samba4-idmap Imho we should remove the idmap.ldb by default.
Happened again: Ticket #2016101121000687 I'll move it to UCS because it is not only a UCS@school issue.
The idmap.ldb database is now removed while initializing the samba4-idmap listener module. 4.1-3: r73188 4.2: r73189 YAML: r73190
Verified root@master10:~# univention-directory-listener-ctrl resync samba4-idmap root@master10:~# ls /var/lib/samba/private/idmap.ldb* /var/lib/samba/private/idmap.ldb /var/lib/samba/private/idmap.ldb_1476721611 Advisory is ok too.
<http://errata.software-univention.de/ucs/4.1/309.html>