Bug 39536 – UMC-Webserver: xmlsec1 <defunct>

Bug 39536 - UMC-Webserver: xmlsec1 <defunct>


Summary:	UMC-Webserver: xmlsec1 <defunct>

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-10-14 16:13 CEST by Florian Best
Modified:	2019-01-03 07:21 CET (History)
CC List:	1 user (show)

See Also:	45560
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):
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 Florian Best

2015-10-14 16:13:32 CEST

The UMC-Webserver uses pysaml2 for its SAML service provider implementation.
This spawns subprocesses using xmlsec1.

I saw in my environment some defunct xmlsec1 processes:

root      5651  0.2  2.3 717612 24464 ?        SNl  02:44   0:26 /usr/bin/python2.7 /usr/sbin/univention-management-console-web-server restart
root     18704  0.0  0.0      0     0 ?        ZN   06:10   0:00  \_ [xmlsec1] <defunct>
root     18708  0.0  0.0      0     0 ?        ZN   06:10   0:00  \_ [xmlsec1] <defunct>

Comment 1 Florian Best

2017-01-09 00:51:17 CET

Fixed upstream https://github.com/rohe/pysaml2/commit/dc996f87cfcb0209c7d98bc951569fb595cac2d3

Comment 2 Stefan Gohmann

2019-01-03 07:21:39 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.