# NousResearch/hermes-agent · SIGUSR2 faulthandler chaining kills gateway process

## Open now

- 1 issue, 0 PRs open on GitHub.
- #84373: \[Bug\]: SIGUSR2 faulthandler diagnostic kills Linux gateway because handler chains to default signal action

A bug where the SIGUSR2 signal handler for fault diagnostics chains to the default signal action, causing the Linux gateway process to be killed. Fixes address preventing this chaining behavior.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 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_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: 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

- #84373: \[Bug\]: SIGUSR2 faulthandler diagnostic kills Linux gateway because handler chains to default signal action

## Prior & competing PRs

- **#84447: fix(gateway): do not chain SIGUSR2 faulthandler to default action (#84373)**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#75750`
- **#84539: fix(gateway): do not chain SIGUSR2 faulthandler dump to process kill**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#75750`, `#84373`

## Fix status

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