Univention Bugzilla – Bug 24522
02univention-directory-notifier.inst fails to start UDL - runsv
Last modified: 2020-07-03 20:55:07 CEST
Folgende Fehlermeldung findet sich im join.log auf einem UCS 3.0-RC amd64 Master: Configure 02univention-directory-notifier.inst Starting Univention Directory Notifier daemon. warning: univention-directory-notifier: unable to open supervise/ok: file does not exist failed.
Das scheint nur ein temporäres Problem zu sein.
UCS-3.0 is OoM. runit will be phased out by systemd anyway: Bug #43687 It's only of cosmetic significance: only "warning". But directly after installation the notifier is not running; only the reboot fixes it. FYI: # mkdir -p /etc/runit/test # touch /etc/runit/test/down # ln -snf /usr/share/univention-runit/sleep-dynamic /etc/runit/test/finish # cat >>/etc/runit/test/run <<__SH__ #!/bin/sh while [ ! -e /tmp/test ] do sleep 10 done __SH__ # chmod +x >>/etc/runit/test/run # ln -snf /etc/runit/test /etc/runit/univention ; sv up test warning: test: unable to open supervise/ok: file does not exist The issue is caused by "runsvdir" not having picked up the new service yet when the "up" is issued. The corresponding "runsv" process has not been started yet: # man 8 runsvdir .. > At least every five seconds runsvdir checks .... So adding a "sleep 5" 8plus error handling) in 02univention-directory-notifier.inst:39 should fix it. FYI: ucs-test/tests/00_base/check_log_files_definitions.py:147 currently ignores that line as the bug is triggered everywhere.
Created attachment 8796 [details] Fix runsv supervision
*** Bug 11889 has been marked as a duplicate of this bug. ***
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.