MC-4442 — [watchdog:missed:systemd-watchdog] Task didn't fire: systemd-watchdog

Home Board MC-4442

[watchdog:missed:systemd-watchdog] Task didn't fire: systemd-watchdog

Task `systemd-watchdog` (systemd Service Watchdog) has a cron schedule of `0 * * * *`. The previous expected fire was at **2026-05-30 08:00 UTC+02:00** (more than 15 min ago), b...

State Done Next Action Closed Owner Luci Runtime Closed Age 14d ago

Description

MC-4442

Task `systemd-watchdog` (systemd Service Watchdog) has a cron schedule of `0 * * * *`. The previous expected fire was at **2026-05-30 08:00 UTC+02:00** (more than 15 min ago), but `task_runs` has no entry since then. Last actual run: **2026-05-30 06:05:43** Task file: `~/workspace/tasks/systemd-watchdog.md` Investigate: is the task enabled? Is the schedule correct? Is there a lock or prerequisite blocking it?

Activity

done

Luci is working...

Details — Done · Medium · Luci ▼

State

Done

Closed

State

Priority

People

Owner (assigned to)

Controller

Timing / Details

Due Date

Snooze

Source scheduler-watchdog (scheduled)

Project infra

Created 14d ago

Updated 14d ago

Advanced / Operator evidence

Routing owner

Routes via

Operator console

Evidence

Ticket is done; runtime is closed. MC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here.

Workflow

Start Dev Review + QA ▾

Select phases to include:

Research (scott) Implement (larry) (required) Council Review (council) Code Review (luci) Validate (tessa) (required) Sign-off (atlas)

Agents

Review Gates

Decision

WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.