The Ultimate Minecraft Server Crash Guide
The Ultimate Minecraft Server Crash Guide
When a Minecraft server suddenly stops, restarts, or crashes upon player login, the exact crash stack trace is stored in crash-reports/. This guide covers how to resolve the four most destructive Minecraft server crashes.
Where to Find Your Crash Report
Open the Files tab on the Ash Host Game Panel and look inside the crash-reports/ folder. Open the newest file named crash-YYYY-MM-DD_HH.MM.SS-server.txt.
1. Fixing Watchdog Crash: "A single server tick took 60.00 seconds"
Your crash report starts with the famous Spigot/Paper Watchdog message:
Description: Watching Server
java.lang.Error: Watchdog: A single server tick took 60.00 seconds (should be max 0.05)
Considering it to be crashed, server will also shutdown.
Why this happens: Minecraft has an internal safety monitor (Watchdog) that shuts down the server if a tick takes longer than 60 seconds. This is caused by massive chunk loading, massive redstone clocks, a corrupted entity loop, or a plugin waiting for an external database that is offline.
How to Fix It:
- Scroll down into the Thread: Server thread section of your crash report to find which plugin or world function is listed at the top of the stack.
- Temporary Safety Workaround: In
server.properties, set:
(This gives the server 180 seconds to complete complex operations before forcing a shutdown).max-tick-time=180000 - Pre-generate chunks: If the crash happened while someone flew with an Elytra, use the
Chunkyplugin to pre-render chunks during off-peak hours.
2. "java.lang.OutOfMemoryError: Java heap space"
In your console or crash report, you see:
java.lang.OutOfMemoryError: Java heap space
Exception in thread "Server thread" java.lang.OutOfMemoryError
Why this happens: The server ran out of allocated RAM. Common causes include unoptimized mob farms, huge render distances, dynmap tile renders, or running 30+ plugins on a 2GB RAM plan.
How to Fix It:
- Reduce View & Simulation Distance: In
server.properties, setview-distance=6andsimulation-distance=4. This cuts RAM usage by over 40%. - Disable Idle Villager Ticking: In
config/paper-world-defaults.yml, settick-inactive-villagers: false. - Upgrade Server RAM: If you are running 20+ plugins or modpacks, upgrade your server plan to 4GB or 6GB RAM from the Ash Host Client Area.
3. Ticking Entity / Corrupted Chunk Crash
The server crashes whenever a specific player joins or enters a certain region:
net.minecraft.server.MinecraftServer.tickChildren
Description: Ticking entity
Entity's Exact location: 142.50, 64.00, -890.30
Entity's Block location: World: (142,64,-890)
How to Fix It in Paper/Purpur:
Modern Paper versions have automated tools to safely erase corrupted entities and blocks without deleting your whole world:
- Open
config/paper-global.ymlin your panel file manager. - Find and set the auto-removal flags to true:
unsupported-settings: perform-username-validation: true entities: spawning: remove-corrupt-tile-entities: true - Start your server. Paper will automatically delete the broken entity at that coordinate and safely boot the world.
Scale Your Minecraft World with Zero TPS Drops
Ash Host Minecraft servers feature dedicated RAM, high single-core AMD performance, and Aikar's optimized JVM garbage collection flags.
Explore Minecraft Hosting Plans →Hjalp dette svar dig?
Relaterede artikler
Powered by WHMCompleteSolution