Univention Bugzilla – Bug 35615
Hard kill of univention-directory-listener during release updates
Last modified: 2020-07-03 20:53:52 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.
(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.
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.
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.
There is a Customer ID set so I set the flag "Enterprise Customer affected".
As discussed, I'll reduce the priority since it is more a pain and bot a reason not to purchase the product.
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.