Adding --background to the start-stop-daemon command in the init script
seems to get around the issue.
start-stop-daemon --background --start -c tenshi --pidfile $PIDFILE
--startas $DAEMON -- -P $PIDFILE
This is documented as a "last resort" by start-stop-daemon. Maybe there
is a better solution.
Here is a startup hang and status on a 16.04 system. Identical behavior
on a 18.04 fresh install.
sudo service tenshi start
Job for tenshi.service failed because a timeout was exceeded. See "systemctl
status tenshi.service" and "journalctl -xe" for details.
● tenshi.service - LSB: tenshi log
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tenshi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819434
Title:
ten
Also fails on 16.04. Hanging on multiple installations.
After reboot, tenshi does not start automatically. But manually
starting it and waiting past the timeout, the tenshi tasks do start, and
tenshi apparently works fine, sending the expected log monitoring
messages.
--
You received this bug n
Removing the package after the failed install is not straight forward, here is
a workarond:
sudo systemctl stop tenshi.service; sudo killall tenshi; sudo apt purge
tenshi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
