Univention Bugzilla – Bug 46290
univention-reload-service uses sv up
Last modified: 2018-04-06 22:09:02 CEST
The init script uses sv up instead of sv start. Thus, it happens that the service is not listed as started on slow systems.
In addition, the service should require the start of univention-runit.
Created attachment 9388 [details]
Created attachment 9389 [details]
"service univention-reload-service stop" and "service univention-reload-service restart" didn't work at all...
* patch applied
* also s/down/stop/
* added package dependency (on univention-runit)
* merged to 4.3
[4.2 3793a064] Bug #46290: give runsv time to recognize process state
[4.2 423207e7] Bug #46290: changelog, advisory
[4.3 9339fe1d] Bug #46290: give runsv time to recognize process state
(cherry picked from commit 3793a06)
[4.3 cdc1452e] Bug #46290: changelog
[4.2 0bb18fdd] Bug #46290: advisory update
It looks like we need for the customer and the slow systems to increase the sv timeout from 7 to 30 seconds. Can you change the line
sv start univention-reload-service
sv -w 30 start univention-reload-service
[4.2 3d93de04] Bug #46290: raise timeout to 30s
[4.2 4a07b30b] Bug #46290: copyright
[4.2 fe0a58f5] Bug #46290: advisory update
[4.3 cfad674e] Bug #46290: raise timeout to 30s
What I tested:
systemctl stop univention-reload-service.service -> OK
systemctl start univention-reload-service.service -> OK
systemctl restart univention-reload-service.service -> OK
yaml -> OK
UCS@school 4.2 v8 has been released.
If this error occurs again, please clone this bug.