Skip to main content

Roles installation issues


This article provides details about how to troubleshoot role installation issues.

This section provides details about how to troubleshoot role installation.


GravityZone appliance can run one, several, or all of the following roles:

  • Database Server

  • Update Server

  • Web Console

  • Communication Server

  • Report Builder Database

  • Report Builder Processors

  • Incidents Server

The GravityZone virtual appliance is available for download here.

A GravityZone deployment requires running at least one instance of the basic roles (Database Server, Update Server, Web Console, and Communication Server).

You can install multiple instances of the Communication Server role or Web Server role, and connect them to other roles via Role Balancers. The built-in Role Balancer cannot be installed together with other roles on the same GravityZone appliance. If you already have third-party balancing software or hardware within your network, you can choose to use them instead of the built-in balancers.

GravityZone roles are installed through the CLI using the option 5 Install/Modify roles.

Database Server and Update Server packages are stored by default on the virtual appliance. You can install them without Internet connectivity.


If the roles installation fails, check the following:

  1. Internet connectivity to server using ping or wget commands.

  2. Your border firewall allows connectivity to and does not block the .deb files.

  3. Check the GravityZone proxy settings configuration (if needed). The connectivity to through a proxy can be checked with the following commands:

    • Proxy with authentication:

      wget -e use-proxy=yes -e http-proxy=http://username:password@PROXY-IP:PROXY-port

    • Proxy without authentication:

      wget -e use-proxy=yes -e http-proxy=http://PROXY-IP:PROXY-port

The troubleshooting log for roles installation is located under: /opt/bitdefender/var/log/installer.log

For further investigations, we recommend collecting a set of logs from the affected endpoint and contacting Bitdefender Enterprise Support. For more information on how to gather the logs, refer to Use the GravityZone LogCollector.