Univention Bugzilla – Full Text Bug Listing |
Summary: | Tracebacks in UMC module init() function are not logged | ||
---|---|---|---|
Product: | UCS | Reporter: | Alexander Kläser <klaeser> |
Component: | UMC (Generic) | Assignee: | Florian Best <best> |
Status: | CLOSED FIXED | QA Contact: | Dirk Wiesenthal <wiesenthal> |
Severity: | normal | ||
Priority: | P5 | CC: | best, gohmann, jmm |
Version: | UCS 3.0 | ||
Target Milestone: | UCS 3.2-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
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: |
Description
Alexander Kläser
2013-12-05 22:42:57 CET
> → usually this entry can be observed in the UMC server log file. The response
> containing the traceback is ignored as invalid as its ID is not in the list of
> known requests. Forcing the server to dump the message, we see the traceback:
Yes, internally there is a SET request send to the Moduleprocess (which is no request from the frontend).
Shouldn't the moduleprocess exit when init() fails?
(In reply to Florian Best from comment #1) > ... > Shouldn't the moduleprocess exit when init() fails? Well, it would be consistent, otherwise side effects may happen unnoticed or they may happen at a later state which will be difficult to recognize. A feedback in form of a traceback is now sent to the client if the initialization of a module fails. YAML: 2013-12-13-univention-management-console.yaml If something went wrong during module initialization (i.e. during "import time"), I get a traceback "ImportError: wizard does not exist" (or something like that). Shortly after that I get a dialogue that the connection is lost and the client is trying to reconnect. Before this change we got "Connection to module process failed". While I like the fact that now a traceback is shown, it is useless in the current form. Please show the correct traceback. Is this "import wizard" really used anywhere or does it only exist to hide the real error? Please also have a look at the dialogue popping up (it better does not!). Maybe it was because I used "?username=Administrator&password=secret"? *** Bug 28746 has been marked as a duplicate of this bug. *** (In reply to Dirk Wiesenthal from comment #4) > If something went wrong during module initialization (i.e. during "import > time"), I get a traceback "ImportError: wizard does not exist" (or something > like that). Shortly after that I get a dialogue that the connection is lost > and the client is trying to reconnect. The import of univention.management.console.wizards.$modulename is not used and has been removed. > Before this change we got "Connection to module process failed". While I > like the fact that now a traceback is shown, it is useless in the current > form. Please show the correct traceback. Is this "import wizard" really used > anywhere or does it only exist to hide the real error? This was a typo, the correct traceback is no shown. > Please also have a look at the dialogue popping up (it better does not!). > Maybe it was because I used "?username=Administrator&password=secret"? This is related to the updater module and would have to be fixed there. univention-management-console 6.0.23-1.773.201312131648 univention-management-console-frontend 3.0.152-8.805.201401141007 OK: * Shows up in logs * Is sent to the frontend * Works for ImportError and __init__() and init() * Module dies reasonably fast so that a new one is usable after a temporary (network) error YAML OK Fix was in svn r46753 and r47061 |