EDR Server: Service won't start after upgrade to 7.6.x due to Postgres version compatibility
search cancel

EDR Server: Service won't start after upgrade to 7.6.x due to Postgres version compatibility

book

Article ID: 289811

calendar_today

Updated On:

Products

Carbon Black EDR (formerly Cb Response)

Issue/Introduction

  • Services will not start after upgrade
  • Service startup logs show config files cannot be found
  • postgres startup.logĀ 
    • database files are incompatible with server
      The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 13.5.

Environment

  • EDR Server: Upgrade to 7.6.x

Cause

  • Services were not properly stopped before the upgrade
  • cbupgrade has not been run

Resolution

  1. Stop services
  2. Run /usr/share/cb/cbupgrade
    • If cbupgrade complains about postgres, manually stop and start the postgres 10 service and rerun cbupgrade
    • sudo -u cb /usr/pgsql-10/bin/pg_ctl start -w -l /var/log/cb/pgsql/setup.log -D /var/cb/data/pgsql -o "-p 5002"'
      
      sudo -u cb /usr/pgsql-10/bin/pg_ctl stop -w -l /var/log/cb/pgsql/setup.log -D /var/cb/data/pgsql -o "-p 5002"'
  3. Once upgrade completes either let cbupgrade start services or manually restart services

Additional Information

If /etc/yum.repos.d/CarbonBlack.repo has the value enabled=1, the service will upgrade if 'yum update' is run. To prevent this, change the value to enabled=0