Bug 35615 - Hard kill of univention-directory-listener during release updates
Summary: Hard kill of univention-directory-listener during release updates
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
Version: UCS 4.2
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-15 10:20 CEST by Sönke Schwardt-Krummrich
Modified: 2020-07-03 20:53 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.114
Enterprise Customer affected?: Yes
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID: 00009
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 Sönke Schwardt-Krummrich univentionstaff 2014-08-15 10:20:55 CEST 
A customer in a larger environment (>50.000 users) noticed that during the update some new listener modules have been installed via several packages. Each package restarted the listener process that began to initialize the new listener module.
But before the initialization has been finished, the next package installed a new listener module and forced a restart of the listener by killing it (signal 9) after a certain timeout.
This way, the new modules had to be initialized several times which
a) increased the processing time
b) the init process gets killed hard which may cause problems because auf 
   "half handled objects" or corrupt data.
Comment 1 Moritz Muehlenhoff univentionstaff 2014-08-15 11:59:15 CEST 
(In reply to Sönke Schwardt-Krummrich from comment #0)
> A customer in a larger environment (>50.000 users) noticed that during the
> update some new listener modules have been installed via several packages.
> Each package restarted the listener process that began to initialize the new
> listener module.

We should use a dpkg trigger for listener modules.
Comment 2 Stefan Gohmann univentionstaff 2017-04-18 08:01:13 CEST 
The School Customer affected flag is set but neither a Ticket number is referenced nor a Customer ID is set. Please set a Ticket number or a Customer ID. Otherwise the School Customer affected flag will be reset.
Comment 3 Stefan Gohmann univentionstaff 2017-06-16 20:39:58 CEST 
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 4 Florian Best univentionstaff 2017-06-28 14:52:03 CEST 
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 5 Stefan Gohmann univentionstaff 2017-09-15 20:46:43 CEST 
As discussed, I'll reduce the priority since it is more a pain and bot a reason not to purchase the product.
Comment 6 Ingo Steuwer univentionstaff 2020-07-03 20:53:52 CEST 
This issue has been filed against UCS 4.2.

UCS 4.2 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.