Univention Bugzilla – Bug 50022
Listener module well-known-sid-name-mapping.py takes 13-14 seconds for "ucr set"
Last modified: 2019-08-19 15:11:25 CEST
During the analysis of Bug 44278 we found that the listener takes really long to catch up behind the transactions of OpenLDAP server. When looking at the listener.log, it seems like the well-known-sid-name-mapping.py listener module takes quite long for each "ucr set groups/default/...". * I guess on the one hand the listener module could be smarter: It looks like it sets some variables repeatedly. * But also the "ucr commit /etc/ldap/slapd.conf" takes nearly 8 seconds on my vanilla UCS 4.4-1 Master KVM instance. Maybe that can be improved too (would be a seaprate bug)? * The well-known-sid-name-mapping.py listener module could collect all the UCR settings and then actually commit them in the postrun in one atomic step. Part of the listener.log during AD-Takeover: ======================================================================= 19.08.19 14:52:23.379 LISTENER ( PROCESS ) : updating 'cn=Zertifikatherausgeber,cn=groups,dc=adtakeover,dc=local' command m 19.08.19 14:52:23.383 LISTENER ( PROCESS ) : updating 'cn=Abgelehnte RODC-Kennwortreplikationsgruppe,cn=groups,dc=adtakeover,dc=local' command m 19.08.19 14:52:23.387 LISTENER ( PROCESS ) : updating 'uid=gast,cn=users,dc=adtakeover,dc=local' command m 19.08.19 14:52:23.391 LISTENER ( PROCESS ) : updating 'uid=gast,cn=users,dc=adtakeover,dc=local' command m 19.08.19 14:52:23.395 LISTENER ( PROCESS ) : updating 'cn=Domain Guests,cn=groups,dc=adtakeover,dc=local' command r 19.08.19 14:52:23.396 LISTENER ( PROCESS ) : updating 'cn=Domänen-Gäste,cn=groups,dc=adtakeover,dc=local' command a 19.08.19 14:52:23.399 LISTENER ( PROCESS ) : well-known-sid-name-mapping: ucr set groups/default/domainguests=Domänen-Gäste ## Note the time gap here ! 19.08.19 14:52:37.116 LISTENER ( PROCESS ) : samba4-idmap: added entry for S-1-5-21-1290326482-3477815558-1836117412-514 19.08.19 14:52:37.119 LISTENER ( PROCESS ) : well-known-sid-name-mapping: ucr set groups/default/domainguests=Domänen-Gäste ## Note the time gap here ! And why is it setting this again?? 19.08.19 14:52:50.894 LISTENER ( PROCESS ) : samba4-idmap: renaming entry for S-1-5-21-1290326482-3477815558-1836117412-514 to S-1-5-21-3963911642-3967960182-3313604782-514 19.08.19 14:52:50.894 LISTENER ( WARN ) : Entry CN=S-1-5-21-3963911642-3967960182-3313604782-514 already exists 19.08.19 14:52:50.895 LISTENER ( PROCESS ) : samba4-idmap: removing entry for S-1-5-21-1290326482-3477815558-1836117412-514 19.08.19 14:52:50.899 LISTENER ( PROCESS ) : samba4-idmap: modifying entry for S-1-5-21-3963911642-3967960182-3313604782-514 19.08.19 14:52:50.906 LISTENER ( PROCESS ) : updating 'cn=Domänen-Gäste,cn=groups,dc=adtakeover,dc=local' command m 19.08.19 14:52:50.911 LISTENER ( PROCESS ) : updating 'cn=Gäste,cn=Builtin,dc=adtakeover,dc=local' command m 19.08.19 14:52:50.915 LISTENER ( PROCESS ) : updating 'cn=Domain Computers,cn=groups,dc=adtakeover,dc=local' command r 19.08.19 14:52:50.915 LISTENER ( PROCESS ) : updating 'cn=Domänencomputer,cn=groups,dc=adtakeover,dc=local' command a 19.08.19 14:52:50.919 LISTENER ( PROCESS ) : well-known-sid-name-mapping: ucr set groups/default/domaincomputers=Domänencomputer ## Note the time gap here ! 19.08.19 14:53:04.701 LISTENER ( PROCESS ) : samba4-idmap: added entry for S-1-5-21-1290326482-3477815558-1836117412-515 19.08.19 14:53:04.704 LISTENER ( PROCESS ) : well-known-sid-name-mapping: ucr set groups/default/domaincomputers=Domänencomputer =======================================================================