Bug 42868 - LDAP reconnect handling
LDAP reconnect handling
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: univention-lib
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-08 07:00 CET by Stefan Gohmann
Modified: 2019-01-03 07:17 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
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 Stefan Gohmann univentionstaff 2016-11-08 07:00:59 CET
It looks like we have a lot of LDAP server reconnect issues at least in our Jenkins test environments:
 - Bug #39810
 - Bug #38312
 - Bug #42867
 - Bug #40259

My suggestion is to increase the client connection attempt number. If it doesn't help, we should re-check the reconnect handling. Maybe it won't reconnect in some cases.
Comment 1 Stefan Gohmann univentionstaff 2016-11-08 07:08:03 CET
r74184:
Check if the Jenkins results are better if we increase ldap/client/retry/count to 40 (Bug #42868)
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:17:53 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.