How can I configure a systemd service to restart periodically?

青春壹個敷衍的年華 提交于 2019-12-02 15:30:12

Yes, you can make your service to restart it periodically by making your service of Type=notify. Add this option in [Service] section of your service file along with Restart=always and give WatchdogSec=xx, where xx is the time period in second you want to restart your service. Here your process will be killed by systemd after xx time period and will be restarted by systemd again. for eg.

[Unit]
.
.

[Service]
Type=notify
.
.
WatchdogSec=10
Restart=always
.
.

[Install]
WantedBy= ....

This may not have been present at the time the question was asked, but there is now an option called RuntimeMaxSec, which terminates the service after it has been running for the given period of time.

e.g.

[Service]
Restart=always
RuntimeMaxSec=604800

To me this seems more elegant than abusing Type=notify and WatchdogSec.

matmat

I saw a solution here that seemed elegant, if a bit roundabout. The key idea is to create a one-shot service triggered by a timer that restarts another service.

For the timer:

[Unit]
Description=Do something daily

[Timer]
OnCalendar=daily
Persistent=true

[Install]
WantedBy=timers.target

For the one-shot service:

[Unit]
Description=Restart service

[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl try-restart my_program.service

For the one-shot service on Ubuntu 16.04 LTS:

[Unit]
Description=Restart service

[Service]
Type=oneshot
ExecStart=/bin/systemctl try-restart my_program.service

This solution lets you leverage systemd's timers, including the ability to restart the service at a particular time of day, and not just after some amount of time has elapsed.

How about a crontab like

30 3 * * sun /bin/systemctl restart yourService

which would restart the service yourService at 3:30am each Sunday.

Just some alternate approaches to ultimately reach the same goal:

  • if you have control over the service implementation you could make it end voluntarily after a while, for example either plain exiting after a certain number of iterations (if applicable) or using a timeout timer with a handler sendin itself a SIGTERM/SIGKILL
  • if voluntary service ending is not feasible/practical you could have a small cron-based script killing the service process(es).

Wanted to comment on the

[Service]
Restart=always
RuntimeMaxSec=604800

answer above but can't w/o more points.

Comment is that this solution will invoke failure handling set by OnFailure=failure_handling.service. Since the scheduled restart isn't a real failure any logging, notifications, etc. from the failure handling service will be unwanted and probably disruptive.

An actual periodic restart would be a sensible feature for systemd, but I won't hold my breath.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!