Question 1

How do I read a Minecraft crash report?

Accepted Answer

Minecraft crash reports contain key sections: the crash description at the top, the stack trace showing the error origin, and system details. Look for lines starting with 'Caused by:' or 'at' followed by mod names to identify the problematic mod. Our analyzer highlights these automatically.

Question 2

What causes 'Out of Memory' errors in server logs?

Accepted Answer

Out of Memory errors occur when your server runs out of allocated RAM. Common causes include too many mods/plugins, memory leaks from buggy mods, too many loaded chunks, or insufficient RAM allocation. Increase your server's RAM or reduce mod count to fix this.

Question 3

How do I find which mod is crashing my server?

Accepted Answer

Look for mod names in the stack trace, especially after 'Caused by:' lines. The error often mentions the mod's package name (like 'com.modname'). You can also check the 'Mod List' section in crash reports. Remove mods one by one to identify the culprit if unclear.

Question 4

What do WARNING and ERROR mean in logs?

Accepted Answer

WARN/WARNING indicates potential issues that don't stop the server but may cause problems. ERROR indicates serious issues that may affect server operation. FATAL/SEVERE errors usually cause crashes. Focus on ERROR and FATAL messages first when troubleshooting.

Server Log Analyzer

Log Input

Supported Log Types

Analysis Results

Debug Server Issues Fast

Frequently Asked Questions

Need Help Fixing Server Issues?