How to Read Minecraft Crash Reports
Last modified on Dec 6, 2021 in Server Errors
Many times when modifying a server you may experience issues with the server crashing. These crashes are generally caused by either mods, the world, or the server jar. When a server crashes, it generates a crash report in the FTP File Access.
These crash reports break down why the server crashes and can help you get a better understanding of what’s wrong and how to fix it. At first look, it may seem confusing but all crash reports are similar and once you know what to look for you will be able to accurately read Minecraft crash reports.
Understanding a Crash Report
Where to find the crash reports
- Head to your Game Panel and to the left, press FTP File Access and log in.
- Once in FTP File Access, you will see a folder named `crash-reports`. Go ahead and click that. Looking inside of that directory you will notice a file or multiple files.
- Every file is written with the date (2019-08-17) which makes it easy to know when each report was made. When there are several files it’s always best to look at the latest and most recent crash to identify the issue.
- To read the crash report, click the “edit” link to the right of the file.
Reading the Crash Report
---- Minecraft Crash Report ---- // Everything's going to plan. No, really, that was supposed to happen. Time: 1/24/20 7:25 AM Description: Exception in server tick loop Missing Mods: unknown : need [1.5.2,): have missing net.minecraftforge.fml.common.MissingModsException: Mod thaumcraft (Thaumcraft) requires [baubles@[1.5.2,)] at net.minecraftforge.fml.common.Loader.sortModList(Loader.java:266) at net.minecraftforge.fml.common.Loader.loadMods(Loader.java:572) at net.minecraftforge.fml.server.FMLServerHandler.beginServerLoading(FMLServerHandler.java:98) at net.minecraftforge.fml.common.FMLCommonHandler.onServerStart(FMLCommonHandler.java:333) at net.minecraft.server.dedicated.DedicatedServer.func_71197_b(DedicatedServer.java:125) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:486) at java.lang.Thread.run(Thread.java:748)
This is the top portion of the report where it will have the date, time and stack trace. The stack trace is a report of when a program runs at a certain time in its execution. This will be primarily where we will discover the error that is causing the server or client to crash.
In this example, we can tell that a mod is missing due to part of the stack trace saying "Missing Mods: unknown : need [1.5.2,): have missing". If we go down to the next line we can see that it tells "net.minecraftforge.fml.common.MissingModsException: Mod thaumcraft (Thaumcraft) requires [baubles@[1.5.2,)]" which translates to the mod Thaumcraft needs the mod Baubles version 1.5.2 in order to run properly.
A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- System Details -- Details: Minecraft Version: 1.12.2 Operating System: Linux (amd64) version 3.10.0-957.27.2.el7.x86_64 Java Version: 1.8.0_222, Oracle Corporation Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1474787976 bytes (1406 MB) / 2075918336 bytes (1979 MB) up to 2075918336 bytes (1979 MB) JVM Flags: 4 total; -Xmx2048M -Xms2048M -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 FML: MCP 9.42 Powered by Forge 188.8.131.5247 5 mods loaded, 5 mods active States: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored | State | ID | Version | Source | Signature | |:----- |:---------- |:------------ |:-------------------------------- |:--------- | | L | minecraft | 1.12.2 | minecraft.jar | None | | L | mcp | 9.42 | minecraft.jar | None | | L | FML | 184.108.40.206 | forge1122.jar | None | | L | forge | 220.127.116.1147 | forge1122.jar | None | | L | thaumcraft | 6.1.BETA26 | Thaumcraft-1.12.2-6.1.BETA26.jar | None | Loaded coremods (and transformers): Profiler Position: N/A (disabled) Is Modded: Definitely; Server brand changed to 'fml,forge' Type: Dedicated Server (map_server.txt)
The second half of the crash report will go over your system details and the states of the mods loading in. With this, you can find our what version of Java they are running, how much ram they have allocated and the versions of the mods to be able to assist them. One of the best tools with crash reports is knowing the States in which a mod loads in. These states are as follows: 'U' = Unloaded 'L' = Loaded 'C' = Constructed 'H' = Pre-initialized 'I' = Initialized 'J' = Post-initialized 'A' = Available 'D' = Disabled 'E' = Errored
You can see these states to the left of each mod. In this example, they only made it to the loaded state. So if you have a mod that was UCE that would mean the mod Unloaded, Constructed and than Errored which means there was an error with loading that particular mod causing it to crash so you now know what the exact mod causing the issue is and can look into why it's occurring.
There are hundreds of different reasons that your server may crash, it can be from a world issue, server jar, mods, and far more. As long as you can narrow down what the reason is, the solution should come easier. If you can narrow down it’s a world issue, you can Google the error line to see if there are any solutions or you can restore a backup. With so many different solutions to so many different problems, there isn’t a way to break down each individual error you can get.