Failure to start services due to cb-supervisord

[#1]

Version

5.1.1 Patch 3 and above

Issue

cb-supervised service fails to start after upgrade to a CB Response version in which supervisord is installed.

Cause

This is caused by having a service user account different then cb set in /etc/cb/cb.conf under the CbUser parameter.

Symptoms

A error message similar to this will show when trying to start services:

node0: Starting cb-supervisord: Error: Invalid sockchown value root:cb
node0: For help, use /usr/bin/supervisord -h
node0:                                                     [FAILED]
node0: Exec failure (1)

Solution

1. Back up a copy of /etc/cb/cb-supervisord.conf
   

   cp /etc/cb/cb-supervisord.conf /etc/cb/cb-supervisord.conf.old

2. Change the chown= entry in cb-supervisord.conf to match the user name specified under CbUser in /etc/cb/cb.conf
   

   vi /etc/cb/cb-supervisord.conf
   chown= root:(user name of CbGroup from cb.conf)

3. Repeat steps 1-2 on every minion if this is a clusters environment.
4. Start cb-enterprise services
   1. For Standalone:
      

      service cb-enterprise start

   2. For Cluster:
      

      /usr/share/cb/cbcluster start

5. Remove the cb-supervisord.conf.old file after verifying services are up
   

   rm -f /etc/cb/cb-supervisord.conf.old

Important Note(s)

Services will not start due to cb-supervisord.conf configuration if customer has user other than cb configured in cb.conf