{"id":189691,"date":"2025-06-10T11:53:59","date_gmt":"2025-06-10T09:53:59","guid":{"rendered":"https:\/\/fivemx.com\/?p=189691"},"modified":"2025-09-10T09:10:02","modified_gmt":"2025-09-10T07:10:02","slug":"so-uberprufen-sie-die-txadmin-protokolle-auf-fehler","status":"publish","type":"post","link":"https:\/\/fivemx.com\/de\/how-to-check-txadmin-logs-for-errors\/","title":{"rendered":"So \u00fcberpr\u00fcfen Sie txAdmin-Protokolle auf Fehler"},"content":{"rendered":"\n

txAdmin maintains three types of persistent log files in the txData\/<profile>\/logs\/<\/code> 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.<\/p>\n\n\n\n

Target Audience<\/strong>: FiveM server administrators<\/a> using txAdmin v4.6.0 or newer with log rotation capabilities.<\/p>\n\n\n\n

Log Types and Locations<\/h2>\n\n\n\n

File Structure<\/h3>\n\n\n\n
txData\/\n\u2514\u2500\u2500 <profile>\/\n    \u2514\u2500\u2500 logs\/\n        \u251c\u2500\u2500 admin\/\n        \u251c\u2500\u2500 fxserver\/\n        \u2514\u2500\u2500 server\/\n<\/pre>\n\n\n\n
Log Categories<\/h3>\n\n\n\n
Admin Logs<\/strong> (admin\/<\/code>) 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.<\/p>\n\n\n\n
FXServer Logs<\/strong> (fxserver\/<\/code>) Contains the log of everything that happens in the fxserver console (stdin, stdout, stderr). Any live console input is prefixed with ><\/code>.<\/p>\n\n\n\n
Server Logs<\/strong> (server\/<\/code>) Contains all actions that happen inside the server, for example player join\/leave\/die, chat messages, explosions, menu events, commands.<\/p>\n\n\n\n
Web Interface Log Access<\/h2>\n\n\n\n
Method 1: Live Console<\/h3>\n\n\n\n
    \n
  1. Access your txAdmin web panel at http:\/\/your-server-ip:port<\/code><\/li>\n\n\n\n
  2. Navigate to Live Console<\/strong> in the sidebar<\/li>\n\n\n\n
  3. Monitor real-time server activities, warnings, and error messages for debugging issues<\/li>\n\n\n\n
  4. Look for entries marked with [ERROR]<\/code>, [WARN]<\/code>, or [CRITICAL]<\/code><\/li>\n<\/ol>\n\n\n\n
    Method 2: Server Log Viewer<\/h3>\n\n\n\n
      \n
    1. Go to Server Log<\/strong> in the sidebar menu<\/li>\n\n\n\n
    2. Monitor all activities on the server including player connections, chat messages, game deaths, menu actions, executed commands, and system events<\/li>\n\n\n\n
    3. Use the filter options to isolate error messages<\/li>\n\n\n\n
    4. Export log sections for detailed analysis<\/li>\n<\/ol>\n\n\n\n
      Method 3: Action Log<\/h3>\n\n\n\n
        \n
      1. Navigate to Settings<\/strong> \u2192 Diagnostics<\/strong><\/li>\n\n\n\n
      2. View the Action Log, which records all actions performed by txAdmin or any Admin<\/li>\n\n\n\n
      3. Check for failed administrative actions or system errors<\/li>\n<\/ol>\n\n\n\n
        File-Based Log Access<\/h2>\n\n\n\n
        Direct File Reading<\/h3>\n\n\n\n
        # Navigate to logs directory\ncd txData\/<your-profile>\/logs\/\n\n# View recent errors in fxserver logs\ntail -100 fxserver\/fxserver-YYYY-MM-DD.log | grep -i error\n\n# Search for specific error patterns\ngrep -r \"ERROR\\|WARN\\|CRITICAL\" .\/\n\n# Monitor logs in real-time\ntail -f fxserver\/fxserver-$(date +%Y-%m-%d).log\n<\/pre>\n\n\n\n
        Log File Naming Convention<\/h3>\n\n\n\n