Skip to main content

Use the GravityZone LogCollector

Use the LogCollector scripts provided by Bitdefender to generate system logs, that will help the Bitdefender Enterprise Support team to investigate and resolve product issues.

Overview

Bitdefender offers a logcollector archive, to be used in investigation and troubleshooting, which with the help of the specific commands can gather default product logs (without debug logging enabled).

Using the LogCollector scripts

To gather default logs, follow the below steps:

  1. Connect to a GravityZone CLI.

    You can use PuTTY as well.

  2. Once you have logged in as bdadmin, type sudo su and the password for bdadmin.

  3. Run the apt-get install gz-logcollector -yq command.

  4. Run the logcollector all save command.

  5. Using WinSCP, copy the log file on your Windows machine.

  6. Send the gzlogs_hostname_timestamp.tar.gz file, together with a detailed description of the issue, to the following email address: [email protected].

    A member of the Bitdefender Enterprise Support team will contact you shortly.

Command examples:

  • To gather all default logs:

    logcollector all save

  • To enable debug logging for more than one role:

    logcollector enableprocessor enablecs

  • To gather all advanced logs and disable debug logging for Communication Server and console processors:

    logcollector all save disablecs disableprocessor

Watch a full video tutorial on the topic here:

Available commands

  • systeminfo -> Gather system information: dmesg; IP; memory info; CPU info; running processors; listening ports; diginfo; package versions; service status; RabbitMQ cluster and user status; free space.

  • processorlogs -> Gather all processor logs.

  • ecslogs -> Gather communication server logs.

  • systemlogs -> Gather system logs from /var/log.

  • applogs -> Gather application logs from /opt/bitdefender/var/log.

  • kitlogs -> Gather kit logs from /opt/bitdefender/var/www.

  • svalogs -> Gather Security Server (SVA) logs.

  • dump -> Gather database dump.

  • all -> Run all of the commands, except save and debug logging commands, which have to be run manually.

  • save -> Save all gathered logs into an archive for collecting.

Important

It is highly recommended to use the following commands in situations where advanced specific logs (with debug logging enabled) are required and only assisted by the Bitdefender Enterprise Support team.

You can enable or disable debug logging using the corresponding command for each role:

  • enableprocessor -> Enable debug logging for the console processors.

  • disableprocessor -> Disable debug logging for the console processors.

  • enablecs -> Enable debug logging for the Communication Server.

  • disablecs -> Disable debug logging for the Communication Server.

  • enablearrakis -> Enable debug logging for the Update Server.

  • disablearrakis -> Disable debug logging for the Update Server.

  • enableus -> Enable debug logging for the console Update System.

  • disableus -> Disable debug logging for the console Update System.

  • enablevasync -> Enable debug logging for the GravityZone configuration service.

  • disablevasync -> Disable debug logging for the GravityZone configuration service.

  • enablelurker -> Enable debug logging for GravityZone Incidents server.

  • disablelurker -> Disable debug logging for GravityZone Incidents server.

In this section: