Bug 33427

Summary: UMC-Server: Restart automatically upon crash
Product: UCS Reporter: Alexander Kläser <klaeser>
Component: UMC (Generic)Assignee: UMC maintainers <umc-maintainers>
Status: RESOLVED WONTFIX QA Contact:
Severity: enhancement    
Priority: P5 CC: best, gohmann, kramer
Version: UCS 4.0   
Target Milestone: UCS 4.0-x   
Hardware: Other   
OS: Linux   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=37366
https://forge.univention.org/bugzilla/show_bug.cgi?id=37314
https://forge.univention.org/bugzilla/show_bug.cgi?id=39909
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): Usability
Max CVSS v3 score:

Description Alexander Kläser univentionstaff 2013-11-15 15:05:54 CET 
It would be nice to restart the UMC automatically in case the server process dies (e.g., via runit).
Comment 1 Alexander Kläser univentionstaff 2013-11-15 15:06:36 CET 
Currently, it is not obvious to the user that the UMC server process needs to be restarted.
Comment 2 Alexander Kläser univentionstaff 2015-03-25 09:24:37 CET 
I tag this to errata milestone as it will avoid that users run into problems with the server process being stopped. However, in order to be able to improve the UMC server components, we of course need to log traceback messages. Maybe we can think of some mechanism for letting users report these crashes directly.
Comment 3 Florian Best univentionstaff 2015-03-25 12:56:00 CET 
We should not restart it if trying to start fails more than twice.
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:17:06 CET 
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.