Bug 41681 – log segfaults of UMC (module) processes

Bug 41681 - log segfaults of UMC (module) processes


Summary:	log segfaults of UMC (module) processes

Status:	RESOLVED WONTFIX

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

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-06-28 13:11 CEST by Florian Best
Modified:	2019-01-03 07:19 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	5: Will affect all installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.057
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Cleanup, Error handling
Max CVSS v3 score:

Flags:	best: Patch_Available+

Attachments
patch (1.55 KB, patch) 2016-06-28 13:11 CEST, Florian Best	Details \| Diff
View All 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 Florian Best

2016-06-28 13:11:53 CEST

Created attachment 7770 [details]
patch

It would be useful if we would write the python-traceback of all threads to the logfile(s) of UMC when a segfault occurs. This is especially useful when segfaults occur e.g. due to the italc code in the UMC computerroom module.

Attached is a patch which does this.

Comment 1 Florian Best

2016-11-25 12:00:28 CET

python-faulthandler is part of unmaintained.

Comment 2 Stefan Gohmann

2019-01-03 07:19:07 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 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.