How to Find and Read a Server Crash Report

If you’re ever running a server and it crashes, server crash reports are your best tool in finding what caused the crash, and can help you and anyone else trying to fix your server. When a server crashes it will usually generate a crash report, which will contain all the information needed to find the cause of the crash as well as taking the steps to fix it.

If your server crashed and made a crash report, you’ll see a message like this in the console, where the name of the file will be the date and time the server crash occurred:

HOW TO FIND A CRASH REPORT

Multicraft:

  1. Login to your panel (https://mc.shockbyte.com/index.php?r=site/page&view=home), and then navigate to the “Server” tab, and select the server that is crashing.

       

  2. On the left, visit the “Files” category, and then click on the “FTP File Access” menu option.
  3.           

  4. Click the “login” button to access the files. If this gives you an error, simply re-enter your Multicraft password into the empty password field.
  5. Click on the folder in your server files called “crash-reports”.
  6.           

  7. Then click on the newest crash report to open it, by default the newest crash report will be the one at the bottom. This will download it to your computer.

  8. Click the downloaded crash report to open it in your default text editor.

FileZilla:

  1. Use FileZilla to access your server files by logging in. If you’re having issues with this, we have a guide on how to get started using FileZilla here.
  2. On the bottom right hand side file browser, locate the “crash-reports” folder, this will be at the bottom of your server file list by default.
  3.           

    • Locate the newest crash report, this will be the top file by default. You can open it in 1 of 2 ways:
    1. Double click the file to download it to your computer, where you can open it on your PC.
    2. Right-click the file and select “View/Edit” to instantly open it with your default text program.

HOW TO READ A CRASH REPORT

A typical crash report will look like the following:

---- Minecraft Crash Report ----

// My bad.

Time: 2/5/19 10:10 PM
Description: Exception ticking world

java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
at java.util.ArrayList$Itr.next(ArrayList.java:859)
at net.minecraft.server.v1_12_R1.PlayerChunkMap$3.a(PlayerChunkMap.java:71)
at net.minecraft.server.v1_12_R1.PlayerChunkMap$3.computeNext(PlayerChunkMap.java:98)
at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:145)
at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:140)
at net.minecraft.server.v1_12_R1.WorldServer.j(WorldServer.java:455)
at net.minecraft.server.v1_12_R1.WorldServer.doTick(WorldServer.java:306)
at net.minecraft.server.v1_12_R1.MinecraftServer.D(MinecraftServer.java:742)
at net.minecraft.server.v1_12_R1.DedicatedServer.D(DedicatedServer.java:371)
at net.minecraft.server.v1_12_R1.MinecraftServer.C(MinecraftServer.java:651)
at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:555)
at java.lang.Thread.run(Thread.java:748)

A detailed walkthrough of the error, its code path and all known details is as follows:
[...]

The quickest way to find the cause of a crash report is to look at the “Description:” part of the report. This will often describe what caused the crash. If you are having issues understanding what the description means, then you can always copy and paste it into google, as this will often bring up pages where other people are having the same issue as you. Despite this, there are some common errors that you could have on your crash report:

Ticking Entity - This most likely means that there is a corrupt entity in your world, this type of world corruption is most likely to be fixable without loosing the whole world (but is much easier to fix by generating a new world).

Ticking World - This most likely means that the entire world itself is corrupt, this is usually caused by changing your version of Minecraft (creating a new world should fix this).

There’s plenty of other crash reasons, and even more if you are running a modded server, so if you’re still having issues with your server feel free to submit a ticket so that our Technical Team can take a look at your crash report for you. When making a ticket we suggest uploading the crash report to a website such as pastebin, making it easier for us to read.

 

If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php

Mitchell Smith

Managing Director @ Shockbyte

  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

BlackSpigot Error

If you're receiving the error "Please contact BlackSpigotMC. 0x0" and your server isn't starting,...

Set PluginClassLoader as parallel capable

If you're receiving the error "Set PluginClassLoader as parallel capable" and your server isn't...

My Minecraft server won't start

If your server isn't starting, it could be caused by a variety of issues. The steps below should...

MalformedJSONException: Resolving JSON Parsing Errors

An invalid .json configuration file can cause your server to crash or plugins/mods to...

How to Fix Errors in YAML (.YML) Config Files

We have a video tutorial on fixing YAML (.yml) configuration errors:   When...