CB Response: Redis fails to start after upgrade to 6.4
book
Article ID: 289686
calendar_today
Updated On:
Products
Carbon Black EDR (formerly Cb Response)
Issue/Introduction
- Upgrade fails to start services starting at redis
- /var/log/messages shows a segfault due to Cylance
- No information is logged in redis logs
Environment
- CB Response Server: 6.4
- Cylance Installed
Cause
Cylance is blocking redis from starting
Resolution
- To start services up
- Stop Cylance
- Start Response
- As a permanent solution Cylance will need to stop blocking Redis
- Disable Memory Protection in Cylance
- Add Redis to exclusions in Cylance
Additional Information
- If the upgrade had not completed, run /usr/share/cb/cbupgrade after disabling Cylance. This will also start services up once complete
- Cylance service may be named cylancesvc or cyprotect on the server
Feedback
thumb_up
Yes
thumb_down
No