Bug 46276 - 03univention-directory-listener.inst listener start does not work
03univention-directory-listener.inst listener start does not work
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
UCS 4.3
Other Linux
: P5 normal (vote)
: UCS 4.3
Assigned To: Felix Botner
Stefan Gohmann
: interim-3
Depends on:
  Show dependency treegraph
Reported: 2018-02-12 16:33 CET by Felix Botner
Modified: 2018-03-14 14:38 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
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 Felix Botner univentionstaff 2018-02-12 16:33:39 CET
at the end of 03univention-directory-listener.inst listener the listener is started, but that does not work because systemd thinks it is already started

-> systemctl status univention-directory-listener 
● univention-directory-listener.service - LSB: Univention Directory Listener Daemon
   Loaded: loaded (/etc/init.d/univention-directory-listener; generated; vendor preset: enabled)
   Active: active (exited) since Mon 2018-02-12 16:23:47 CET; 3min 49s ago
     Docs: man:systemd-sysv-generator(8)

-> sv status univention-directory-listener
down: univention-directory-listener: 141s
Comment 1 Felix Botner univentionstaff 2018-02-12 17:13:55 CET
stop and start listener in join script
Comment 2 Stefan Gohmann univentionstaff 2018-02-20 08:54:40 CET
Changelog: Fail, please add a changelog entry.

Tests: OK, it works.

Code review: OK
Comment 3 Felix Botner univentionstaff 2018-02-20 12:18:59 CET
Comment 4 Stefan Gohmann univentionstaff 2018-02-20 13:26:35 CET
Comment 5 Stefan Gohmann univentionstaff 2018-03-14 14:38:18 CET
UCS 4.3 has been released:

If this error occurs again, please use "Clone This Bug".