Roastd / Minecraft

The server crashed and then hung

What it looks like in your log

Seems like you crashed and the server got stuck, you might need to terminate the process

What causes it

The server crashed and its shutdown never finished, so the process stayed stuck instead of restarting.

How to fix it

We force-stop and restart this automatically. The crash just above it in the log is the real problem to fix if it keeps happening.

Why it happens

The server crashed, started its shutdown, and the shutdown never finished. Something on the server thread was still blocked, so the process sat there with the world unsaved and the port held, and this line is the watchdog noticing. It is the aftermath of the crash above it in the log, not a separate problem.

Fix it step by step

1. 1Scroll upThe real fault is the first ERROR or FATAL line before this one. Fix that; this line goes with it.
2. 2Make sure something restarts itOn a hosted panel the process is force-stopped and restarted for you. On your own machine, a start script with a loop or a service manager does the same job, otherwise the server stays dead until you notice.
3. 3Check the world savedA hang during shutdown can leave the last minutes of play unsaved. If the crash repeats, take a backup before every restart while you chase it.

Errors that travel with this one

• The server stalled for too long and the watchdog stepped inThe server has not responded for 60 seconds! Creating thread dump
• Not enough RAM to startError occurred during initialization of VM: Could not reserve enough space for object heap
• The server port is already in use**** FAILED TO BIND TO PORT! The exception was: java.net.BindException: Address already in use
• The Minecraft EULA has not been acceptedYou need to agree to the EULA in order to run the server. Go to eula.txt for more info.
• A mod is missing a dependencyMissing or unsupported mandatory dependencies:
• A mod is incompatibleIncompatible mod set!