如何解决服务在非常快速的重启调用后卡住失败
在非常快速的重启请求之后服务停留在 failed
上,直到另一个重启调用
玩弄 systemd 配置文件(下面的最后一次迭代)没有解决问题
应用:kismet
systemctl 配置文件:
[Service]
ExecStart=
ExecStart=/usr/bin/kismet --no-ncurses --no-logging
TimeoutStopSec=1
RemainAfterExit=no
Restart=always
RestartSec=5s
#TimeoutStartFailureMode=2
KillMode=control-group
复制:
运行 while true; do systemctl restart kismet.service; sleep 0.01; done
几秒钟然后停止
结果:
kismet.service - Kismet
Loaded: loaded (/lib/systemd/system/kismet.service; disabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/kismet.service.d
└─override.conf
Active: failed (Result: signal) since Sat 2021-03-13 20:35:12 IST; 2min 58s ago
Process: 3423 ExecStart=/usr/bin/kismet --no-ncurses --no-logging (code=killed,signal=KILL)
Main PID: 3423 (code=killed,signal=KILL)
Mar 13 20:35:13 enforceair-0002 systemd[1]: Failed to start Kismet.
Mar 13 20:35:13 enforceair-0002 systemd[1]: Stopped Kismet.
Mar 13 20:35:13 enforceair-0002 systemd[1]: kismet.service: Start request repeated too quickly.
Mar 13 20:35:13 enforceair-0002 systemd[1]: Failed to start Kismet.
Mar 13 20:35:13 enforceair-0002 systemd[1]: Stopped Kismet.
Mar 13 20:35:13 enforceair-0002 systemd[1]: kismet.service: Start request repeated too quickly.
Mar 13 20:35:13 enforceair-0002 systemd[1]: Failed to start Kismet.
Mar 13 20:35:13 enforceair-0002 systemd[1]: Stopped Kismet.
Mar 13 20:35:13 enforceair-0002 systemd[1]: kismet.service: Start request repeated too quickly.
Mar 13 20:35:13 enforceair-0002 systemd[1]: Failed to start Kismet.
恢复:
再运行一轮systemctl restart kismet.service
问题是:如何从失败中自动恢复?
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。