fix(runtime): keep supervision and absence retries in container
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
226d93e2aa
commit
3f9fd2f36f
21 files changed
+1056
-137
No files matched your search
@@ -34,36 +34,34 @@ in logs or shared terminals.
|
||||
By default Compose uses the locally built `zapret-autotune-managed-target:local`.
|
||||
Tags are only local build/test candidates, not production release references.
|
||||
For production promotion, set `ZAPRET_AUTOTUNE_IMAGE=<registry>/<managed-target>@sha256:<digest>`
|
||||
in the private `.env` and pull that immutable image before starting the unit.
|
||||
Use a managed target image, not the generic image; the systemd command never
|
||||
builds images. Do not enable the production service with a tag or local default.
|
||||
in the private `.env` and pull that immutable image before starting the target.
|
||||
Use a managed target image, not the generic image. Do not deploy production
|
||||
with a tag or local default.
|
||||
|
||||
Offline static guard (from repository root):
|
||||
`python3 deploy/managed-target/check_static.py`.
|
||||
Isolated, accelerated shell supervision fixtures (no network):
|
||||
`python3 deploy/managed-target/check_supervision.py`.
|
||||
|
||||
## Optional native systemd supervision
|
||||
## In-container supervision
|
||||
|
||||
For unattended boot, place this checkout at `/opt/zapret2-autotune`, provision
|
||||
`deploy/managed-target/.env` and state as above, and build the target image first.
|
||||
For production, select and pull the immutable managed-target digest as above
|
||||
instead of using a local build tag.
|
||||
Install `deploy/managed-target/zapret-autotune.service` in `/etc/systemd/system/`,
|
||||
then run `systemctl daemon-reload` and `systemctl enable --now zapret-autotune`.
|
||||
Do not simultaneously start the same project with detached Compose.
|
||||
Enabling the unit starts this isolated target on subsequent boots. `ExecStop`
|
||||
only stops `target`; it does not replace the foreground process's failure code.
|
||||
An explicit service stop suppresses restart, including during a shutdown race.
|
||||
|
||||
Compose has no automatic restart. The foreground systemd unit restarts **only
|
||||
exit 75**, with at most three starts per six hours. Clean typed recovery timeouts,
|
||||
Compose has no automatic restart. PID 1 restarts the entire owned runtime only
|
||||
for technical failures, with three starts per rolling six hours (including initial
|
||||
startup) and cancellable 15/30-second cooldowns. Clean typed recovery timeouts,
|
||||
unexpected monitor exits/crashes, and Shadowsocks failures qualify only if
|
||||
shutdown cleanup succeeds. Configuration (64), safety/database/rollback/cleanup
|
||||
failures (78), and graceful SIGTERM (0) never request restart. Investigate and
|
||||
failures (78), and graceful SIGTERM (0) never request restart. Exhausting the
|
||||
restart budget exits 78. Investigate and
|
||||
repair nonretry failures before manually starting again; do not clear state.
|
||||
Monitor cancellation/join is bounded to 60 seconds, final target-local zapret
|
||||
Monitor cancellation/join is bounded to 45 seconds, reconciliation gets 45 seconds
|
||||
plus five to force kill, and final target-local zapret
|
||||
stop gets 30 seconds then forced kill after five more, and each Shadowsocks join
|
||||
gets five seconds. Exceeding a join bound fails closed. Compose grants 120
|
||||
seconds; systemd grants 180 seconds.
|
||||
gets five seconds. Exceeding a join bound fails closed. Compose grants 240
|
||||
seconds. Reconcile after joining the monitor and before even stopping zapret:
|
||||
stop also sources config, so unknown state is never sourced. The sequential
|
||||
cleanup budget is 140 seconds; 240 seconds also covers an in-flight startup
|
||||
command and scheduling grace. Watchdogs run in fresh shell interpreters and
|
||||
cancel/join their own sleepers, including during PID 1's EXIT trap.
|
||||
|
||||
## Isolation and runtime contract
|
||||
|
||||
@@ -97,8 +95,9 @@ Any startup command failure/timeout exits 78, never the retry code 75. These
|
||||
bounds do not shorten the monitor's 90-minute bootstrap/recovery scan budget.
|
||||
|
||||
SIGTERM/SIGINT cancels and waits for the monitor before stopping target-local
|
||||
zapret and Shadowsocks children. Monitor fatal exits stop the
|
||||
entrypoint. Monitor health is YouTube Player API status through the owned SOCKS,
|
||||
zapret and Shadowsocks children. Nonretry monitor fatal exits stop the
|
||||
entrypoint; technical exits and Shadowsocks failures restart from private configs
|
||||
only after safe cleanup. Monitor health is YouTube Player API status through the owned SOCKS,
|
||||
not video playback/SABR; GGC candidates are scoped to the exact discovered
|
||||
hostname.
|
||||
|
||||
|
||||
Reference in new issue
Block a user