Bug 41249 - Keep alive for LDAP/notifier connections
Keep alive for LDAP/notifier connections
Status: CLOSED MOVED
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
UCS 3.2
Other Linux
: P5 enhancement (vote)
: UCS 3.2-8-errata
Assigned To: Philipp Hahn
Arvid Requate
:
Depends on: 34763
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-10 20:14 CEST by Ingo Sieverdingbeck
Modified: 2016-06-01 18:18 CEST (History)
5 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Sieverdingbeck univentionstaff 2016-05-10 20:14:38 CEST
+++ This bug was initially created as a clone of Bug #34763 +++

Ticket#: 2014050721007513

At a customer 5 DC slaves thought they had a valid/established TCP connection to the DC backup port 7389 and were waiting for LDAP search results. But on the DC backup all those TCP connections were unknown and seem to be shut down for some time. Since the slaves do not send any data (waiting for LDAP responses), the will not recognize that the TCP connection is broken and has to be reestablished.


We should activate the TCP keep alive function within listener for notifier/LDAP connections, so the listener is able to detect broken connections.
Comment 1 Philipp Hahn univentionstaff 2016-05-17 12:36:03 CEST
<https://univention.plan.io/issues/5246>