Univention Bugzilla – Full Text Bug Listing |
Summary: | LDAP connection invalid | ||
---|---|---|---|
Product: | UCS | Reporter: | Florian Best <best> |
Component: | UMC - Domain management (Generic) | Assignee: | Florian Best <best> |
Status: | CLOSED FIXED | QA Contact: | Alexander Kramer <kramer> |
Severity: | normal | ||
Priority: | P5 | CC: | gohmann, walkenhorst |
Version: | UCS 4.0 | Flags: | best:
Patch_Available-
|
Target Milestone: | UCS 4.0-3-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: |
https://forge.univention.org/bugzilla/show_bug.cgi?id=44013 https://forge.univention.org/bugzilla/show_bug.cgi?id=44735 |
||
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): | Error handling, External feedback | |
Max CVSS v3 score: | |||
Attachments: | patch for UMC-server |
Description
Florian Best
2015-04-24 11:17:18 CEST
Reported again, 4.0-1 errata160 (Walle), udm/get users/user I have a system where I see a similar exception in the stdout of umc-server: 10.05.15 15:01:02.443 MAIN ( PROCESS ) : Processor: dying 10.05.15 15:01:02.443 MAIN ( PROCESS ) : Processor: dying Exception ldap.LDAPError: LDAPError('LDAP connection invalid',) in <bound method Processor.__del__ of <univention.management.console.protocol.session.Processor object at 0x2c68ad0>> ignored 10.05.15 15:01:03.444 SSL ( WARN ) : SSL error in _receive: (-1, 'Unexpected EOF'). Probably the socket was closed by the client. 10.05.15 15:01:03.444 MAIN ( PROCESS ) : Processor: dying 10.05.15 15:01:03.445 MAIN ( PROCESS ) : Processor: dying Exception ldap.LDAPError: LDAPError('LDAP connection invalid',) in <bound method Processor.__del__ of <univention.management.console.protocol.session.Processor object at 0x2c77190>> ignored Created attachment 6915 [details]
patch for UMC-server
The patch for the UMC-server part (which is not critical as it happens in destructor).
>>> import univention.admin.uldap >>> lo, po = univention.admin.uldap.getMachineConnection() >>> lo.lo.lo <ldap.ldapobject.ReconnectLDAPObject instance at 0x7f24dac14c68> >>> lo.lo.lo.unbind() >>> lo.lo.lo.unbind() Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 597, in unbind return self.unbind_ext(None,None) File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 588, in unbind_ext return self._ldap_call(self._l.unbind_ext,RequestControlTuples(serverctrls),RequestControlTuples(clientctrls)) File "/usr/lib/python2.7/dist-packages/ldap/ldapobject.py", line 106, in _ldap_call result = func(*args,**kwargs) ldap.LDAPError: LDAP connection invalid > Stefan changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Flags| |Patch_Available+
The patch is only for the UMC-Server part, not for UDM.
Reported again, 4.0-2 errata231 (Walle) udm/syntax/choices/info shares/share Reported again, 4.0-2 errata263 (Walle) udm/syntax/choices/info computers/computer Reported again, 4.0-2 errata264 (Walle) udm/syntax/choices/info users/user Reported again with the following remark: Die Bearbeitungsmaske des Benutzers war offen, aber es war keine Primäre Gruppe eingetragen. Ich konnte auch keine auswählen über die Dropdown-Liste. Ich habe das Bearbeiten abgebrochen, den Benutzer neu geöffnet und dann war die Primäre Gruppe "Domain Admins" wieder aufgeführt. 1) Schritte, um den Fehler zu reproduzieren Aufruf eines Benutzers mit gleichen Gruppen wie "Administrator" in der UMC 2) erwartetes Ergebnis Bearbeitung des Benutzers. 3) beobachtetes Ergebnis Fehlermeldung der UMC, sonst nichts. Reported again, 4.0-3 errata285 (Walle) I could not find the cause of this problem :( but at least I know how to trigger it manually to reproduce the problem: unbind()ing the ldap connection. Add the following line to e.g. the get() method in /usr/share/pyshared/univention/management/console/modules/udm/udm_ldap.py:631 + ldap_connection.lo.lo.unbind() return obj univention-management-console-module-udm (5.1.25-84): r63137 | Bug #38346: reexecute function if the ldap connection gets broken 2015-06-23-univention-management-console-module-udm.yaml: r63138 | YAML Bug #38346 I fixed this already yesterday in UCS 4.1 but the code branches are different. So no merge of svn r63137. As for the fix I assumed for the QA that the bug is related to the ReconnectLDAPObject class (see initial post above) and used the following line inside udm_ldap.py to provoke the behavior: ldap_connection.lo.lo.unbind() UCS 4.0-3 OK - FIXED: No more traceback if a user has the same group-membership as the admin OK - debian/changelog OK - yaml file UCS 4.1-0 OK - FIXED: No more traceback if a user has the same group-membership as the admin FYI: No debian/changelog because this bug was fixed with another commit r63118 FYI: No need for doc/changelog entry Reported again, 4.0-3 errata285 (Walle) Reported again, 4.0-3 errata313 (Walle) Reported again, 4.0-3 errata295 Reported again, 4.0-3 errata295 (Walle) Reported again, 4.0-3 errata342 (Walle) Reported again, 4.0-3 errata342 (Walle) Reported again, 4.0-3 errata336 (Walle) |