Univention Bugzilla – Bug 48613
It's possible to start univention-directory-listener twice
Last modified: 2021-05-14 16:34:42 CEST
I followed https://help.univention.com/t/recreate-listener-cache/6426 to re-initialize the listener. root@master10:~# ps ax | grep list 13116 ? Ss 0:00 runsv univention-directory-listener 13146 pts/1 S 0:03 /usr/sbin/univention-directory-listener -F -b dc=ar41i1,dc=qa -m /usr/lib/univention-directory-listener/system -c /var/lib/univention-directory-listener -d 2 -x -ZZ -D cn=admin,dc=ar41i1,dc=qa -y /etc/ldap.secret -g 13310 pts/1 S 0:00 tail -f /var/log/univention/listener.log In this state (initialization has finished) it's possible to start a second instance (the log output comes from a tail -f running in the background): root@master10:~# /etc/init.d/univention-directory-listener start [ ok ] Starting univention-directory-listener (via systemctl): univention-directory-listener.service. root@master10:~# 23.01.19 16:37:38.282 DEBUG_INIT 23.01.19 16:37:38.291 LISTENER ( WARN ) : Notifier/LDAP server is master10.ar41i1.qa:7389 23.01.19 16:37:38.292 LDAP ( PROCESS ) : connecting to ldap://master10.ar41i1.qa:7389 UNIVENTION_DEBUG_BEGIN : uldap.__open host=master10.ar41i1.qa port=7389 base=dc=ar41i1,dc=qa UNIVENTION_DEBUG_END : uldap.__open host=master10.ar41i1.qa port=7389 base=dc=ar41i1,dc=qa root@master10:~# ps ax | grep list 13116 ? Ss 0:00 runsv univention-directory-listener 13146 pts/1 S 0:03 /usr/sbin/univention-directory-listener -F -b dc=ar41i1,dc=qa -m /usr/lib/univention-directory-listener/system -c /var/lib/univention-directory-listener -d 2 -x -ZZ -D cn=admin,dc=ar41i1,dc=qa -y /etc/ldap.secret -g 13310 pts/1 S 0:00 tail -f /var/log/univention/listener.log 14872 ? S 0:01 /usr/sbin/univention-directory-listener -F -d 2 -b dc=ar41i1,dc=qa -m /usr/lib/univention-directory-listener/system -c /var/lib/univention-directory-listener -ZZ -x -D cn=admin,dc=ar41i1,dc=qa -y /etc/ldap.secret No clue what it does, but IIRC there should be some locking and some checks to avoid this.
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.