Manually Start EDR Server Services

Products

• Carbon Black EDR (formerly Cb Response)

Issue/Introduction

Manually start services in the correct order if the automatic service start times out

Environment

• EDR: 7.4.0 and Higher

Resolution

1. Check what the last service to start-up was by running
   • service cb-enterprise status
2. Manually start services in the following order, beginning on the service right after the last service running in the above command
   • /usr/share/cb/cbservice cb-pgsql start
   • /usr/share/cb/cbservice cb-datagrid start
   • /usr/share/cb/cbservice cb-redis start
   • /usr/share/cb/cbservice cb-rabbitmq start
   • /usr/share/cb/cbservice cb-solr start
   • /usr/share/cb/cbservice cb-coreservices start
   • /usr/share/cb/cbservice cb-sensorservices start
   • /usr/share/cb/cbservice cb-datastore start
   • /usr/share/cb/cbservice cb-liveresponse start
   • /usr/share/cb/cbservice cb-allianceclient start
   • /usr/share/cb/cbservice cb-enterprised start
   • /usr/share/cb/cbservice cb-nginx start
      

Additional Information

The default timeout for services startup is 5 minutes this can be changed using the steps here