Contents
Why does systemd not honor the timeout?
Or could it be that the TimeoutStopSec value in the service file does not affect the real timeout when doing a reboot or poweroff and only affects when stopping the service manually via systemctl –user stop? If so, how can I increase the reboot/poweroff timeout? I’m testing this on a current Debian 10.5 installation. Know someone who can answer?
How to change the systemd service timeout value?
Use TimeoutStartSec, TimeoutStopSec or TimeoutSec (more info here) to specify how long the timeout should be for starting & stopping the process. Afterwards, this is how my systemd file looked: You can also view the current Timeout status by running any of these (but you’ll need to edit your service to make changes!
How long does it take for systemd to shutdown?
I have a systemd user service that potentially takes many minutes to properly shutdown. It’s a very large HDF5 database (several GB large) and if the process does not stop cleanly, then the database is corrupt afterwards.
When does systemd shut down in Ubuntu 18.04?
Jun 12 11:54:15 dev.local systemd-shutdownd [3178]: Shutting down at Mon 2017-06-12 20:00:00 CST (poweroff)… On an Ubuntu 18.04 machine shutdown is managed by systemd. On my machine I have enabled automatic reboots via unattended upgrades:
How to set up systemd service to retry 5 times on a…?
I want systemd to start a script and retry a maximum of 5 times, 30s apart. Reading the systemd.service manual and searching the Internet didn’t produce any obvious answers. After much trial and error I solved my problem and thought it worth posting here…
How long does it take systemd service to finish?
Because there’s a lot of computation, this service takes around 70 seconds to finish. I didn’t configure any timeout for systemd, and didn’t change the default configs at /etc/systemd/system.conf, but still when I execute service SERVICE stop my service is timing out after 60 seconds. Checking with journalctl -b -u SERVICE.service I find this log: