Browse your product documentation including release notes and installers
The Cb Response 6.2.4 Server Release Notes document provides information for users upgrading from previous versions as well as users new to the Cloud and On-Prem products. It consists of the following sections:
New Features – Describes new and modified features introduced in this sensor release.
Corrective Content – Describes issues resolved by this release as well as more general improvements in performance or behavior.
Known Issues and Limitations – Describes known issues or anomalies in this version.
Contacting Technical Support – Describes ways to contact Carbon Black Technical Support and what information to have ready.
Published: November 7, 2018
Target Cloud GA: November 11, 2018
Target On-Prem GA: November 15, 2018
Please make note to confirm if the clean_requirements_on_remove is turned off in your environment before proceeding with the upgrade.
grep 'clean_requirements_on_remove' /etc/yum.conf
Set to 0 to turn off and run 'yum clean all' before proceeding
If this config was enabled during upgrade and receiving the following error, please use this solution
--------------------------------------------------------------------------------
UPGRADE ABORTED
--------------------------------------------------------------------------------
'rpm -q postgresql93 postgresql93-libs postgresql93-server' failed(2)
@nverrill, posgres93 is installed in versions prior to 6.2.4. When you upgrade to 6.2.4 we want postgres93 to still be installed. When you run /usr/share/cb/cbupgrade our scripts will do an automated migration to postgres10. If postres93 is not installed when trying to run /usr/share/cb/cbupgrade, the migration will not be able to start and thus you will be in a situation where the services will not be able to start.
Both will technically be installed, however after migrations and services have successfully started, you can then remove postgres93 and files.
If you do find yourself in a situation where postgres93 is uninstalled before cbupgrade was run, you can use the following to workaround the issue.
Thank you,
Bryce