Cairn

Systemd scope mismatch causes false-positive stale-unit warnings

NousResearch/hermes-agent · cluster 36755 · gateway

Data as of

5 open items. Fix attempted, not merged.

The short answer

2open issues
3open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 3 PRs.

A bug where systemd timing/shutdown checks query the wrong scope (user vs. system) or read synthesized defaults for non-existent units, producing false-positive 'stale systemd unit' warnings. Multiple fixes address scoping, unit-loaded state, and default-value handling.

Open issues2

  • Issue#36755bug(diagnostics): check_systemd_timing_alignment false-positive — systemctl show returns default 90s for nonexistent --user unit
  • Issue#61003shutdown_forensics: false-positive 'Stale systemd unit' warning when unit exists in system scope only

Open PRs3

  • PR#36766fix(gateway): skip systemd timing check for non-loaded units
  • PR#37324fix(gateway): ignore unloaded systemd units in forensics
  • PR#61017fix(gateway): honor systemd unit scope in shutdown check

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #57901 Fix systemd timeout check for missing user unit · duplicate → #34734, #36766, #37324, #54396, #36755
  • #61532 fix(gateway): query systemd timeout in owning scope · superseded by another PR → #54396
Closed issues · 1
  • Closed#63158False-positive "Stale systemd unit" warning: timing check reads synthesized defaults from `systemctl --user` for system-scope units
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.22: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/36755.json
cluster/36755.md