Game server ended with “Exit code 137” (OOMKilled)
What the message means
Exit code 137 means: the process was forcibly ended from the outside, almost always because your server's memory was full. The game itself then writes no error message – the log simply ends.
What it looks like in the log
[20:31:15] [Server thread/INFO]: Saving chunks for level 'ServerLevel[world]'/minecraft:overworld
container@pterodactyl~ Server process exited with code 137 (OOMKilled: true)
container@pterodactyl~ Exit code: 137
container@pterodactyl~ Server marked as offline...
Excerpt from an example log, marked the way the analysis marks it.
Common causes
- The server needs more RAM than the plan has – because of mods, plugins, large worlds or many players.
- On Minecraft: -Xmx is set so high that there's no room left for Java itself.
- A memory leak in a mod, plugin or addon: usage climbs until it's killed.
- Additional programs in the same server (bots, databases) that take up memory.
How to fix it
- Watch the RAM usage in your panel's overview: does it climb slowly or jump up suddenly?
- On Minecraft: set -Xmx about 1 to 1.5 GB below the plan's RAM.
- If usage climbs steadily, look for the leak by removing mods or plugins as a test.
- If the memory isn't enough for what you want to do at all, get a plan with more RAM.