Sometimes, we'll need your logs. If we've asked for your logs and you have no idea how to send them, you've come to the right page!
| Info |
|---|
Quick Jump: |
| Table of Contents | ||
|---|---|---|
|
Crash Logs:
| Note |
|---|
Without a Ticket ID, these logs will NOT reach the Support Team. |
The crash logs contain a heap of diagnostic codes that help us identify certain BATM issues. These logs help us solve BATM problems and crashes. Please do not send these logs unless we request them.
Method 1: GUI
Navigate to "Send Logs to Support" for the user panel:
Check “Terminal Crash Logs”:
Enter the Issue ID (ticket number) provided by Support.
Click “Send”. You’ll receive an email confirmation of submission from Support.
Method 2: CLI
Also see: batm-manage: the CAS CLI Toolkit
| Code Block |
|---|
sudo /batm/batm-manage send crashlogs |
| Tip |
|---|
Include the relevant Support Ticket number! |
NOTE: Support may request that you enable “Server Telemetry”.
Telemetry enables your Standalone CAS to automatically send new crash logs to our development server, and is enabled by simply creating an empty file:
| Code Block |
|---|
sudo touch /batm/app/master/server.telemetry |
delete the file to disable Telemetry:
sudo rm /batm/app/master/server.telemetry
| Tip |
|---|
Include the relevant Support Ticket number! |
More information:
Clearing the logs:
In some cases, your logs may have grown too large or numerous to submit. Perhaps you just want to free up space? In that case type this:
| Code Block |
|---|
sudo /batm/batm-manage log clear |
That will delete the admin and master logs.
Afterwards, restart all GB services (to create new, empty log files)
| Code Block |
|---|
sudo /batm/batm-manage stop all sudo /batm/batm-manage start all |
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|