Debug Logs
Mumara offers comprehensive logging services to help you track activity within your application, including message logs and system error logs. The Debug Logs viewer provides tools to browse, search, and manage log files for troubleshooting issues and monitoring application health.
Navigate to Tools → Logs → Debug Logs to access the log viewer.
Log Viewer Interface
The Debug Logs page features a Log Viewer with two main tabs: Dashboard for an overview of log distribution, and Logs for browsing and managing individual log files.
Dashboard Tab
The Dashboard tab provides a visual overview of your log entries across all severity levels.
Log Distribution Chart
A donut chart displays the distribution of log entries by severity level, with different colors representing each level. This visualization helps you quickly assess the overall health of your application - a chart dominated by Info entries is normal, while large Error or Critical segments warrant investigation.
Level Summary Cards
Below the chart, cards display statistics for each log level:
| Card | Description |
|---|---|
| All | The total number of log entries across all files and severity levels, shown with a percentage (always 100% for this card) |
| Emergency | System is unusable - these are the most severe errors indicating complete failure requiring immediate attention |
| Alert | Action must be taken immediately - critical issues that need urgent intervention but the system may still be partially functional |
| Critical | Critical conditions - serious errors that affect major functionality but don't render the entire system unusable |
| Error | Error conditions - problems that prevented an operation from completing successfully but don't affect overall system stability |
| Warning | Warning conditions - potential problems that should be addressed but haven't caused failures yet |
| Notice | Normal but significant conditions - noteworthy events that aren't errors but may be worth reviewing |
| Info | Informational messages - routine operational messages that confirm the system is working as expected |
| Debug | Debug-level messages - detailed diagnostic information only useful during development or troubleshooting |
Each card shows the entry count and percentage of total logs. Click any card to filter the Logs tab to show only entries of that severity level.
Logs Tab
The Logs tab displays log files organized by date, with counts for each severity level and actions for managing individual files.
Table Columns
| Column | Description |
|---|---|
| Date | The date of the log file in YYYY-MM-DD format - Mumara creates a separate log file for each day, making it easy to find logs from specific dates |
| All | The total number of log entries in this day's log file across all severity levels |
| Emergency | Count of emergency-level entries for this date - any number above zero requires immediate attention |
| Alert | Count of alert-level entries that need urgent action |
| Critical | Count of critical errors logged on this date |
| Error | Count of error entries - these are common and indicate failed operations that should be investigated |
| Warning | Count of warning entries - potential issues that haven't caused failures yet |
| Notice | Count of notable but non-error events |
| Info | Count of informational messages - typically the largest number, showing normal operations |
| Debug | Count of debug-level messages - only populated when debug logging is enabled |
| Actions | Three action buttons for each log file (see below) |
Action Buttons
Each row has three action buttons:
| Button | Description |
|---|---|
| View (magnifying glass) | Opens the log file to view individual entries, filter by level, and search for specific content |
| Download (download icon) | Downloads the raw log file to your computer for offline analysis, sharing with support, or archival |
| Delete (red trash) | Permanently removes the log file from the server - use with caution as deleted logs cannot be recovered |
View Log File
Clicking the View button on any log file opens the detailed log viewer for that specific date.
Page Header
The page displays "View Log File" with the subtext "Inspect the log file to review detailed records of system events, errors, and activities." The date is shown as "Log [YYYY-MM-DD]" to confirm which log file you're viewing.
Levels Filter (Left Sidebar)
The left sidebar provides quick filtering by severity level:
| Level | Description |
|---|---|
| All | Show all entries regardless of severity - the count shows the total number of entries in this log file |
| Emergency | Filter to show only emergency-level entries |
| Alert | Filter to show only alert-level entries |
| Critical | Filter to show only critical entries |
| Error | Filter to show only error entries - often the most useful filter when troubleshooting problems |
| Warning | Filter to show only warning entries |
| Notice | Filter to show only notice entries |
| Info | Filter to show only informational entries - useful for reviewing normal operations |
| Debug | Filter to show only debug entries |
Each level shows a count indicating how many entries of that type exist in the current log file. Click any level to filter the entries displayed in the main area.
Log Info Panel (Right Side)
The top of the right panel displays metadata about the current log file:
| Field | Description |
|---|---|
| File path | The full server path to the log file - useful for accessing logs directly via SSH or file manager if needed |
| Log entries | The total number of entries in this log file, shown as a badge |
| Size | The file size of the log - large sizes may indicate excessive logging or many errors |
| Created on | The timestamp when this log file was first created |
| Updated at | The timestamp of the most recent entry written to this file |
| Download | Button to download this specific log file |
| Delete | Button to permanently delete this log file |
Search
A search box allows you to find specific entries within the log file. Type keywords like error messages, file names, user IDs, or any text that might appear in log entries, then click the search button to filter results.
Log Entries Table
The main area displays individual log entries in a table:
| Column | Description |
|---|---|
| Environment | The application environment where this entry was logged, typically "production" - helps identify if logs are from production, staging, or development environments |
| Level | The severity level of this entry, shown with a colored badge matching the level (Error entries show red badges, Info shows blue, etc.) |
| Time | The exact time this entry was logged, shown in HH:MM:SS format - useful for correlating errors with user-reported issues |
| Header | The log message summary showing what happened - click on an entry to expand and view the full message, context data, and stack traces for errors |
Log Levels Explained
Understanding log severity helps you prioritize which entries need attention:
| Level | Severity | When It's Used |
|---|---|---|
| Emergency | Highest | System is completely unusable - requires immediate action |
| Alert | Very High | Immediate action needed - system is severely degraded |
| Critical | High | Critical component failure - major functionality affected |
| Error | Medium-High | An operation failed - should be investigated and fixed |
| Warning | Medium | Something unexpected happened but didn't cause failure - may lead to errors if ignored |
| Notice | Low-Medium | Significant but normal events - worth noting but not concerning |
| Info | Low | Routine operational messages - confirms normal system behavior |
| Debug | Lowest | Detailed diagnostic data - only enable when actively troubleshooting |
Common Error Patterns
Database Connection Errors
SQLSTATE[HY000]: Connection refused
This indicates the application cannot connect to the database server. Check that MySQL/MariaDB is running, verify database credentials in your configuration, and ensure the database server allows connections from the application server.
SMTP/Mail Errors
Connection could not be established with host
Email sending failed due to SMTP connection issues. Verify your SMTP server settings, check that the SMTP port isn't blocked by a firewall, and confirm the SMTP credentials are correct.
Permission Errors
file_put_contents(): Permission denied
The application cannot write to a file or directory. Check that the web server user has write permissions to the storage, cache, and logs directories. Common fix: chmod -R 775 storage and chown -R www-data:www-data storage.
Memory Errors
Allowed memory size exhausted
A PHP script ran out of memory. This may indicate a memory leak, an operation processing too much data at once, or simply that the PHP memory_limit needs to be increased in php.ini.
Queue/Job Errors
MaxAttemptsExceededException
A queued job failed too many times and was marked as failed. Check the Failed Jobs section to see the specific job and error, then investigate why the job keeps failing.
Best Practices
Regular Monitoring
- Check errors daily - Review the Error and Critical counts on the Dashboard to catch problems early
- Watch for trends - A sudden increase in errors may indicate a new bug, infrastructure issue, or attack
- Correlate with events - If users report problems, check logs from that timeframe to identify the cause
- Monitor disk space - Large or numerous log files can fill up disk space, especially with debug logging enabled
Log Management
- Don't run debug in production - Debug-level logging generates large volumes of data and can impact performance; only enable temporarily when troubleshooting
- Set appropriate retention - Keep logs long enough for troubleshooting and compliance, but delete old logs to conserve disk space
- Download before deleting - If you might need logs for future reference, download them before deleting from the server
- Archive for compliance - Some industries require log retention; archive important logs to external storage
Troubleshooting Workflow
- Start with the Dashboard - Get an overview of log distribution and identify problem dates
- Filter by Error level - Focus on errors first since they indicate actual failures
- Use Search - Look for specific error messages or affected components
- Review timestamps - Correlate log times with when issues were reported
- Expand entries - Click on errors to see full stack traces and context data
- Check patterns - Look for recurring errors that might indicate a systemic issue
Troubleshooting
No Logs Appearing
Possible causes:
- Logging is disabled in Application Settings
- The storage/logs directory doesn't have write permissions
- Log files are being written to a different location
Solutions:
- Check the Reporting Level in Settings → Application Settings → Logs Tab
- Verify storage/logs directory permissions (should be writable by web server)
- Check your .env file for LOG_CHANNEL and LOG_PATH settings
Log Files Growing Too Large
Possible causes:
- Debug logging is enabled in production
- High error rate from an unresolved bug
- Excessive logging from a specific feature
Solutions:
- Set reporting level to Error for production (not Debug or Info)
- Investigate and fix the root cause of frequent errors
- Implement log rotation at the server level
- Configure automatic log cleanup in cron settings
Cannot Delete Log Files
Possible causes:
- File permission issues
- File is currently being written to
- Disk is full
Solutions:
- Check file ownership and permissions
- Try again after a few minutes
- Use SSH to delete files directly if the web interface fails
- Free up disk space if the server is full
Next Steps
- Activity Logs - Monitor user actions within the application
- Authentication Logs - Review login and security events
- ESP Callbacks - View email delivery callback data
- Failed Jobs - Manage failed background jobs
- Application Settings - Configure logging behavior