Dear Sailors,
We have started to get “Disk volume /usr at 14% free” warning.
The thing is we have 120GB of disk and its 94GB is free. The /usr folder holds 224MB in total.
Do you have any suggestions?
I’m assuming you’re referring to the Virtual Appliance here and if so, I’d check the “logs” directory to see if you’ve generated some verbose logs here somehow that are taking up a lot of space.
Hi Ed,
Thanks for your response.
Yes I was referring to VA.
As you suggested, I checked the logs directory and also remove some big old log files however it hasn’t affected the size of /usr folder.
There is a new knowledge base article about the problem.
I’m also seeing this error but I don’t have any pending updates and the documentation doesn’t specify how to " clear your /usr mount" and I don’t want to break anything.
Where you able to fix the disk space issue?
Support Articles - /usr partition is almost full error on Virtual Appliance
You can refer this document and can resolve the issue
If you are not seeing any updates, then try running STUNT script it will resolve disk space warning issue.
Support Articles - /usr partition is almost full error on Virtual Appliance
Hey all,
We had the exact same issue, disk space warning at around ~14% started spamming us with alerts.
We were told that it is a non-issue as the /usr folder doesn’t increase in size. However, begs the question: why did it alert in the first place.
Root cause was our VM OS was stuck in an old state & IDN were unable to update remotely. We had to do this manually and then clear the config files. This removed the error.
1. Check your VM OS version, to do this, on your VM run this command:
cat /etc/os-release
This will have your release version somewhere like: 4100.1.1.(Bringontheweekend)
2. Ask ISC if your VM OS is latest version
I don’t know where you can check this without ISC support
3. If yours is out of date, get their guide on how to update the OS
If they can do it remotely, great. But might not be possible and should give you some commands to update this, but it’ll be something like:
sudo /opt/sailpoint/share/bin/flatcar-update -Q --to-version “4100.1.1.(Arsenalsignastriker)”
4. Clear out old config files with:
sudo rm /etc/systemd/system/update-engine.service.d/override.conf
Restart cluster
Error should be gone 