Univention Bugzilla – Full Text Bug Listing |
Summary: | Setup aborts because "connection to the UMC Server broke up unexpectedly" | ||
---|---|---|---|
Product: | UCS | Reporter: | Arvid Requate <requate> |
Component: | System setup | Assignee: | UCS maintainers <ucs-maintainers> |
Status: | RESOLVED WONTFIX | QA Contact: | UCS maintainers <ucs-maintainers> |
Severity: | normal | ||
Priority: | P5 | CC: | best, damrose |
Version: | UCS 4.3 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=48157 | ||
What kind of report is it?: | Bug Report | What type of bug is this?: | 6: Setup Problem: Issue for the setup process |
Who will be affected by this bug?: | 1: Will affect a very few installed domains | How will those affected feel about the bug?: | 3: A User would likely not purchase the product |
User Pain: | 0.103 | 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: | |||
Attachments: | Screenshot |
Description
Arvid Requate
2018-06-21 21:48:52 CEST
I don't really understand the situation: You are on the software selection page. Didn't you do anything there for a long time? This message comes when the UMC-WebServer connection to the UMC-Server breaks (e.g. because the UMC-Server restarts or crashes). Log files would help. > Didn't you do anything there for a long time? Yes, as mentioned in the Description of the bug. The issue is: > I had no way to recover from that (F5 => eternal spinner). (In reply to Arvid Requate from comment #2) > > I had no way to recover from that (F5 => eternal spinner). If F5 doesn't work anymore, it sounds like that the UMC-(Web-)-Server or Apache doesn't run anymore. Maybe it crashed? Is it reliable reproducible? If this happens to you next time, tell me, then I will have a look. Extra information which would help: right click → "Inspect element (Q)" → Select "Console" and make a screenshot of error messages in the console. Same for the "Network" tab. Then we see if there are javascript errors and which requests go wrong (or hang). Not sure, could be related to Bug #48157. This issue has been filed against UCS 4.3. UCS 4.3 is out of maintenance and many UCS components have 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 it and update the UCS version. In this case please provide detailed information on how this issue is affecting you. |