Direct answer

On Linux/container hosting, exit code 137 commonly means the Java process was killed with SIGKILL, often because the host/container ran out of allowed memory or an external supervisor killed it. Confirm the panel/OS logs because exit-code meanings can be wrapper-specific.

What it means

Check host or container memory pressure and forced termination instead of treating code 137 as a Minecraft-specific crash message.

Exit code 137 vs. 1

On Unix/container hosting, 137 is commonly 128 + SIGKILL (9), so check host/container/panel evidence for an external kill. Exit code 1 is the separate generic application-failure case.

If you are a player

  • This is a server-side startup problem. Send the owner the exact panel/console error; reinstalling your game client will not fix it.

If you run the server

Targeted diagnosis: On Linux, exit code 137 normally means the process ended from SIGKILL (128 + 9), which can occur with an out-of-memory killer, container limit or manual kill; the code alone does not prove OOM.

  1. Read the first Java/JVM error before the final “server stopped” or panel exit-code summary.
  2. Run java -version in the same shell/container/panel runtime that actually launches the server.
  3. Verify the Java release and JVM arguments against the exact server software/version; remove old or copied flags that the current runtime rejects.
  4. Fix startup/runtime selection before changing world or plugin data, because Minecraft may not have started yet.

Fix and verify: Inspect journalctl -k or the host/container OOM event history and compare heap settings to the total limit. For cgroup v2, cat /sys/fs/cgroup/memory.events can show memory event counters. Allow headroom for native memory instead of equating -Xmx with total process memory.

Important notes

  • Exit-code conventions vary across hosting wrappers. Treat 137 as a strong clue to an external kill in Unix/container environments, then confirm with host/panel logs.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000