Univention Bugzilla – Bug 41514
Replication module does not reconnect if bind failed
Last modified: 2018-08-29 12:49:39 CEST
If the bind during connect() in replication.py fails but open for the connection was successful, the connection is not rebuild during the connect() retry but used without successful bind after a 10s sleep. This seems to be caused by the condition 'connection and not reconnect' in connect(), which evaluates to True in this case. To solve this it could be enough to set reconnect=1 in handler() in case of an exception during connect().
Created attachment 7730 [details] Reconnect in case of an error
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4. If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
9f260031d9 | reconnect in case of an error 4fa8796fdf | version bump f49f6e7309 | Advisory
OK: 9f260031d9 4fa8796fdf f49f6e7309 ~OK: sed -i -e '1i rootpw "XXXXXXXX"' /etc/ldap/rootpw.conf pkill -SIGHUP -f /usr/sbin/univention-directory-listener service univention-directory-listener restart tail -f /var/log/univention/listener.log udm "computers/$(ucr get server/role)" modify --dn "$(ucr get ldap/hostdn)" --set description="$(date)" OK: errata-announce univention-directory-replication.yaml OK: apt install univention-directory-replication OK: univention-directory-replication.yaml
<http://errata.software-univention.de/ucs/4.3/223.html>