Minecraft server getting killed on 2GB RAM droplet

  • Posted on November 10, 2013
  • me184910Asked by me184910

I have a droplet with the 2GB ram configuration. I installed a Vanilla Minecraft server, I hopped on (just me on it), and the server crashes after 30 seconds. There is no crash log, except for “Killed”. This is the command I use to start the server on the screen:

java -Xmx1024M -Xms1024M -jar mcserver.jar nogui

This is the standard 1.7.2 Minecraft.

Anybody knows what’s going on?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @me184910,

The killed command means your Droplet killed the process because the Droplet didn’t have enough RAM to keep the services active. It’s called an OOM killer, out of memory.

My first suggestion would be to add SWAP to your Droplet. You can see how to do that here:

I won’t recommend more than a GB of SWAP to be added.

Regarding priority, you can’t simply just do that, other services also require RAM so you’ll need to make there is enough for everybody so to say, otherwise your Droplet will start killing processes.

As such, try with the SWAP and if that doesn’t work, I’ll suggest upgrading to the next plan.

@gagnon, how much swap space did you allocate? I’m going through the same issue right now and I’m curious what we’ve all been trying that doesn’t work.

Forgot to mention that I have plenty of swap space available… Other than high CPU usage, RAM is fine and swap usage is barely nonexistent. I think DigitalOcean is killing it because it’s using too much CPU