Ask the Community
Groups
Appliance's /usr/bp /var or '/' partitions are full - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>Use an SSH client such as <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fwww.chiark.greenend.org.uk%2F%7Esgtatham%2Fputty%2Flatest.html">PuTTY</a> to access the Unitrends system at the command line level. <i>Note: Ensure you have the OS password to access the Unitrends system’s command line. The OS </i><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013244978">password</a> <i>may differ from the password used to access the User Interface.</i> </p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> # df -h Filesystem Size Used Avail Use% Mounted on /dev/md3 15G 2.1G 12G 16% / tmpfs 16G 96K 16G 1% /dev/shm /dev/md0 243M 63M 169M 27% /boot /dev/md2 99G 2.8G 91G 3% /usr/bp /dev/md1 788G 28G 721G 4% /var/opt/unitrends/database /dev/sda 17T 1.8T 15T 11% /backups </pre> If the % value before /usr/bp indicates 100%, the /usr/bp/ partition is full and needs to be cleaned.<h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p><br>1) From the command line, change directories to /usr/bp/.<br> </p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> [root@Recovery-Series ~]# cd /usr/bp [root@Recovery-Series bp]#</pre> <br>2) Within /usr/bp/, run the command "du -sh *". This will list all files and directories and their sizes.<br> <pre class="code codeBlock" spellcheck="false" tabindex="0"> # du -sh *</pre> <br>3) Determine which logs are using the most amount of space. <pre class="code codeBlock" spellcheck="false" tabindex="0"> # cd logs.dir/ # ls -alh</pre> <br>4) Before deleting check to find out why the logs are so large in size by inspecting the log level. <br><i>Warning: Skipping this step will result in the re-occurrence of this issue.</i><br><br>5) Determine any process using an elevated log level. For more information, <i>including which logs should use an elevated log level by default that shold not be lowered</i>, see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013269118">Log Level Definitions</a>. <br> <pre class="code codeBlock" spellcheck="false" tabindex="0"> # /usr/bp/bin/check_logging Checking /usr/bp/bpinit/master.ini ... bpserver=5 # WARNING: DEBUG LOG LEVEL updatedb=5 # WARNING: DEBUG LOG LEVEL autosynth=5 # WARNING: DEBUG LOG LEVEL ===ERROR: Log parameters are out of bounds for /usr/bp Number of Log sources=55 LogRetentionInstances=100 LogsPerInstance=200 MaxLogKB=10240 Max Log size = 11264000000 KB /usr/bp size = 68849048 KB ===ERROR===</pre> <br>6) Now, lower the log level from the UI. <br><br>Navigate to Configure > <<<i>Unitrends appliance</i>>> >Edit > Advanced > General Configuration<br><br>Search the "Section" column for "debugging".<br><img alt="User-added image" height="351" src="https://us.v-cdn.net/6032361/uploads/migrated/7T621VAZ2Z4X/eid-ka03r0000019vdt-feoid-00n40000003czqx-refid-0em1w000000koap." width="500" class="embedImage-img importedEmbed-img"></img><br><br>7) Delete the offending log. <br><br>Warning: Once removed, this data will not be available for retrieval. If you are unsure of how to proceed, stop here and ask for assistance. <pre class="code codeBlock" spellcheck="false" tabindex="0"> # cd /usr/bp/logs.dir/ # ls -alh # rm <offending>.log</pre> <br>8) Check to confirm file is not held open and pending deletion <pre class="code codeBlock" spellcheck="false" tabindex="0"> # lsof | grep -i delete | /var/log/messages # rsyslogd 6347 root 6w REG 8,23 4714463232 131147 /var/log/messages (deleted) # in:imjour 6347 6353 root 6w REG 8,23 4714463232 131147 /var/log/messages (deleted) # rs:main 6347 6366 root 6w REG 8,23 4714463232 131147 /var/log/messages (deleted)</pre> <br>9) Kill running PID of process holding logs open or reboot appliance to allow linux to clear the file system and reclaim space. <br> <pre class="code codeBlock" spellcheck="false" tabindex="0"> # kill -9 6347 # lsof | grep -i delete | grep /var/log/messages #</pre> <br><br><br> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p>This issue is commonly caused by logging levels at an elevated level.<br><br> </p> <h2 data-id="notes"><strong>NOTES</strong></h2> <p>For more information, see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013269118">Log Level Definitions</a></p> </article> </main>