Version
Cb Response 6.x and later versions
Issue
On startup after upgrade to 6.x in a cluster, it does not start successfully and you receive an error: "unable to start service: cb-redis".
Symptoms
Review of the /var/log/cb/redis/startup.log on minions will show messages indicating the following:
Fatal error, can't open config file '/etc/cb/redis.conf' |
Cause
This behavior will occur if the /etc/cb folder permissions are not correct. We have identified in some rare cases the upgrade process will change the permission of /etc/cb on minions which needs to be corrected manual. A permanent fix will be included in a future release.
Solution
Check permissions on minions for /etc/cb, if you see the following output, then you have encountered this permissions issue on minions.
ll /etc |grep cb
d-wxr----t. 18 root root 4096 <date> cb
To address this issue, please take the following steps on all minions:
chmod 755 /etc/cb
Once you have executed the above command on all minions, do a clean shutdown, kill any remaining processes, and then do a clean startup:
on master: /usr/share/cb/cbcluster stop
on master/minion once stop command completes: killall -KILL -u cb (warning: this command will terminate any integrations running as cb, they will need to be restarted)
on master: /usr/share/cb/cbcluster start
