Things may not go as expected and your server may suddenly crash unexpectedly. To help you locate the issue, make sure to read through this guide. If you are still stuck then don't hesitate to open a ticket where one of our Support Team members will assist you.

Crash: High CPU Usage

If your server crashes and says "_Your server has been stopped automatically due to it using in excess of 350% CPU usage for a prolonged amount of time._" then, as stated, your server is using a large amount of CPU usage. This could be due to many things, such as large worlds, pre-generating chunks, setting up Dynmap, plugins or even player's actions. To help you find out the cause, see our guide on How to make a timings report with PaperSpigot. From there you can use the timings report to identify what is using up your server resources.



Crash: Ports

If your server crashes and says "_Your server has been stopped due to you using a port that belongs to another server. This is usually within a query port._" then your server is taking up a port which is reserved for another server. This crash could occur out of the blue, as it only happens when the server the port is intended for starts up. You need to make sure that the server query port in the server.properties is disabled or set to a value between 8000 to 8200, and make sure any plugins that use ports (such as Votifier or Dynmap) also use a port between 8000-8200.

If it says "Failed to bind to port" then please try starting your server back up in 60 seconds. As stated above, servers using your port will be stopped so you can use the port assigned to you. If the issue still persists numerous times, or you get both the errors stated in this section, then please open a billing ticket and we will assist you.



Crash: Excessive disk space

Whilst we do offer unmetered disk space, we do have a fair usage policy, too, depending on the node. If you use too much disk space to a scale where it could affect other clients, we will stop your server and inform you. We do this when your server reaches 75GB, then you can request a whitelist if your server needs it.

You will know if you are using too much disk space as your server will crash with the message "_Your server is exceeding our fair usage policies by using XGB / 75GB._".

If you get this message and you have Dynmap, please remove the Dynmap files (excluding the config.yml) then change to a lower resolution to reduce disk usage.

We will not offer a whitelist to your server if:
Your plugins are a large contributor in you reaching over 85GB (e.g. Dynmap is using a large amount);
Your server is storing backups (this is against our TOS, we offer backups from only $1/month!).

We will offer a whitelist to your server if:
Your world(s) are the largest contributors in you reaching over 85GB;
You have a valid reason for requiring that much disk space.



Crash: World Issues

Your world can cause your server to crash for a number of reasons. Below will be examples of crashes caused by worlds and an explanation of the issue;

Example 1 - Wrong Version: https://pastebin.com/qusjCbUW
If you generate or update a world to a newer version and then changing back to an older version. Older Minecraft servers cannot understand the newer worlds, and so they cannot start.
These kinds of errors usually include one of the following at the top of the error:
net.minecraft.server.<version>.NBTTagCompound.a
net.minecraft.server.<version>.NBTTagCompound.load



Fixing the world being the wrong version:

Delete your worlds and restart your server; or
Switch back to the newer version the world was made or upgraded on; or
Switch back to the newer version the world was made or upgraded on, use WorldEdit to save your buildings as a schematic, delete the world and switch back to the old version, paste in the structures. [Only works if the structures have no new blocks.]

Example 2 - Corrupted Chunk: https://pastebin.com/hsdfAexL
Sometimes, world chunks can become corrupted and cause your server to crash. These crashes are usually obvious, containing one of the following lines:
net.minecraft.server.<version>.ChunkSection.a
net.minecraft.server.<version>.Chunk.a



Fixing a corrupted chunk:

Delete your worlds and restart your server; or
Use RegionFixer on your world, located here. Note that Mac users need Python 2.7, Windows users can use the Windows executable file.

Example 3 - Session lock: https://pastebin.com/7BZu9Na8
Sometimes the server may not be able to access the session.lock file in your world. This can cause many issues, so the server will crash to prevent issues. There is only one fix for this, which is to access your server files, open the "world" folder, and delete the session.lock file

Crash: Other

Example 1 - YAML Crashes: https://pastebin.com/0iJneEEa
Sometimes, your server may crash due to errors in a YML file. This is unlikely to be a plugin-side issue, those usually just throw errors, however it's not impossible. This is likely from BungeeCord's config.yml, Bukkit's bukkit.yml, Spigot's spigot.yml, etc. Make sure to read through both of the sections below so you can find the exact cause.

Most of the time, YAML crashes are not due to plugins. Usually, these will say the file it is located in right at the top as the server tries to load them in:
[Server] ERROR Could not load spigot.yml, please correct your syntax errors
The error will tell you where the issue is. We recommend using https://yamllint.com just to make sure as it pinpoints exactly where the issue is and tells you what is causing it.

If you have tried to fix your YAML file(s) and are still having issues with it, feel free to open a ticket and we'll help you.

Example 2 - Plugin Crashes: https://pastebin.com/mMk58Mg0
This is the most common type of crash. This is where a plugin causes your server to crash.
When reading these crash reports, always look between the two sections that say "_Server thread dump_" and "_Entire Thread Dump_" and try to find any plugins mentioned in there. In the example above, we can see "_com.earth2me.essentials.spawn_" which tells us this crash is from Essentials Spawn. From here, you can contact the author of the plugin.

Was this article helpful?
Thank you!