Univention Bugzilla – Full Text Bug Listing |
Summary: | UMC crashes with broken pipe | ||
---|---|---|---|
Product: | UCS | Reporter: | Dirk Wiesenthal <wiesenthal> |
Component: | UMC (Generic) | Assignee: | Florian Best <best> |
Status: | CLOSED FIXED | QA Contact: | Sönke Schwardt-Krummrich <schwardt> |
Severity: | normal | ||
Priority: | P5 | CC: | best, gohmann, jmm, klaeser |
Version: | UCS 3.2 | Flags: | best:
Patch_Available+
|
Target Milestone: | UCS 4.0-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=37399 | ||
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 | |
Max CVSS v3 score: | |||
Bug Depends on: | |||
Bug Blocks: | 37315 | ||
Attachments: | patch |
Description
Dirk Wiesenthal
2014-07-01 15:32:40 CEST
I noticed these tracebacks when doing the following: 1) firewall blocks appcenter.software-univention.de 2) start app center → initial loading endures >2min 3) restart UMC server within this loading procedure Well yes, it's probably reproducible by making a request which isn't answered immediately while killing the process. At some point the process have to kill itself when receiving SIGINT. What should the desired behavior be? → The module could answer all pending requests with some error like 500 Internal Server Error/etc. Other suggestions? *** Bug 35640 has been marked as a duplicate of this bug. *** *** Bug 33360 has been marked as a duplicate of this bug. *** (In reply to Florian Best from comment #3) > *** Bug 35640 has been marked as a duplicate of this bug. *** See also Bug #35640 comment 1 there? I experienced this error again with the appcenter: MAIN ( INFO ) : The module appcenter is inactive for too long. Sending EXIT request to module PROTOCOL ( INFO ) : Sending UMCP EXIT REQUEST 141203604715722-22 MAIN ( ERROR ) : Traceback (most recent call last): … Created attachment 6357 [details]
patch
Attached a patch for this. This happens when the module exits itself due to session timeout (no incoming requests) while receiving the upstream EXIT request from the UMC-server who wants to do the same.
Package: univention-management-console Version: 7.1.63-2.837.201411201850 User: fbest Branch: ucs_4.0-0 Scope: errata4.0-0 YAML: 2014-11-20-univention-management-console.yaml YAML: 2014-11-20-univention-management-console.yaml Package: univention-management-console Version: 7.1.63-2.837.201411201850 User: fbest Branch: ucs_4.0-0 Scope: errata4.0-0 (In reply to Florian Best from comment #6) > Attached a patch for this. This happens when the module exits itself due to > session timeout (no incoming requests) while receiving the upstream EXIT > request from the UMC-server who wants to do the same. Sounds reasonable. However, I was unable to trigger the error case without the fix. OK: code change OK: functionality (at least I noticed no new problems) OK: YAML This happened today on demo.univention.de. |