How to Read and Understand Minecraft Server Logs

Minecraft server logs record what your server is doing, including player connections, commands, warnings, errors, plugin activity, mod activity, and server shutdowns. Reading your logs is one of the most useful ways to troubleshoot crashes, lag, plugin problems, mod conflicts, and other server issues.

Beacon Hosting makes your Minecraft server logs accessible directly from the server control panel, allowing you to review activity in real time and investigate problems without needing access to the server's underlying operating system.

How Do I Access My Minecraft Server Logs?

To access your Minecraft server logs through Beacon Hosting:

1. Log in to your Beacon Hosting control panel.
2. Open the Minecraft server you want to troubleshoot.
3. Navigate to the Logs section.
4. View the server's live console output or available log files.

The live console is useful for monitoring what the server is doing right now, while downloaded log files are useful when investigating an issue that occurred earlier.

What Are Minecraft Server Logs?

Minecraft server logs are text records generated by the Minecraft server and its installed software.

Depending on your server software and configuration, logs can contain information about:

• Server startup and shutdown
• Player connections and disconnections
• Player commands
• World loading
• Plugin activity
• Mod activity
• Server warnings
• Errors and exceptions
• Resource loading
• Network connections
• Authentication
• Server crashes
• Performance problems

Logs are particularly useful because they provide information about what happened immediately before and during a problem.

What Do Minecraft Log Levels Mean?

Minecraft logs commonly contain different severity levels. Understanding these levels helps you determine how serious a message is.

INFO

INFO messages are normal informational messages.

Examples include:

[Server thread/INFO]: Done (12.345s)! For help, type "help"

or:

[Server thread/INFO]: Player123 joined the game

These messages are generally expected and do not indicate a problem.

WARN

WARN or WARNING indicates something that may require attention.

A warning does not necessarily mean that your server is broken.

For example, a plugin may warn about a configuration option, deprecated functionality, or an operation taking longer than expected.

Warnings should be investigated when they repeatedly appear around the time a problem occurs.

ERROR

ERROR indicates that something failed.

Errors can be caused by:

• Plugins
• Mods
• Configuration problems
• Missing files
• Incompatible software
• Database connections
• Network problems
• Invalid commands
• Other server components

An error does not always mean the entire server is going to crash. Look at the surrounding log messages to determine what operation failed and whether the server continued running afterward.

SEVERE

Some server software or plugins may use SEVERE for particularly serious errors.

A SEVERE message deserves investigation, especially if it is followed by a shutdown, crash, or repeated failures.

What Should I Look for in Minecraft Logs?

When troubleshooting a problem, do not simply search for the word ERROR.

Instead, look at the events immediately before and after the problem occurred.

Pay particular attention to:

• ERROR
• WARN
• Exception
• Caused by
• Stack trace
• Failed
• Could not
• Unable
• Crash
• OutOfMemory
• Plugin or mod names
• Repeated messages

The most useful part of an error is often not the first line. The stack trace and the Caused by: section can identify the component responsible for the failure.

How Do I Find the Cause of a Minecraft Crash?

If your Minecraft server crashes, start by finding the point in the log where the server stopped functioning.

Search the logs for terms such as:

ERROR
Exception
Caused by:
Crash
Stopping server

Then work backwards through the log.

Look for:

1. The final error message.
2. The exception type.
3. The Caused by: section.
4. The plugin, mod, or Minecraft class mentioned in the stack trace.
5. Any warnings immediately before the error.
6. Whether the same error occurred repeatedly.

For example, if a stack trace repeatedly references a particular plugin shortly before the server crashes, that plugin is a strong candidate for further investigation.

However, the first plugin or mod mentioned in a stack trace is not automatically the root cause. Java stack traces can pass through multiple components, so the complete exception and Caused by: chain should be considered.

What Is a Java Stack Trace?

A stack trace is a detailed record showing which parts of a Java program were executing when an exception occurred.

Minecraft: Java Edition servers and many of their plugins and mods run on Java, so stack traces are extremely common when troubleshooting server problems.

A stack trace may look complicated, for example:

java.lang.NullPointerException
    at example.plugin.SomeClass.method(SomeClass.java:123)
    at net.minecraft.server.SomeOtherClass.method(SomeOtherClass.java:456)

You do not necessarily need to understand every line.

Instead, look for:

• The exception type
• The plugin or mod name
• The first relevant at line
• The Caused by: section
• Repeated exceptions

How Do I Find Which Plugin Is Causing an Error?

If you suspect a plugin is causing a problem, search the log for the plugin's name.

Plugin errors commonly include the plugin name in messages such as:

[PluginName] ...

or within a stack trace.

You can also look for repeated errors that occur immediately after a specific plugin performs an action.

For example, if an error appears every time a player uses a command provided by a particular plugin, that plugin becomes a strong candidate for investigation.

Before removing a plugin, consider whether the error is caused by:

• An outdated plugin version
• An incompatible Minecraft version
• A missing dependency
• An incorrect configuration
• A conflicting plugin
• A broken or corrupted plugin installation

How Do I Find Which Mod Is Causing a Crash?

Modded servers can be more difficult to troubleshoot because multiple mods may interact with each other.

When investigating a mod-related crash, look for:

• The mod ID
• The mod name
• The exception type
• The Caused by: section
• Missing dependencies
• Version mismatch messages
• Mod loading errors
• Registry errors
• Mixin errors
• Class-loading errors

If the crash log explicitly identifies a mod, start your investigation there.

For modded servers, the crash report can also contain useful information in addition to the normal server log.

How Do I Troubleshoot Minecraft Server Lag Using Logs?

Logs can help identify some causes of lag, but not every performance problem will appear as an obvious error.

When investigating lag, look for messages related to:

• Server ticks taking too long
• Watchdog warnings
• Long-running tasks
• Plugin operations
• Chunk loading
• World generation
• Saving
• Memory problems
• Repeated errors

A common message associated with severe server performance problems may indicate that the server is taking too long to process ticks.

If the server repeatedly reports long tick times, investigate what the server was doing immediately beforehand.

Keep in mind that logs alone are not always sufficient to diagnose performance problems. Performance profiling tools can provide much more detailed information about CPU usage, entities, chunks, plugins, and other sources of server load.

How Do I Troubleshoot a Minecraft Server That Will Not Start?

If your server fails during startup:

1. Start the server.
2. Wait for the startup process to fail.
3. Read the final section of the console.
4. Look for ERROR, Exception, Failed, or Caused by:.
5. Check which plugin, mod, configuration file, or dependency is mentioned.
6. Compare the error with any recent changes to the server.

Recent changes are particularly important.

If the server worked correctly yesterday and stopped starting after installing a new plugin, mod, or configuration change, that change should be one of the first things investigated.

How Do I Troubleshoot a Minecraft Server Crash?

For a server that crashes after previously running normally:

1. Identify approximately when the crash happened.
2. Find the corresponding section of the log.
3. Look for exceptions and errors immediately before the shutdown.
4. Check for a crash report if one was generated.
5. Identify the plugin, mod, or server component involved.
6. Check whether the same error occurred before the crash.
7. Compare the problem with any recent changes.

If the server automatically restarts after crashing, make sure you inspect the logs from the previous server process, not just the new startup messages.

What Does "Can't Keep Up!" Mean in Minecraft?

The message:

Can't keep up! Is the server overloaded?

generally means the server is taking longer than expected to process its scheduled work.

This can occur when the server is under heavy load, such as during:

• World generation
• Large numbers of entities
• Chunk loading
• Redstone-heavy activity
• Plugin operations
• Mod operations
• Large server saves
• CPU-intensive tasks

A single Can't keep up! message does not necessarily indicate a serious problem.

If the message occurs repeatedly, particularly alongside high tick times or noticeable gameplay lag, further performance investigation is recommended.

What Does "OutOfMemoryError" Mean?

An error such as:

java.lang.OutOfMemoryError

indicates that the Java process could not allocate the memory it needed.

Possible causes include:

• The server does not have enough allocated memory
• A mod or plugin is using excessive memory
• A memory leak
• Excessive world or entity activity
• An unusually large workload

Increasing the server's memory allocation can help in some situations, but simply adding more RAM does not fix every memory-related problem.

If the error continues after increasing available memory, investigate which software or workload is consuming the memory.

Should I Send My Entire Minecraft Log to Support?

If you are asking for help with a server problem, providing the relevant log or crash report can make troubleshooting significantly easier.

When possible, provide:

• The time the problem occurred
• What you were doing when it happened
• The relevant section of the log
• The complete error or stack trace
• Any crash report that was generated
• Recent changes to the server

Avoid removing the actual error or stack trace from the report. The surrounding lines can provide important context.

Also remove any sensitive information before sharing logs publicly, such as credentials, tokens, private URLs, or other confidential configuration data.

Minecraft Logs vs. Crash Reports

A server log records ongoing server activity, while a crash report is generated specifically to provide information about a crash.

When troubleshooting a crash, check both if they are available.

The server log can show what was happening immediately before the crash, while the crash report may contain additional information about the exception, server state, and affected components.

Common Minecraft Log Problems

Repeated plugin errors

Repeated errors from the same plugin may indicate:

• An outdated plugin
• An incompatible version
• A configuration problem
• A missing dependency
• A plugin conflict

Check the plugin's documentation and compatibility with your Minecraft server version.

Missing dependency

Some plugins and mods require additional software to operate.

If the log reports that a dependency is missing, install the required dependency or correct the affected configuration.

Version mismatch

Minecraft plugins and mods are often version-dependent.

Check that your:

• Minecraft version
• Server software
• Plugins
• Mods
• Dependencies

are compatible with one another.

Configuration errors

Invalid configuration files can prevent plugins, mods, or even the server from starting correctly.

If a problem started after editing a configuration file, compare the file against the software's default configuration or documentation.

Best Way to Read Minecraft Logs

The most effective way to troubleshoot a Minecraft log is to start with the time the problem occurred, then work through the surrounding messages.

Do not treat every warning as a problem.

Instead:

1. Identify what happened.
2. Find the corresponding timestamp.
3. Read the messages immediately before and after it.
4. Find the exception or error.
5. Follow the stack trace.
6. Look for Caused by:.
7. Identify the affected plugin, mod, or server component.
8. Check for recent configuration or software changes.
9. Test one change at a time.

This approach is much more reliable than searching for random errors and changing multiple server settings at once.

Quick Answer: How Do I Read a Minecraft Server Log?

Start by finding the time the problem occurred, then look for errors, exceptions, warnings, and stack traces around that time. Pay particular attention to Caused by: messages and references to plugins, mods, dependencies, or configuration files.

A log does not necessarily tell you the answer in a single line. Reading the surrounding messages and tracing the exception back to its source is often necessary.

Beacon Hosting Minecraft Server Logs

Beacon Hosting provides access to your Minecraft server logs through the server control panel, making it easier to monitor your server and investigate problems.

If your server is experiencing crashes, errors, or unexpected behaviour, check the logs first. The information in the logs can help identify whether the issue is related to a plugin, mod, configuration, server software, or another component.