Crashes & restart loops
Find the underlying failure instead of hiding it with longer timeouts.
Preserve the useful logs
Capture the FXServer console output before and through the first failure. Read the earliest relevant error, not only the final restart line. Note the txAdmin/artifact version, time, player count, and recent changes.
Classify the symptom
- Immediate startup failure: look for invalid configuration, missing files, failed database connections, or a resource dependency.
- Crash after a resource change: reproduce the change on an isolated server and compare against the last working version.
- Hang under load: compare performance charts and resource profiling with the player count at that time.
- Host failure: inspect RAM, disk space, process termination, and provider limits.
Make one controlled change
Roll back or disable the suspected change in a test environment. Some resources have dependencies; disabling one on a live server can cause other failures. Keep a working backup before changing the production configuration.
Recovery settings
Boot grace periods should reflect normal startup time. If the server never finishes loading, a longer grace period only delays detection. Scheduled restarts are maintenance tools, not a remedy for an unexplained crash.
When asking for help
Share a redacted log excerpt with context, exact versions, reproduction steps, and what changed. Framework/resource maintainers are the right contact for their own errors; use txAdmin support when evidence points to the manager itself.
Source: txAdmin upstream documentation.