Univention Bugzilla – Full Text Bug Listing |
Summary: | cherrypy.TimeoutError | ||
---|---|---|---|
Product: | UCS | Reporter: | Tim Petersen <petersen> |
Component: | UMC (Generic) | Assignee: | UMC maintainers <umc-maintainers> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | CC: | best, geerds, gohmann, klaeser |
Version: | UCS 3.1 | ||
Target Milestone: | UCS 3.x | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: |
https://forge.univention.org/bugzilla/show_bug.cgi?id=34753 https://forge.univention.org/bugzilla/show_bug.cgi?id=34989 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): | External feedback, Usability | |
Max CVSS v3 score: |
Description
Tim Petersen
2013-05-24 12:20:35 CEST
Good catch. I think we have some more timeout issues in this area, see also Bug #24852. Can we simple increase the timeout? (In reply to comment #1) > Good catch. > > I think we have some more timeout issues in this area, see also Bug #24852. Can > we simple increase the timeout? Another example is Bug 25465. Increasing the timeout does not solve the root of the problem. Ideally, we would need a sort of progress handling for calls that may take more time than a few seconds. We received a feedback containing the same cherrypy.TimeoutError traceback with remark [#2014051921008964]: Beim Aufruf der App-Verwaltung aufgetreten. (In reply to Florian Best from comment #3) > We received a feedback containing the same cherrypy.TimeoutError traceback > with remark [#2014051921008964]: > Beim Aufruf der App-Verwaltung aufgetreten. We received it 3 times from different mail addresses. Another Remark: app center lässt sich nicht aufrufen (In reply to Alexander Kläser from comment #2) > (In reply to comment #1) > > Good catch. > > > > I think we have some more timeout issues in this area, see also Bug #24852. Can > > we simple increase the timeout? > > Another example is Bug 25465. Increasing the timeout does not solve the root > of the problem. Ideally, we would need a sort of progress handling for calls > that may take more time than a few seconds. Yes, IMHO we should not have commands which aren't answered immediately (thats also against HTTP design). Reported by: 3.2-3 errata181 (Borgfeld) Remark: SBS2003 + UCS Server Reported by: 3.2-3 errata182 (Borgfeld) Remark: Active Directory-Verbindung SBS2003 Windows 2000 Modus We received the following traceback: UCS Version: undefined Unrecoverable error in the server. TimeoutError raise cherrypy.TimeoutError() File "/usr/lib/pymodules/python2.6/cherrypy/_cprequest.py", line 567, in run response = self.request.run(meth, path, qs, rproto, headers, rfile) File "/usr/lib/pymodules/python2.6/cherrypy/_cpwsgi.py", line 219, in get_response s, h, b = self.get_response() File "/usr/lib/pymodules/python2.6/cherrypy/_cpwsgi.py", line 79, in setapp Traceback (most recent call last): Unrecoverable error in the server. last traceback reported again (UCS 3.2) Reported again, 3.2-6 errata376 (Borgfeld) This issue has been filed against UCS 3.1. UCS 3.1 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 reopen this bug. In this case please provide detailed information on how this issue is affecting you. |