txAdmin Partial status & timeout restarts

This guide was reviewed against txAdmin v8.1.2 monitor source on 1 November 2026. Your installed FXServer artifact determines runtime behavior.

What "Partial" meansCopy Anchor Link

txAdmin monitors two independent signals: an FXServer heartbeat and the HTTP health check that fetches dynamic.json. In the reviewed monitor source, ONLINE means both are healthy; PARTIAL means one is unhealthy; OFFLINE can indicate both are unhealthy. A Partial state does not by itself prove a txAdmin bug or a DDoS.

The monitor can warn players one minute before a health-triggered restart when the heartbeat remains healthy but HTTP health checks keep failing. Restart behavior depends on the monitor state and configured recovery limits.

Diagnose in orderCopy Anchor Link

1. Record the FXServer artifact, txAdmin version, UTC timestamp, active player count, exact restart message and any recent deployment.
2. Look in txAdmin System Logs and Live Console for the first health-check or heartbeat failure. Keep logs from before the restart, not only the final warning.
3. From the FXServer host test the actual game HTTP endpoint (usually port 30120) with a short timeout. Adjust the port/interface to your deployment:

curl --max-time 5 -i http://127.0.0.1:30120/dynamic.json

A timeout, refused connection or HTTP error points to an HTTP listener, networking or resource-load problem. A successful local request does not establish that external players or Cfx can reach the endpoint. 4. Compare heartbeat loss with HTTP-only failures. Check host CPU/RAM pressure, blocked event loop, reverse-proxy/firewall configuration, host provider limits and recent FXServer artifact changes. 5. If the failure started with an artifact or resource update, reproduce against a staging server and compare logs and timings with the previous known-good build. Preserve evidence before rolling back. 6. Test external reachability of the game endpoint independently of txAdmin's panel TCP port. Never open a private panel port to fix the game endpoint.

What not to doCopy Anchor Link

• Do not disable watchdogs or increase timeouts blindly to suppress restarts.
• Do not assume "Partial" means the server process crashed.
• Do not paste real registration keys, database credentials, staff tokens, player identifiers or unredacted logs into public tickets.

EscalationCopy Anchor Link

Include a redacted log, precise build, dynamic.json status/latency, restart timestamp, and whether the heartbeat was still arriving. Community issue #1133 documents a similar symptom, but is not proof that your server has the same cause.

Related: Crashes & restart loops, Monitoring dashboard, Environment & ports.

Sources: v8.1.2 FxMonitor implementation, txAdmin Partial timeout issue #1133.