Troubleshooting
Out of Memory (OOM) Errors
Fix Out of Memory errors and prevent crashes on your Cafora server.
An Out of Memory (OOM) error occurs when your server exceeds its allocated RAM. The server crashes and may fail to restart.
Recognizing OOM Errors
In your server logs, look for:
java.lang.OutOfMemoryError: Java heap spaceImmediate Steps
Try starting the server again. Sometimes a restart is enough.
If it fails to start, reduce resource usage before restarting.
Check RAM usage graphs in the Pterodactyl Panel.
Reducing RAM Usage
Lower View Distance
In server.properties:
view-distance=6
simulation-distance=4Remove Heavy Plugins/Mods
- Temporarily disable non-essential plugins
- Remove large mods or modpacks that exceed your plan capacity
Clear Entities
- Run
/kill @e[type=item]to clear dropped items - Reduce mob farms and entity-heavy areas
Pre-Generate World
- Use Chunky to pre-generate terrain
- Prevent runtime chunk generation which spikes RAM usage
Prevention
- Monitor RAM usage regularly
- Watch for memory leak patterns (RAM creeping up over hours)
- Optimize JVM flags for better garbage collection
- Upgrade your plan if you consistently need more memory
If OOM errors persist after optimization, your server needs more RAM than your current plan provides.