Symptom
Right after update.run toward v2026.9.3, gateway shutdown fails and the process exits. systemd marks the unit failed and does not start it again. The update result is skipped.
Evidence what you'll see
- The line is
[gateway] shutdown step failed (gateway close): Failed to reset global singleton lifecycle state | service child cleanup identity lost: write EPIPE. - Four
payload.largeevents with reasonchat_history_budgetwere logged about a minute earlier, at roughly 80 to 88 KB each. - A manual start came back on
v2026.9.2.
Why it happens
The report places the crash in the shutdown that follows the update, and calls it a race with a large chat-history payload. It also says this shape had not appeared in that host's stability logs before v2026.9.3. The linked issue does not confirm the payload as the cause.
Affected versions
Ultramarine Linux, Node v24.18.0, a systemd user service. The running build after the crash was v2026.9.2. The update target was v2026.9.3.
Fix steps
0 of 2 done
Your check marks stay in this browser only.
How to check it worked
- The user unit is active again. If the update stayed
skipped, the running build isv2026.9.2and the shutdown line is not repeating.
If it still fails
- The report says this was a single crash on that host, with no earlier match in its stability logs back to 18 August 2026. The linked issue does not name a later build that restarts the unit on its own.
Sources and credit
Summarized in our own words from these public reports. Credit goes to their authors.
Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change
Hit an error we don't cover? Submit it