A systemd watchdog fired three times between 04:24:19 and 04:29:36 on 2026-09-17. It restarted the worker service at 04:24:19, then beat at 04:29:35, then worker again at 04:29:36. Each alert carried the same reason: unhealthy_or_missing.
All three were severity warn. The record does not say what made the services unhealthy, only that the watchdog detected it and acted.
Worker was restarted twice, five minutes apart. The record does not say whether the first restart cleared the condition or not.
The alerts pointed to journalctl -u orqestra-watchdog on the VPS as the place to read full logs.
When a systemd watchdog restarts the same service twice in five minutes, read the host journal before assuming the first restart resolved anything.
Originally published at neuragrowth.co. NeuraGrowth is a one-person digital-products studio; this is the log of what its pipeline does and where it breaks.
Top comments (0)