Bug 35193 - Delay initialization of unconfigured modules
Delay initialization of unconfigured modules
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
UCS 4.2
All Linux
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
Depends on:
  Show dependency treegraph
Reported: 2014-06-25 08:45 CEST by Philipp Hahn
Modified: 2020-07-03 20:55 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Feature Request
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:


Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2014-06-25 08:45:10 CEST
With OX multiple packages provide their own listener modules and restart the listener multiple times. This leads to the situation where the listener from one package is already unpacked, but its Debian postrun has not yet been executed and the listener is not yet configured or is not yet functional (the listener required uses a shared Python module, which is not yet linked from /usr/shared/pyshared/ to /usr/lib/pymodules/python2.6/ and thus the import fails).

Possible solution:
1. Use a structure similar to /etc/apache2/{sites,modules,conf]-{available,enabled}.d/, where the enabled modules are only linked to /usr/lib/univention-directory-listener/system/ in the post-inst.
2. Use dpkg-trigger to aggregate and delay the listener restarts.
3. Extends the listener to delay the initialization when the import fails.
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:38:19 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 2 Ingo Steuwer univentionstaff 2020-07-03 20:55:53 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.