How to read and interpret your Arma Reforger Logs

[TMG Manic]

Debugging Server Crashes & Reading Logs in Arma Reforger​

Server crashed? Don’t panic. Reforger logs are verbose, and with the right tools, you can trace the issue, patch it, and get your ops back online. This guide walks through crash diagnosis, log parsing, and proactive debugging.

Step 1: Locate Your Logs​

• For dedicated servers, logs live in:
  /home/armauser/.local/share/ArmaReforger/Logs (Linux)
  %USERPROFILE%\Documents\My Games\ArmaReforger\logs (Windows)
• Look for files like:
  CrashReports.log – crash metadata
  server.log – runtime output
  modloader.log – mod loading issues

Step 2: Read the Crash Report​

Open `CrashReports.log` and look for:

Date: 2025-08-08 03:14:22
Game Version: 1.4.0.48
State: Failed (Error Code 0xC0000005)
GUID: 7F3A-9D2B-4C1E

What to check:

• Error codes (e.g. `0xC0000005` = access violation)
• Repro steps—what triggered the crash?
• Was it mod-related, scenario-related, or platform-specific?

Step 3: Parse server.log​

This file shows real-time output. Look for:

• Mod loading failures
• Missing scenario files
• Invalid config syntax
• Script exceptions or null references

Use:

tail -f server.log

to monitor live output during startup.

Step 4: Validate Modloader.log​

If your server crashes on startup, it’s often a mod issue. Open `modloader.log` and look for:

Failed to load mod: BetterMuzzleFlashes
Reason: Missing dependency: WeaponCore

Fix by:

• Adding missing mods to your config
• Checking mod versions and compatibility
• Validating mod IDs from ServerData.json

Step 5: Use External Tools​

• ARSM Monitor – live stats, logs, and crash tracking
• ReforgerJS Logger – structured event logging for player actions, kills, and admin events

These tools help you catch issues before they crash the server.

Step 6: Report to Bohemia (Optional)​

• Use the Crash Reporter dialog if available
• Attach `CrashReports.log` and reproduction steps
• Submit via Bohemia Feedback Tracker

Pro Tips​

• Always validate your JSON configs before restart
• Batch mod installs—don’t dump 30 mods at once
• Use `-maxFPS` to prevent runaway CPU usage
• Keep logs rotated—don’t let them balloon

Final Notes​

Crashes happen. What matters is how fast you trace, patch, and redeploy. If you’re stuck, post your `CrashReports.log`, `server.log`, and config snippets. Tag TMG Manic or drop your stack.