EDR: CB-Enterprise service not starting on cluster or stand alone server
search cancel

EDR: CB-Enterprise service not starting on cluster or stand alone server

book

Article ID: 288616

calendar_today

Updated On:

Products

Carbon Black EDR (formerly Cb Response)

Issue/Introduction

While starting the cb-enterprise service below error would occur. 

Node[0 ] [Errno 30] Read-only file system: '/var/cb/data/solr5/./solr.xml'
Node[0 ] Traceback (most recent call last):
Node[0 ] File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/utils/exceptions.py", line 70, in decorator
Node[0 ] File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/maintenance/cbstartup/main.py", line 165, in main
Node[0 ] File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/maintenance/cbstartup/main.py", line 111, in run
Node[0 ] File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/maintenance/cbstartup/actions/solr_core_setup.py", line 7, in execute
Node[0 ] File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/utils/solr_core_setup.py", line 18, in execute
Node[0 ] File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/utils/solr_core_setup.py", line 46, in _deploy_files_to_data_dir
Node[0 ] File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/utils/solr_core_setup.py", line 78, in _deploy_files
Node[0 ] File "/usr/lib64/python2.7/shutil.py", line 133, in copy
Node[0 ] copyfile(src, dst)
Node[0 ] File "/usr/lib64/python2.7/shutil.py", line 97, in copyfile
Node[0 ] with open(dst, 'wb') as fdst:

Environment

  • EDR: All supported versions

Cause

The following 3 reasons can be a cause for this issue resulting in Linux mounting the partition as "read-only"
  • Filesystem consistency issue
  • Power failure
  • Hardware issue

Resolution

This is an OS issue which need to be resolved by Linux admins. Once filesystem returns back to normal cb-enterprise services should start as normal.
  • dmesg file need to be reviewed by Linux admin for any disk errors. 
  • This issue has also been resolved by remounting the filesystem . Below command can be used for remounting 

mount -o remount,rw {mount point}

Where {mount point} is the directory where the FS is mounted.