Univention Bugzilla – Bug 45905
slapd and listener are not started during UCS 4.3 master setup
Last modified: 2018-03-14 14:38:17 CET
slapd is not started during UCS 4.3 DC master setup: root@unassigned-hostname:~# tail -n 4 /usr/lib/univention-install/01univention-ldap-server-init.inst invoke-rc.d slapd start joinscript_save_current_version exit 0 root@unassigned-hostname:~# invoke-rc.d slapd start Running in chroot, ignoring request. root@unassigned-hostname:~#
Fixed: https://git.knut.univention.de/univention/ucs/commit/ae636e1b061653677dca5b3128982295040c6a8e * Use service instead of invoke-rc.d since systemd policy layer Changelog missing.
The same happens to the listener: univention-directory-notifier: * Use service instead of invoke-rc.d since systemd policy layer prevents starting services in a chroot environment (Bug #45905) https://git.knut.univention.de/univention/ucs/commit/0a083a5fea01efcebd3f125021ea29d82c687855
And bind: univention-bind: * Use service instead of invoke-rc.d since systemd policy layer prevents starting services in a chroot environment (Bug #45905) https://git.knut.univention.de/univention/ucs/commit/ea8dc103fad66b36e879d5f2f645b315ca5a2499
It seems a lot of services are affected by this. Can't we change the systemd policy layer instead so that it allows starting services in chroot during the initial system installation?
univention-heimdal: https://git.knut.univention.de/univention/ucs/commit/c7cef1598425bdb465ba0487b960d386e39d2df6 univention-appcenter: https://git.knut.univention.de/univention/ucs/commit/2ba7d23d0ded4da8c60098d6338efa8b9e44fa50
Changelog added: https://git.knut.univention.de/univention/ucs/commit/4d93bb943d5338dde16ba05d1d15b13a3666eac6 The packages <package>univention-ldap</package>, <package>univention-directory-notifier</package>, <package>univention-bind</package>, <package>univention-heimdal</package> and <package>univention-appcenter</package> now use the command <command>service</command> instead of <command>invoke-rc.d</command> to restart services. This is necessary for the services to be restarted during the UCS installation (<u:bug>45905</u:bug>). (In reply to Florian Best from comment #4) > It seems a lot of services are affected by this. Can't we change the systemd > policy layer instead so that it allows starting services in chroot during > the initial system installation? That would also start a lot of other services. I don't think it would be a good idea.
OK - setup OK - changelog
UCS 4.3 has been released: https://docs.software-univention.de/release-notes-4.3-0-en.html https://docs.software-univention.de/release-notes-4.3-0-de.html If this error occurs again, please use "Clone This Bug".