Directly contact our Support Team

GravityZone LogCollector for troubleshooting

Bitdefender GravityZone provides full visibility into organizations' overall security posture, global security threats, and control over its security services that protect virtual or physical desktops, servers and mobile devices. All Bitdefender's Enterprise Security solutions are managed within the GravityZone through a single console, Control Center, that provides control, reporting, and alerting services for various roles within the organization.

This article describes how to use the LogCollector scripts provided by Bitdefender to generate system logs, that will help Bitdefender 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 below commands can gather full product logs.

  • systeminfo -> Gather system information: dmesg; IP; memory info; CPU info; running processors; listening ports; diginfo; package versions; service status; rabbit 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

Important:

It is highly recommended to use the following commands in situations where specific logs are required and only assisted by Bitdefender Enterprise Support team.

Make sure to 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.

Using the LogCollector scripts

To gather logs without debug logging enabled follow the below steps:

  1. Copy the logcollector.tgz file to /home/bdadmin/ (you can use WINSCP to copy the file).
  2. Connect to a GravityZone CLI (you can use PUTTY as well).
  3. Once you have logged as bdadmin, type sudo su and the password for bdadmin.
  4. Type cd /home/bdadmin/ to go to the directory where logcollector.tgz was copied.
  5. Run the command tar xzvf logcollector.tgz.
  6. Run ls -liah and you should see the file: logcollector
  7. Run the command: ./logcollector all save
  8. Using WINSCP, copy the logs on your Windows machine.
  9. Send the gzlogs_hostname_timestamp.tar.gz file, together with a detailed description of the issue, to the following email address: gzn-gs@bitdefender.com.
    A member of of Bitdefender Enterprise Support team will contact you shortly.

Command examples:  

  • To gather all logs without debug logging enabled:
    ./logcollector all save
  • To enable debug logging for the console processors, gather all logs and disable debug logging:
    ./logcollector enableprocessor all save disableprocessor
  • To enable debug logging for the console processors, gather processors logs and disable debug logging:
    ./logcollector enableprocessor processorlogs save disableprocessor
Can't find a solution for your problem? Open an email ticket and we will answer the question or concern in the shortest time possible.

Rate this article:

Submit