# NousResearch/hermes-agent · Systemd scope mismatch causes false-positive stale-unit warnings

## Open now

- 2 issues, 3 PRs open on GitHub.
- #36755: bug(diagnostics): check_systemd_timing_alignment false-positive — systemctl show returns default 90s for nonexistent --user unit
- #61003: shutdown_forensics: false-positive 'Stale systemd unit' warning when unit exists in system scope only
- PR #36766: fix(gateway): skip systemd timing check for non-loaded units
- PR #37324: fix(gateway): ignore unloaded systemd units in forensics
- PR #61017: fix(gateway): honor systemd unit scope in shutdown check

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.

## TL;DR

- 8 member(s): 2 open issue(s), 1 closed issue(s), 3 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): 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 member 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.

## Open related issues

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

## Closed / duplicate issues

- #63158: False-positive "Stale systemd unit" warning: timing check reads synthesized defaults from \`systemctl --user\` for system-scope units

## Prior & competing PRs

- **#61532: fix(gateway): query systemd timeout in owning scope**. closed without merge · fix tier `suggested`
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#54396`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#36766: fix(gateway): skip systemd timing check for non-loaded units**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `c9df4bc094fb`
  - files: `gateway/shutdown_forensics.py`, `tests/gateway/test_shutdown_forensics.py`
- **#37324: fix(gateway): ignore unloaded systemd units in forensics**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `gateway/shutdown_forensics.py`, `tests/gateway/test_shutdown_forensics.py`
- **#57901: Fix systemd timeout check for missing user unit**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#34734`, `#34734`, `#36766`, `#37324`, `#54396`, `#36755`
- **#61017: fix(gateway): honor systemd unit scope in shutdown check**. open
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#54396`, `#34734`, `#36766`, `#37324`, `#58735`, `#61003`, `#54396`, `#61017`
  - files: `gateway/shutdown_forensics.py`, `tests/gateway/test_shutdown_forensics.py`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`