Version
Cb Response 4.x, 5.x, 6.x
Issue
Services won't start due to a file outside of /var/cb/data taking up excessive disk space
Symptoms
df -h shows 100% of disk space used
Solution
- Remove common large files from Cb Response server
- Check for old hprof files (hprof files are stack traces from java when SOLR crashes):
find /var/log/cb -type f -iname "*.hprof.*" |
- Remove any that are found:
rm -f {full path}/*hprof.old |
- Check for old cbdiags:
find / -type f -iname "cbdiag*" |
- Remove any that are found:
rm -f {full path}/*.cbdiag |
Warning: Do not delete the cbdiag utility /usr/share/cb/cbdiag
- If if /var is near full:
- If this resolved the space issue, verify yum caching option is not turned on:
vi /etc/yum.conf keepcache=0 |
- Verify there is free space and Cb Response isn't what's taking up space:
- Verify you've freed up some space:
df -h
- If disk usage is still near 100%, verify that SOLR and Modulestore aren't taking up all the disk space:
du -h /var/cb/data/ --max-depth=1 |
Note: If this directory is taking up the majority of space, follow this guide: No Free Disk Space Prevents Cb Response Services From Starting
- Otherwise check for other files outside of Cb Response. This will give you the 25 largest files:
Warning: Use caution when deleting any files
du -k --max-depth=1 | sort -nr | awk 'BEGIN {split("KB,MB,GB,TB", Units, ",");}{u = 1;while ($1 >= 1024) {$1 = $1 / 1024; u += 1} $1 = sprintf("%.1f %s", $1, Units); print $0;} ' |
Note: You can use explainshell.com to make sense of long commands like this, such as: