Bug 41514 – Replication module does not reconnect if bind failed

Bug 41514 - Replication module does not reconnect if bind failed


Summary:	Replication module does not reconnect if bind failed

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Listener (univention-directory-listener)
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.3-1-errata
Assigned To:	Arvid Requate
QA Contact:	Philipp Hahn

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-06-09 17:18 CEST by Ingo Sieverdingbeck
Modified:	2018-08-29 12:49 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.051
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Flags:	sieverdingbeck: Patch_Available+

Attachments
Reconnect in case of an error (650 bytes, patch) 2016-06-09 17:24 CEST, Ingo Sieverdingbeck	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ingo Sieverdingbeck

2016-06-09 17:18:45 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().

Comment 1 Ingo Sieverdingbeck

2016-06-09 17:24:44 CEST

Created attachment 7730 [details]
Reconnect in case of an error

Comment 2 Stefan Gohmann

2017-06-16 20:40:42 CEST

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.

Comment 3 Arvid Requate

2018-08-20 17:37:05 CEST

9f260031d9 | reconnect in case of an error
4fa8796fdf | version bump
f49f6e7309 | Advisory

Comment 4 Philipp Hahn

2018-08-23 16:34:11 CEST

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

Comment 5 Arvid Requate

2018-08-29 12:49:39 CEST

<http://errata.software-univention.de/ucs/4.3/223.html>