Troubleshooting Java Error Exit Codes
Reference for common Java exit codes and what they mean for your Minecraft server.
When your server crashes, it exits with a numeric code. This code helps identify the cause of the crash.
Common Exit Codes
| Exit Code | Meaning | Common Cause | Fix |
|---|---|---|---|
| 0 | Normal shutdown | Server stopped gracefully | Not an error |
| 1 | General error | Plugin/mod error, config issue | Check Console for the error message |
| 137 | Out of Memory (OOM) | Server ran out of RAM | Increase RAM in Startup, use Aikar's Flags |
| 143 | SIGTERM | Server was forcefully stopped | Normal when stopping from panel |
| -1 | Unknown error | Various causes | Check Console and crash reports |
| 127 | Command not found | Missing Java installation | Check Java version in Startup |
| 255 | General failure | Various | Check Console for details |
Exit Code 137 (Most Common)
This is the most frequent crash code. The server ran out of memory and was killed by the system.
Fixes:
- Increase RAM allocation in
Startup - Apply Aikar's Flags for better memory management
- Reduce view distance and simulation distance
- Remove heavy plugins/mods
- Install Spark and check
/spark healthfor memory usage
Exit Code 1
This means the server encountered an error during startup or operation.
Fixes:
- Check
Consolefor the first error message (not the last) - If you recently added a plugin/mod, try removing it
- Check for YAML errors in config files
- Verify Java version compatibility
💡 Tip: The exit code alone isn't always enough — always check
Consoleoutput and crash reports for the actual error message.
See also: Server Won't Start | How Much RAM
If you need help, join our Discord.
How is this guide?
40% Off — Limited TimeGet your Minecraft server todayInstant setup, DDoS protection, and 24/7 support included.
Get a Server