Files
OpenFUT/scripts/systemd/openfut-host.service
T
funman300 8ae432223a ops: systemd supervision for Core and the FIFA17 host (staging-proven)
Replaces the detached `setsid nohup … nsenter …` launch, which had no restart
policy, no boot persistence and no supervisor-visible logs. Staging units are
installed and proven; production units are TEMPLATES and are not installed.

Three decisions, each measured rather than assumed:

* `Wants=`, not `Requires=`, from host to Core. With `Requires`, stopping Core
  stopped the host AND a later Core start did not bring it back -- a routine
  Core restart would leave the client with no server. With `Wants` the host
  survives a Core outage, answers 503 core_unavailable, never falls back to
  Python, and resumes the moment Core returns with no intervention. Both halves
  tested.
* Readiness is a bounded ExecStartPre TCP gate, because ordering proves nothing
  about readiness and Type=exec only proves the binary exec'd. Core binds its
  listener after migrations and content load, so "port open" is a real signal.
  The gate FAILS rather than blocking: a host that waits forever looks healthy
  while serving nobody.
* The netns is resolved by container NAME every start. The container is
  restart=unless-stopped and its netns inode CHANGES on restart (measured:
  4026539938 -> 4026540033), so a hardcoded pid is wrong by construction and
  anything left in the old namespace serves nobody. Proven equivalent to today's
  nsenter against a scratch container, never production's namespace.

`systemd-analyze verify` caught two real defects before deployment:
StartLimitIntervalSec/StartLimitBurst sat in [Service], where systemd 252
silently ignores them, so the crash-loop ceiling was not taking effect; and a
Documentation URL containing %20 parsed as a specifier. Both fixed and the
effective properties re-confirmed from the running units.

Staging evidence: Core-first ordering, host refused when Core is absent or
merely not listening, outage survival, automatic recovery, restart, graceful
stop with no strays, boot simulated via multi-user.target, 3x SIGKILL contained
at ~5s spacing, journald logs, and economy state byte-identical throughout
(integrity ok, fk 0).
2026-08-22 20:46:15 +00:00

56 lines
2.0 KiB
Desktop File

[Unit]
Description=OpenFUT FIFA17 UTAS host (PRODUCTION) — client-facing, Core-dependent
Documentation=file:///home/alex/OpenFUT/scripts/systemd/README.md
# PRODUCTION TEMPLATE — NOT INSTALLED.
Requires=openfut-netns.service
After=openfut-netns.service
Wants=openfut-core.service
After=openfut-core.service
# `Wants` on Core, deliberately NOT `Requires`/`BindsTo`/`PartOf` — measured on
# staging: those propagate a Core stop into a host stop, and a later Core start
# does NOT bring the host back, so a routine Core restart would leave the client
# with no server at all. With `Wants` the host survives a Core outage, answers
# 503 `core_unavailable` (never a Python fallback), and resumes serving the
# moment Core returns with no supervisor intervention. Both halves were proven
# on the staging units.
#
# `Requires` on the netns unit IS correct: without the namespace the host would
# bind the wrong network entirely.
# StartLimit* MUST live in [Unit]: systemd 252 silently IGNORES them in
# [Service] (`systemd-analyze verify` flags it), which would have left the
# crash-loop ceiling at the 10s/5 default instead of the intended 60s window.
StartLimitIntervalSec=60
StartLimitBurst=5
[Service]
Type=exec
User=root
NetworkNamespacePath=/run/netns/openfut
EnvironmentFile=/etc/openfut/host.env
# Admission gate. Ordering alone proves nothing about readiness (Type=exec only
# proves the binary exec'd). Core binds its port only after migrations and the
# content pack have loaded, so "port open" is a real readiness signal here.
# Bounded and FAILING rather than blocking: a host that waits forever looks
# healthy to the supervisor while serving nobody.
ExecStartPre=/home/alex/OpenFUT/scripts/systemd/openfut-wait-tcp.sh 127.0.0.1 18080 30
ExecStart=/home/alex/openfut-migration/promote-contract-20260822-184409/artifacts/openfut-utas-host
KillSignal=SIGTERM
KillMode=mixed
TimeoutStopSec=30
Restart=on-failure
RestartSec=5s
StandardOutput=journal
StandardError=journal
SyslogIdentifier=openfut-host
[Install]
WantedBy=multi-user.target