Skip to content

GOST Manager v2.0.3

Latest

Choose a tag to compare

@github-actions github-actions released this 02 Aug 00:45
· 1 commit to main since this release
f46437f

GOST Manager v2.0.3

Released: 2026-08-02

GOST Manager v2.0.3 improves Watchdog probe accuracy and reduces Monitoring
overhead under high connection and file-descriptor load while preserving the
existing Direct Mode traffic lifecycle.

Watchdog stability

  • Added explicit per-profile Ping and TCP health checks. Ping remains the
    compatible default, and operators opt individual profiles into TCP checks.
  • TCP checks connect only to the allowlisted KHAREJ_IP:TUNNEL_PORT target.
  • Local configuration, execution, and resource failures are classified as
    non-actionable probe_error; they do not change success/failure counters or
    create traffic actions.
  • Historical profile events retain the check mode used when the event occurred.
    Watchdog schema v3 adds a nullable, allowlisted event-time mode and safely
    backfills profile events from Ping-only releases.
  • Production policy snapshots normalize a missing legacy v2.0.1 or v2.0.2
    check_mode to Ping while preserving explicit Ping/TCP, maintenance, manual
    override, and stop ownership.

Monitoring stability

  • Fresh installations use 20-second Fast, 60-second TCP, 120-second Slow, and
    1,800-second maintenance cadences.
  • Added an atomic high-traffic Monitoring preset with validation, private backup,
    no-op detection, and an optional collector-only restart.
  • Separated Fast, TCP, and Slow collection so CPU/stat sampling remains timely
    while socket, filesystem, static process, and FD work runs less frequently.
  • Large 10,000-FD process fixtures prove descriptor enumeration remains on the
    Slow cycle.
  • Added persistent collection load shedding after overruns, with bounded recovery
    after three on-time cycles.
  • Reduced SQLite write overhead with one main collection transaction, bounded
    retention work, post-commit checkpoint maintenance, and no automatic VACUUM.

Upgrade compatibility

  • Deterministic fixtures cover upgrades from both v2.0.1 and v2.0.2.
  • Upgrades preserve Direct Mode env files, units, service identity/state,
    Monitoring configuration/history, Watchdog configuration/history, manual
    override, and existing check modes.
  • Installation and upgrade perform zero GOST traffic lifecycle actions and no
    firewall changes.
  • The production rollout and rollback procedure is documented in
    docs/GM-203-PRODUCTION-RUNBOOK.md, with a read-only preflight/postflight
    verification script at scripts/gm-203-production-check.sh.

Known limitations

  • TCP connect is not full SOCKS authentication or forwarding validation.
  • This release does not enable BBR.
  • This release does not make 2 GiB RAM sufficient for approximately 8,000
    connections; add RAM or reduce traffic before rollout when headroom is unsafe.
  • Production rollout and soak are still pending.

Upgrade

Use the checksum-verified latest-release setup flow, or pin this release with:

GOST_MANAGER_VERSION=v2.0.3 \
bash <(curl -fsSL https://raw.githubusercontent.com/WikiPanel/GOST-Manager/main/setup.sh)

After upgrade, keep existing profiles on Ping unless TCP checks are explicitly
approved. Apply the high-traffic Monitoring preset and perform controlled probe
tests only during the documented rollout window.