Just Published! Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

5.2, 5.3 PGSQL or Redis Won’t Consistently Start

5.2, 5.3 PGSQL or Redis Won’t Consistently Start

Version

Cb Response 5.2.x, 5.3.x

Issue

Services won’t start after upgrading to 5.2/5.3. Trying repeatedly allows services to start

Cause

If a third party authentication such as samba/winbind or LDAP is in use, PGSQL or Redis can time out while trying to start while waiting for this authentication service to return results. This issue is caused by the supervisord code requesting full group enumeration prior to starting services. cb-pgsql is affected because it is the first service started. Our startup script in /etc/init.d/cb-enterprise has a 30 second delay waiting for cb-pgsql to complete its startup sequence. The enumeration delay can take longer than our 30 second timeout.

Solution

Workaround

Use the attached cb-enterprise init.d script that should be placed in the /etc/init.d/ directory on all minion systems

Solution

Upgrade to 6.1 where we have code changes that prevent the AD group enumeration in the first place:

Cb Response 6.1 Documentation and Solution Repository

Labels (1)
Attachments
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎07-07-2017
Views:
567
Contributors