Gateway SIGTERM startup exit code and supervisor recovery
Cluster 103191. Data as of
Nothing open on GitHub. Fix merged in #104517 on 6 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #104517. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104517. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes concern the gateway process exiting with code 0 when receiving SIGTERM during startup, which causes the service supervisor (s6) to treat the shutdown as intentional and not restart the gateway. The changes aim to ensure a non-zero exit code so the supervisor triggers recovery.
Open issues0
Open PRs0
Fixes on record
-
#104517 fix(gateway): an unexpected SIGTERM during startup exits non-zero so the service manager restarts the gateway (#103191, salvage #103208)
files:
contributors/emails/[email protected],gateway/run.py,gateway/run_shutdown.py,tests/gateway/test_startup_restart_race.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#103191Gateway: SIGTERM during startup exits 0 → s6 finish treats it as intentional stop, gateway stays down (dashboard double gateway-restart race)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Merged PRs
- #104517
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 6 Sep 2026