Reading and Diagnosing Server Logs
Locate and interpret DayZ server log files to diagnose mod conflicts, script errors, BattlEye events, and crash stack traces.
Overview
DayZ generates several distinct log files during operation. Knowing which log contains which type of information saves significant time when diagnosing crashes, mod conflicts, and player issues. All logs are stored in server_profile/logs/ unless otherwise noted.
Log File Reference
server_profile/
logs/
script.log ← SQF script errors and mod output
scheduler.log ← Frame timing and crash stack traces
*.RPT ← Main timestamped event log (in server root or profile dir)
BattlEye/
BEServer.log ← BattlEye events (kicks, bans, filter matches)
The .RPT file location varies by install. On Pterodactyl it is typically in the server root directory alongside the executable.
script.log
script.log captures all SQF scripting errors and diag_log output from mods. This is the first place to look when a mod is not working:
Error in expression <_vehicle setPos _pos>
Error position: <_pos>
Error Undefined variable in expression: _pos
File some_mod\scripts\init.sqf, line 47
Key patterns to search for:
Error in expression— SQF runtime errorscript error: cf not found— CF not loaded or load order wrongCannot load texture/Cannot load model— missing mod asset (mod not installed correctly)Missing addons:— mod dependency not installed
Enable verbose script logging in serverDZ.cfg:
logLevel = 4;
Levels: 0 = off, 1 = errors only, 2 = warnings, 3 = info, 4 = verbose. Level 4 generates large logs but captures all mod output.
scheduler.log
scheduler.log records the server's internal task scheduler and is where crash stack traces appear:
[Scheduler] Frame time: 45ms avg, 203ms max
[Scheduler] Task overflow: mission_spawn_task exceeded budget by 88ms
A stack trace in scheduler.log looks like:
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 6F4B2310
Stack trace:
...
When submitting a crash report to a mod author or support, copy the full stack trace from scheduler.log.
RPT Log
The RPT (Report) log is the primary timestamped event log. It captures:
- Server startup and shutdown events
- Player join and disconnect events (with Steam IDs)
- BattlEye kick and ban events
- Frame timing warnings
- Mission loading progress
2026-04-27 14:05:12 Player "Survivor" (GUID 76561198...) connected
2026-04-27 14:07:44 Player "Survivor" disconnected
2026-04-27 14:10:01 BattlEye Server: Player #3 Survivor (1.2.3.4) kicked
The RPT is the log to check when investigating specific player incidents, as it includes timestamps and GUIDs.
BattlEye Logs
BattlEye/BEServer.log records all BE activity:
[2026-04-27 14:30:01] Player "CheatSuspect" was kicked by BattlEye: Script Restriction #12
The restriction number maps to a line in scripts.txt. See Configuring BattlEye Filters and Preventing False Kicks for how to act on these.
Enabling Verbose Logging
In serverDZ.cfg:
logLevel = 4;
logFile = "server_profile/logs/script.log";
For BE verbose logging, in server_profile/BattlEye/beserver.cfg:
LogLevel 3
Common Log Patterns and Fixes
| Log Message | Likely Cause | Fix |
|---|---|---|
Missing addons: mod_x |
Mod not installed or misspelled in -mod= |
Verify mod folder and startup parameters |
script error: cf not found |
CF not first in mod list | Reorder -mod= flag |
Frame time: >100ms avg |
Server overloaded | Reduce -limitFPS, increase -cpuCount |
Script Restriction #N in BE log |
Mod triggering BE filter | Add exception to scripts.txt |
ACCESS_VIOLATION in scheduler.log |
Crash, often mod conflict | Check recently added mods |
Log Rotation
Logs are not automatically rotated. On long-running servers they can grow large. Periodically archive or clear them:
# Archive and clear logs
tar -czf logs_backup_$(date +%Y%m%d).tar.gz server_profile/logs/
rm server_profile/logs/*.log
The server creates new log files on next start.