Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
maxLevel3


Server Logs (Master & Admin):

Note

Without a Ticket ID, these logs will NOT reach the Support Team.

The server logs contain a heap of information that help us identify certain server issues, including transaction failures. Not all issues can be identified with the server logs, but in many cases these logs can pinpoint a problem that can't be solved any other way. Our development team relies on these logs to find elusive errors.

Method 1: GUI

  1. Navigate to "Send Logs to Support" from the user panel:

  2. Check “Master & Admin Logs”:

  3. Enter the Issue ID (ticket number) provided by Support.

  4. Click “Send”. You’ll receive an email confirmation of submission from Support.

Method 2: CLI

Code Block
sudo /batm/batm-manage send serverlogs
Tip

Include the relevant Support Ticket number!


More information:

Info

The server logs are comprised of 2 files:

  • /var/log/batm/master.log

  • /var/log/batm/admin.log

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

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@10d56
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel in ( "crash" , "cas" , "logs" ) and type = "page" and space = "ESD"
labelscas logs crash
Page Properties
hiddentrue

Related issues