heartbeat 服务在几次重启后没有启动，因为它似乎达到了定义的最大限制。从 /var/log/messages 和 system heartbeat status，我发现了以下输出。如果已经达到最大尝试次数，如何在不重启服务器的情况下启动服务，因为我无法重启服务器，因为它是 prod 框。
May 30 05:18:11 servername.domain.com heartbeat: Exiting: error loading config file: yaml: line 19: did not find expected key
May 30 05:18:11 servername.domain.com systemd: heartbeat.service: main process exited, code=exited, status=1/FAILURE
May 30 05:18:11 servername.domain.com systemd: Unit heartbeat.service entered failed state.
May 30 05:18:11 servername.domain.com systemd: heartbeat.service failed.
May 30 05:18:11 servername.domain.com systemd: heartbeat.service holdoff time over, scheduling restart.
May 30 05:18:11 servername.domain.com systemd: start request repeated too quickly for heartbeat.service
May 30 05:18:11 servername.domain.com systemd: Failed to start heartbeat.
May 30 05:18:11 servername.domain.com systemd: Unit heartbeat.service entered failed state.
May 30 05:18:11 servername.domain.com systemd: heartbeat.service failed.
May 30 05:20:01 servername.domain.com systemd: Started Session 194726 of user root.
May 30 05:20:01 servername.domain.com systemd: Starting Session 194726 of user root.
请提出启动和运行该服务的方法。
最佳答案
要实现这一点，您可以使用:
systemctl 重置失败。
关于linux - 在超过 StartLimitBurst 后启动 linux 服务的解决方法，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/44261307/