How to Read Crash Report on Minecraft Servers?
When Minecraft servers receive an unexpected error, they shut down for protection and the crash reports Saves a text document in the directory. A server owner needs to be able to read these reports to diagnose the error themselves before opening a support ticket. In this guide, we will learn how to perform error analysis step by step.
Step 1: Head of the Report (Description) Section
formedcrash-date.txtThe first important area that will catch your eye when you open the file is "Description:" line. Here's a summary of why the server crashed:
Description: Ticking entity-> A creature, villager, or item that fell on the map got stuck and caused a loop error.Description: Exception ticking world-> Corruption has occurred in the map (chunk) files.Description: Watchdog Thread System Crash-> Since the server processor was locked and did not respond at all for 60 seconds, protection was activated (Usually it occurs after heavy lag).
Step 2: Stacktrace (Error Detail) Analysis
Search for **"Caused by:"** among the complex lines of English code that follow in the report. The package names following this word tell you which plugin caused the error:
- If between the lines
com.placeholderapi...If you see it, your PlaceholderAPI plugin is causing the crash. - if
org.bukkit.plugin...If a plugin name (e.g. Essentials) is mentioned after the statement, the version of that plugin does not match your server.
Step 3: Exact Solution Steps
- After identifying the plugin causing the error, update or downgrade it.
- If the problem is caused by a corrupt block or creature (Ticking Entity) in the world, what is written in the crash report Details: Entity Type: ... (Location: X, Y, Z) Examine the coordinates. While the server is down, you can restart the server by deleting the corrupted entity at that coordinate with the help of a map editor (MCEdit or Chunky).
This article is specially prepared for PvPServer.
