CB Response: Services do not start with LDAP "cb" user or group in place
search cancel

CB Response: Services do not start with LDAP "cb" user or group in place


Article ID: 287440


Updated On:


Carbon Black EDR (formerly Cb Response)


  • SystemD Service Status Output
systemctl status cb-enterprise.service

● cb-enterprise.service - SYSV: Carbon Black is a surveillance camera for your computer -- always recording so you know precisely what happened and where. This component provides an internal interface to the primary datastore.
Loaded: loaded (/etc/rc.d/init.d/cb-enterprise; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2019-06-19 13:53:14 CDT; 4min 24s ago
Docs: man:systemd-sysv-generator(8)
Process: 8726 ExecStart=/etc/rc.d/init.d/cb-enterprise start (code=exited, status=1/FAILURE)

Jun 19 13:53:14 :redacted: systemd[1]: Starting SYSV: Carbon Black is a survei.....
Jun 19 13:53:14 :redacted: cb-enterprise[8726]: Carbon Black Enterprise Server ....
Jun 19 13:53:14 :redacted: cb-enterprise[8726]: Run /usr/share/cb/cbinit to ini....
Jun 19 13:53:14 :redacted: systemd[1]: cb-enterprise.service: control process ...=1
Jun 19 13:53:14 :redacted: systemd[1]: Failed to start SYSV: Carbon Black is a.....
Jun 19 13:53:14 :redacted: systemd[1]: Unit cb-enterprise.service entered fail...e.
Jun 19 13:53:14 :redacted: systemd[1]: cb-enterprise.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
  • Will also display permission issues due to not having a proper local account available. Various places in the log files and on service startup will show permission being denied to access files only the local cb user or group would have access to.
    • The output below is from /var/log/cb/datagrid/startup.out.
      • "/etc.cb/cb.conf (permission denied)"



  • CB Response Server: All Versions
  • CentOS / RHEL: 7.x


  • CB Response relies on the local cb user and groups for daily operation. 
  • Pulling down these users or groups from LDAP can inhibit the local user and group.


  • Ensure local cb user and group accounts exist
  • Ensure LDAP has not imported a cb user or cb group