Problem
| Info |
|---|
The appliance is down, The reason is the disk is full |
...
on the appliance. |
Reproduction/Solution
From the appliance, run the following commands.
...
sudo rm -r /opt/iqas/server/tmp/messages/
...
/opt/tools/monitor-disk-space.sh
...
df -h
...
docker tag f6857c1a3f7c harbor2.iqcloud.iquate.org/fishbowl/server-appliance:4.6.1694
...
sed -i "s|server-appliance:4.6.1617|server-appliance:4.6.1694|g" /opt/docker/appliance-stack.yml
...
Run the df command to to initially check space on appliance disk looking for usage at or close to 100%
| Code Block |
|---|
# This check the file system usage (-h just means use 1024 as the divisor for space i.e. 1K = 2024 bytes, 1Mb = 1024K etc.).
df -h |
Usage of 100% is blocking appliance stack starting
| Code Block |
|---|
# Check if the stack can start sudo /opt/docker/start-appliance-stack.sh |
...
sudo /opt/docker/start-appliance-stack.sh
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
Related issues | ||
| Jira Legacy | ||
| serverId | f2bd98b1-f69b-3014-a3d7-4fb8ee379d3a | key | CS-5648
...
The appliance stack cannot start.
To establish the largest directories to identify the are where all disk is consumed, run the following:
| Code Block |
|---|
# This check the /opt directory.
sudo du -a /opt/ 2>/dev/null | sort -n -r | head -n 20 |
...
This main cause seems to be at a root level so identify the main targets of use
| Code Block |
|---|
# Check disk usage command (du) at the root level
du -a / | sort -n -r | head -n 5 |
...
| Info |
|---|
remember to check other locations as well |
Clearing the Syslog will resolve the issue.
| Code Block |
|---|
# Force removal of all teh syslog files and any subfolders. Note: use rm command with care.
sudo rm -rf /var/log/syslog*
# reboot appliance
sudo shutdown -r now |