How to Check txAdmin Logs for Errors

Building your first FiveM server? Our complete server setup guide covers everything from hosting to security setup.

txAdmin maintains three types of persistent log files in the txData/<profile>/logs/ directory: admin logs for administrative actions, fxserver logs for console output, and server logs for in-game events. These logs are essential for diagnosing server issues, tracking player activities, and monitoring system performance.

Target Audience: FiveM server administrators using txAdmin v4.6.0 or newer with log rotation capabilities.

Log Types and Locations

File Structure

txData/
└── <profile>/
    └── logs/
        ├── admin/
        ├── fxserver/
        └── server/

Log Categories

Admin Logs (admin/) Contains log of administrative actions as well as some automated ones like server restarts, bans, warns, settings change, live console input. Does not log user IP addresses except from authentication endpoints.

FXServer Logs (fxserver/) Contains the log of everything that happens in the fxserver console (stdin, stdout, stderr). Any live console input is prefixed with >.

Server Logs (server/) Contains all actions that happen inside the server, for example player join/leave/die, chat messages, explosions, menu events, commands.

Web Interface Log Access

Method 1: Live Console

1. Access your txAdmin web panel at http://your-server-ip:port
2. Navigate to Live Console in the sidebar
3. Monitor real-time server activities, warnings, and error messages for debugging issues
4. Look for entries marked with [ERROR], [WARN], or [CRITICAL]

Method 2: Server Log Viewer

1. Go to Server Log in the sidebar menu
2. Monitor all activities on the server including player connections, chat messages, game deaths, menu actions, executed commands, and system events
3. Use the filter options to isolate error messages
4. Export log sections for detailed analysis

Method 3: Action Log

1. Navigate to Settings → Diagnostics
2. View the Action Log, which records all actions performed by txAdmin or any Admin
3. Check for failed administrative actions or system errors

File-Based Log Access

Direct File Reading

# Navigate to logs directory
cd txData/<your-profile>/logs/

# View recent errors in fxserver logs
tail -100 fxserver/fxserver-YYYY-MM-DD.log | grep -i error

# Search for specific error patterns
grep -r "ERROR\|WARN\|CRITICAL" ./

# Monitor logs in real-time
tail -f fxserver/fxserver-$(date +%Y-%m-%d).log

Log File Naming Convention

• Files follow pattern: <type>-YYYY-MM-DD.log
• Example: fxserver-2025-06-10.log

Common Error Patterns

Resource Loading Errors

[ERROR] Failed to start resource 'resource_name'
[ERROR] Could not load resource metadata for resource_name
[WARN] Resource resource_name is using deprecated syntax

Database Connection Issues

[ERROR] MySQL connection failed
[ERROR] Could not execute query
[WARN] Connection to database timed out

Player-Related Errors

Player sources are kept in the format [mutex#id] name where the mutex is an identifier of that server execution. Search for [mutex#id] to find the initial player join with all identifiers.

Memory and Performance Issues

[WARN] High memory usage detected
[ERROR] Script timeout in resource_name
[CRITICAL] Server overload detected

Log Configuration

Rotation Settings

Edit your txData/<profile>/config.json and add an object inside logger with the key being one of [admin, fxserver, server]. Configure rotation options according to the rotating-file-stream library reference.

Example configuration:

{
  "logger": {
    "fxserver": {
      "size": "10M",
      "interval": "1d",
      "compress": "gzip"
    }
  }
}

Verbose Logging

Set txAdminVerbose to true to print on the console more detailed information about errors and events:

# Windows
./FXServer.exe +set txAdminVerbose true

# Linux  
./run.sh +set txAdminVerbose true

Troubleshooting Specific Issues

txAdmin Not Responding

If you get “FXServer is not responding!” it means the txAdmin:Monitor could not connect to the FXServer. Causes include:

• FXServer stuck on a resource
• Port conflicts between FXServer and txAdmin
• Healthcheck returning 404 errors

Permission Issues

If you get “cannot read file”, the admin file txData/admins.json doesn’t exist or txAdmin doesn’t have permission to read it.

Profile Loading Errors

Selected profile cannot be loaded due to permission issues or broken JSON.
Delete corrupted files and restart txAdmin to regenerate.

Best Practices

1. Regular Log Review: Check logs daily for accumulating warnings
2. Automated Monitoring: Set up alerts for critical error patterns
3. Log Retention: Configure appropriate rotation based on server activity
4. Backup Logs: Include log directories in backup procedures
5. Timestamp Correlation: Use timestamps to correlate events across different log types
6. Make sure your server configuration is right: Server.cfg Tutorial

External Resources

• Official txAdmin Documentation – Primary reference for txAdmin features and configuration
• txAdmin GitHub Repository – Source code and issue tracking
• FiveM Server Manual – Complete server setup guide

Uncertainty Note: Log format specifications may vary between txAdmin versions; always verify against your installed version.

Systematic log monitoring through txAdmin’s web interface and direct file access enables proactive identification of server issues before they impact player experience.

FiveM Error Codes & Fixes – Mega-Guide