Bug 34753
| Summary: | problems in UMC during "long" LDAP operation | ||
|---|---|---|---|
| Product: | UCS | Reporter: | Daniel Orrego <orrego> |
| Component: | UMC - LDAP directory | Assignee: | UMC maintainers <umc-maintainers> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | best, gohmann, wiesenthal |
| Version: | UCS 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| See Also: |
https://forge.univention.org/bugzilla/show_bug.cgi?id=33183 https://forge.univention.org/bugzilla/show_bug.cgi?id=31505 https://forge.univention.org/bugzilla/show_bug.cgi?id=35052 |
||
| 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): | Roadmap discussion (moved) | |
| Max CVSS v3 score: | |||
See Bug#33183 for a solution. Moving 10k users should work - and this mechanism could be applied to deletion as well 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. This issue has been filed against UCS 3.2. UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you. |
This was testing the UMC LDAP module (UCS 3.2-1-errata102) * Deleting a list of 10K users was first interrupted after about 5 min. (~4000 deletions), the order has to be given again. This is the first error: ---[UMC] An unknown error with status code 502 occurred while connecting to the server, please try again later. --- * Later, there is a second timeout, and it shows this traceback (although it manages to finish the operation): ---[UMC]: Internal server error. Unrecoverable error in the server. Traceback (most recent call last): File "/usr/lib/pymodules/python2.6/cherrypy/_cpwsgi.py", line 79, in setapp s, h, b = self.get_response() File "/usr/lib/pymodules/python2.6/cherrypy/_cpwsgi.py", line 219, in get_response response = self.request.run(meth, path, qs, rproto, headers, rfile) File "/usr/lib/pymodules/python2.6/cherrypy/_cprequest.py", line 567, in run raise cherrypy.TimeoutError() TimeoutError --- ---[LOGS] ==> /var/log/univention/management-console-server.log <== 06.05.14 09:58:59.826 SSL ( WARN ) : SSL error in _receive: (-1, 'Unexpected EOF'). Probably the socket was closed by the client. 06.05.14 09:58:59.954 MAIN ( WARN ) : Socket died (module=udm) 06.05.14 09:58:59.954 MAIN ( WARN ) : Module process udm died (pid: 8940, exit status: -1, signal: -1) 06.05.14 09:58:59.954 MAIN ( WARN ) : Cleaning up requests 06.05.14 09:58:59.954 MAIN ( WARN ) : Remove inactivity timer 06.05.14 09:58:59.954 MAIN ( PROCESS ) : ModuleProcess: child died ==> /var/log/univention/management-console-module-udm.log <== 06.05.14 09:58:59.926 MAIN ( WARN ) : Shutting down all open connections --- Same traceback is in Bug #31505