View Server Logs

Accessing Server Logs

Method 1: Through Panel Console

1. Log in to your panel
2. Navigate to your server from the dashboard
3. Click on the Console tab
4. View real-time logs as they appear
5. Use the console to execute commands and see output

Method 2: Through File Manager

1. Open the File Manager
2. Navigate to the logs/ folder (location varies by server type)
3. Open log files to view their contents
4. The most recent log file name varies by server type

Understanding Log Files

Current Log Files

The current server log file location and name varies by server type:

• Location: Usually in a logs/ folder
• Content: Current session logs
• Size: Grows continuously (may be rotated periodically)
• Format: Text files, may be compressed

Historical Logs

Older log files are typically:

• Named with timestamps or sequence numbers
• May be compressed (.gz, .zip) to save space
• Stored in the same logs directory
• Automatically archived by the server

Reading Log Entries

Log Format

A typical log entry looks like this:

[HH:MM:SS] [Thread/Level]: Message

Example (format varies by server type):

[14:23:45] [Server thread/INFO]: Starting server...
[14:23:46] [Server thread/INFO]: Loading configuration
[14:23:47] [Server thread/INFO]: Server started successfully

Log Levels

Logs use different levels to indicate importance:

• INFO: Normal operation messages
• WARN: Warnings about potential issues
• ERROR: Error messages that need attention
• FATAL: Critical errors that may crash the server
• DEBUG: Detailed debugging information (if enabled)

Common Log Messages

Server Startup

Log messages during startup vary by server type, but typically include:

• Server version information
• Configuration loading messages
• Initialization steps
• Port binding information
• Ready/started confirmation

Player/User Activity

Connection and activity messages depend on your server type:

• User login/logout events
• Connection information
• Activity logs
• Authentication messages

Errors

Error messages help identify issues:

• Exception stack traces
• Configuration errors
• Resource warnings
• Plugin/mod loading failures
• Performance warnings

Using the Console

The console provides real-time log viewing and allows you to:

View Live Logs

• See messages as they happen
• Scroll through recent history
• Filter or search for specific messages

Execute Commands

• Type commands directly in the console
• See command output immediately
• Useful for server management

Common Console Features

• Auto-scroll: Automatically scrolls to show latest messages
• Search: Find specific text in logs
• Filter: Show only errors, warnings, or specific types
• Clear: Clear the console display (doesn't delete logs)

Troubleshooting with Logs

Server Won't Start

1. Check the end of the most recent log file for error messages
2. Look for FATAL or ERROR entries
3. Common issues:
   • Port already in use
   • Invalid configuration
   • Missing files or dependencies
   • Version incompatibility
   • Insufficient resources

Plugin/Mod Errors

1. Search logs for the plugin/mod name
2. Look for ERROR entries related to the plugin/mod
3. Check for missing dependencies
4. Verify compatibility with server version
5. Review configuration issues

Performance Issues

Look for performance-related warnings in logs:

• Memory warnings
• CPU overload messages
• Lag indicators
• Resource exhaustion errors

Check:

• Resource usage (RAM, CPU)
• Server performance metrics
• Number of active connections/users
• Background processes

Connection Issues

Search for connection-related errors:

• Network errors
• Authentication failures
• Timeout messages
• Connection refused errors

These can indicate:

• Network configuration issues
• Firewall problems
• Server overload
• Authentication/authorization problems

Log File Management

Log Rotation

Logs are automatically rotated to prevent files from growing too large:

• Old logs are compressed (.gz)
• New log files are created periodically
• Old logs are deleted after a retention period

Downloading Logs

To download logs for analysis:

1. Open File Manager
2. Navigate to the logs/ folder (location varies by server type)
3. Download the log files you need
4. Share with support if needed for troubleshooting

Clearing Logs

Warning: Only clear logs if you understand the consequences.

1. Stop the server
2. Delete or rename log files in the logs directory
3. Start the server (new log files will be created)

Advanced Log Analysis

Searching Logs

Use text search in the panel console or downloaded logs to find:

• Specific usernames or player names
• Error messages
• Plugin/mod names
• Timestamps
• IP addresses
• Specific events

Log Analysis Tools

For advanced analysis, you can:

• Download logs and use text editors with search
• Use command-line tools (grep, awk) on Linux
• Use log analysis software
• Parse JSON logs if available

Monitoring Logs

Set up monitoring for:

• Error frequency
• Player connection issues
• Performance warnings
• Security events

Best Practices

Regular Monitoring

• Check logs daily for errors
• Review warnings weekly
• Monitor during peak usage
• Check after making changes

Log Retention

• Keep important logs backed up
• Don't delete logs immediately
• Archive logs before major updates
• Maintain logs for troubleshooting history

Error Response

When you see errors:

1. Read the full error message
2. Check context (what happened before)
3. Search for solutions online
4. Document the issue and resolution
5. Backup before making fixes

Common Log Patterns

Successful Startup

A successful startup typically shows:

• Server initialization messages
• Configuration loading confirmations
• Service binding confirmations
• Ready/started status messages

Normal Operation

Normal operation logs show:

• Regular activity messages
• User connection/disconnection events
• Scheduled task executions
• Routine status updates

Problems

Problem indicators include:

• WARNING messages about issues
• ERROR messages about failures
• FATAL messages about critical problems
• Exception stack traces