What is this error?
The 'Exception in server tick loop' is a generic crash report indicating that the Minecraft server process has encountered a critical error and can no longer process game ticks. Because the server cannot maintain its heartbeat, it shuts down to prevent world corruption.
Common Causes
- Corrupted Chunk Data: A specific area of the world map has invalid data that the server cannot load.
- Mod or Plugin Conflicts: Two or more modifications are attempting to access the same game logic simultaneously.
- Insufficient Resources: The server is running out of memory (RAM) or CPU cycles, causing the tick loop to time out.
- Invalid Entity/Tile Entity: A specific entity (like a mob or item frame) has entered a state that causes the server to crash upon loading.
How to fix it
1. Check the Crash Report
Before making changes, identify the specific cause.
- On AwakeNode: Use the File Manager to navigate to the
/crash-reports/folder. Open the most recent file to see the stack trace. - On other hosts: Use your SFTP client to download the latest file from the
/crash-reports/directory.
Look for lines mentioning specific mods, entities, or world coordinates. This often points directly to the culprit.
2. Remove Problematic Mods or Plugins
If the crash report points to a specific mod or plugin, remove it.
- On AwakeNode: Use the Files tab to delete the offending file from your
modsorpluginsfolder, then restart. - On other hosts: Manually delete the file from your
/mods/or/plugins/folder via SFTP and restart the server.
3. Address Resource Issues
If the crash report indicates a 'java.lang.OutOfMemoryError', your server requires more RAM.
- On AwakeNode: Upgrade your hosting plan. The system automatically updates your startup parameters (Xmx) to match your new allocation.
- On other hosts: You must manually edit your startup script or command line arguments to increase the
-Xmxflag.