Bug 33427 – UMC-Server: Restart automatically upon crash

Bug 33427 - UMC-Server: Restart automatically upon crash


Summary:	UMC-Server: Restart automatically upon crash

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-15 15:05 CET by Alexander Kläser
Modified:	2019-01-03 07:17 CET (History)
CC List:	3 users (show)

See Also:	37366 37314 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:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexander Kläser

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

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

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

2015-03-25 12:56:00 CET

We should not restart it if trying to start fails more than twice.

Comment 4 Stefan Gohmann

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.