π οΈ Step-by-Step Guide for Troubleshooting
π§ 1. Increase the Debug Level (Optional but Recommended)
To capture as much detail as possible in the log files, it's best to increase the debug level before downloading logs.
π Hereβs how to do it:
-
Open the web interface of your gateway
-
Navigate to:
Configuration β General -
Set a higher Debug Level, for example:
-
Debug
β for extended system messages
-
-
Click Save to apply the change
π‘ Note: A higher debug level will produce more log data β useful for troubleshooting, but not recommended for permanent use.
βRecommendation: Increase the debug level and wait for the issue to occur again to capture meaningful log information.
π₯ 2. Download Log Files
Hereβs how to download the current log files:
-
Go to the web interface
-
Navigate to:
Help β Support -
Click on "Download debug log file"
The file will be saved in .tar.gz
format (e.g. logs.tar.gz
)
π This archive contains system logs, event reports, and SMS debug data β ideal for in-depth analysis.
ποΈ 3. Extract the Log Archive
The downloaded file is a compressed archive. You need to extract it before reviewing the contents.
π₯οΈ Recommended tools:
Windows:
-
7-Zip (recommended)
-
WinRAR
macOS & Linux:
-
Double-click the file
-
Or use this terminal command:
π Once extracted, you'll have access to various log files such as:
-
smsd.log
-
system.log
-
error.log
π What to Do With the Log Files?
π¬ If you're encountering issues, you can send the extracted files to our support team:
support@brevis.one
π Alternatively, you can review the .log
files yourself β much of the content is plain text and includes useful details such as:
-
Timestamps
-
Error messages
-
Status codes
π§ Bonus Tip:
Modern AI tools can be used to analyze log files for debugging β a helpful option for advanced users.
Comments
0 comments
Please sign in to leave a comment.