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

Cb Response: Solr Won't Start with CIFS File In Directory

Cb Response: Solr Won't Start with CIFS File In Directory

Environment

Cb Response 6.1.2

Symptoms

service cb-enterprise start

[Errno 2] No such file or directory: '/var/cb/data/solr5/_cbevents/cbevents_2017_08_24_2143/data/index/cifsFILENAME'

Traceback (most recent call last):

File "/opt/jenkins/build/workspace/build-cbent-signed-docker-6.1.2-respin/code/coreservices/src/cb/utils/exceptions.py", line 70, in decorator

File "/usr/lib/python2.6/site-packages/cb/maintenance/cbstartup/main.py", line 152, in main

File "/usr/lib/python2.6/site-packages/cb/maintenance/cbstartup/main.py", line 98, in run

File "/usr/lib64/python2.6/contextlib.py", line 34, in __exit__

self.gen.throw(type, value, traceback)

File "/usr/lib/python2.6/site-packages/cb/maintenance/cbstartup/main.py", line 105, in open_db_session

File "/usr/lib/python2.6/site-packages/cb/maintenance/cbstartup/main.py", line 98, in run

File "/opt/jenkins/build/workspace/build-cbent-signed-docker-6.1.2-respin/code/coreservices/src/cb/maintenance/cbstartup/actions/reset_file_permissions.py", line 8, in execute

File "/opt/jenkins/build/workspace/build-cbent-signed-docker-6.1.2-respin/code/coreservices/src/cb/utils/file_permissions.py", line 82, in reset_permissions

File "/opt/jenkins/build/workspace/build-cbent-signed-docker-6.1.2-respin/code/coreservices/src/cb/utils/cb_shell.py", line 176, in set_file_access_attrs

OSError: [Errno 2] No such file or directory: '/var/cb/data/solr5/_cbevents/cbevents_2017_08_24_2143/data/index/cifsFILENAME'

Cause

The CIFS (common internet file system) file type does not belong to Solr and is Microsoft's version of SMB with enhancements. It was likely generated in some way via Windows mounting of the drive, and it caused problems on startup because we normally check permissions on all files under the Solr on startup. Solr could not access this file, likely because it was added via CIFS mount and Linux does not understand that format.

Resolution

Remove the cifsFILENAME from the directory and services should start

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎11-13-2017
Views:
593
Contributors