# NousResearch/hermes-agent · SQLite lock loss from Linux permission hardening fix

## Open now

- Nothing open on GitHub.

A bug where tightening file permissions on state.db dropped SQLite locks on Linux, causing WAL issues and session outages. The fixes adjust how chmod is applied to avoid breaking existing lock holders.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #109841. Verify it addresses your case.
- **Recommended:** read PR #109841 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## 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_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: 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.

## Closed / duplicate issues

- #109728: \[Bug\]: #109509 permission hardening drops SQLite locks, causing deleted WAL generations and session outage on Linux

## Prior & competing PRs

- **#109841: fix(state): tightening state.db modes no longer drops the holder's SQLite locks (#109786, salvage #109754)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state.py`, `tests/test_hermes_state.py`
- **#109734: fix(state): preserve SQLite locks during Linux permission hardening**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#109841`
- **#109754: fix(state): tighten existing db files by chmod(2), not an open/fchmod/close cycle**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#109841`

## Fix status

- Merged to main in PR #109841 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-13`.