← Back
A single server tick took 60.00 seconds - server will forcibly shutdown
COAL-014 · Watchdog force-killed the server
Minecraft's watchdog killed the server because a tick froze. What the watchdog does, why raising the timeout hides the problem, and how to find the mod that hung.
What it looks like in the log[Server Watchdog/ERROR]: A single server tick took 60.00 seconds (should be max 0.05) [Server Watchdog/ERROR]: Considering it to be crashed, server will forcibly shutdown.
What it means
A healthy server completes 20 ticks a second. The watchdog is a separate thread that notices when a single tick has run far past its budget - 60 seconds by default - and concludes the server is hung rather than slow. It then kills the process and dumps the thread stacks. This is not a performance warning: a tick that long means something is genuinely stuck.
How to fix it
- Read the thread dump printed with the crash. The Server thread's stack shows exactly what it was doing when it froze - the topmost mod package in that trace is what to investigate.
- Chunk generation is the usual innocent cause. A player exploring new terrain with heavy worldgen mods can stall a tick past 60 seconds on a slow disk. Pregenerating the world fixes that properly.
- Deadlocks are the usual guilty one. If the dump shows threads waiting on each other, that is a bug in the named mod - report it, and remove the mod meanwhile.
- Do not simply disable the watchdog. Setting
max-tick-time=-1inserver.propertiesstops the kill, not the freeze - the server then sits there unresponsive instead. It is a reasonable temporary measure while you pregenerate, and a bad permanent one.