On 2026-09-25 the host watchdog on our VPS restarted two services, and the only place the details live is the systemd journal.
The alerts were three, all severity warn. Each said the service was flagged unhealthy and the host watchdog restarted it. Reason: unhealthy_or_missing. That was worker at 14:28:56, then beat at 22:49:31, then worker again at 22:49:32.
The last two are one second apart. The record does not say whether the two are related.
The reason string is unhealthy_or_missing. The alert does not say which it was for either service, and we have not written down why.
We are not going to guess at a cause here. The facts we have are the service names, the timestamps, the shared reason string and the pointer to the journal.
When a watchdog reports a reason that covers more than one failure, treat the alert as a pointer to the journal and read the unit's logs before you decide what went wrong.
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)