Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

Dependency issue on RedHat results in failed Carbon Black install or upgrade

Dependency issue on RedHat results in failed Carbon Black install or upgrade


This solution applies when installing or upgrading all versions of Carbon Black.



Installing or upgrading Carbon Black fails on RedHat installations indicating there is a dependency issue.



During the install/upgrade procedure, the following or similar message is observed in the console's standard out:


Error: Package: wxGTK-2.8.12-1.el6.x86_64 (CarbonBlack)




  • The cause is that Carbon Black is not installed on CentOS. On a CentOS installation, the file will exist:
  • Within the file there is an [extras] section, which allows other extra packages to be downloaded that Carbon Black requires. The necessary wxGTK package is retrieved from this [extras] repository.
  • On an OS that is not CentOS, for example RedHat, the CentOS-Base.repo file will not exist. This means the wxGTK package must be retrieved elsewhere. Please refer to the Server Sizing Guide for more details on supported operating systems.
  • To confirm a CentOS versus RedHat installation, review the output from the command:
# lsb_release -a



To download and install the package on RedHat

  1. Refer to this FAQ EPEL/FAQ before installing the EPEL package.
  2. Download epel-release-6-8.noarch.rpm RPM from the URL above, where 6.8 is the recent EPEL release for RedHat 6.
  3. Copy the RPM to your Carbon Black Enterprise Server and run the following to install:
    # rpm -Uvh <rpm_file>
  4. Make sure enabled=1 is set in the [epel] section in the new file /etc/yum.repos.d/epel.repo:
    # grep enabled /etc/yum.repos.d/epel.repo
  5. Perform the Carbon Black installation or upgrade again, and confirm now the wxGTK package is retrieved from the new EPEL repository.
  6. Once the Carbon Black installation or upgrade is complete, disable using this new EPEL repository by editing the file /etc/yum.repos.d/epel.repo and changing enabled=1 to enabled=0.
Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Creation Date: