No Free Disk Space Prevents Services From Starting
search cancel

No Free Disk Space Prevents Services From Starting

book

Article ID: 284751

calendar_today

Updated On:

Products

Carbon Black EDR (formerly Cb Response)

Issue/Introduction

  • df -h shows 100% of disk space used on one or more drives
  • CbDiags will not generate 

Environment

  • EDR (formerly CB Response) Server: All Supported Versions

Cause

Files within the server has caused the environment to run out of disk space.

Resolution

  • Free up space on the disk 
      1. Remove common large files from the server
      2. Check modulestore disk usage: 
du -h /var/cb/data/ --max-depth=1
  1. If the modulestore directory is consuming excessive disk, purge old modules
  2. Determine if cbevents or cbmodules is taking up space: 
  • For 5.x
du -h /var/cb/data/solr --max-depth=1
  • For 6.x
du -h /var/cb/data/solr5 --max-depth=1
  • For 7.x
du -h /var/cb/data/solr6 --max-depth=1
  1. If cbevents data is filling the disk, purge the older events.
  2. If cbmodules data is filling the disk: review options to safely remove data
  3. Determine if a certain process log file is taking up space:
du -h /var/log/cb/ --max-depth=1
  • Remove .tmp files older than 7 days
find <path_to_process_logs> -name *.tmp -mtime +7 -delete
  • Remove .gz log files older than 7 days:
find <path_to_process_logs> -name *.gz -mtime +7 -delete
  1. If the server is still out of space, determine which drive partition is out of space
df -h
  1. From the affected partition, start at the root folder and work through the largest folder paths to clear data using the du command with the --max-depth=1 flag to list disk usage of each folder
du -h / --max-depth=1