I run Manager server edition (25.8.3.2541) on Ubuntu 22.04, to serve around 10 companies. Recently, it hit an error message “Database or disk is full.”
I came across to this post from 2022. The post discussed failure on back up data because database or disk is full. I wasn’t going to back up Manager data. Manager simply can’t open any accounts of the companies, and it says database or disk is full.
When I calculated total data of each company in Manager, it takes around 426 MB (image attached). My storage in VPS is around 160 GB (image attached) and I didn’t install any other application in the VPS. This is where I get wondered, which part of Manager may consume large space?
The first storage I use was 60 GB. When the first time I got this issue, I just resized the storage to 80 and 130 GB. Only few days ago, I resized the storage to 160 GB. It took only 2-3 days later, the database or disk is full again. I think resizing the storage is not an effective solution for this issue. Can anyone help me to find out effective ways to solve the issue of database or disk is full, please?
I doubt this is an issue caused by Manager. Run some Linux commands to discover which directory takes bulk of space. Maybe that will give hint what is filling up your server.
I’m not a trained programmer. In case other users experience this issue, this is what I did based on Lubos’ suggestion (and consult Gemini) to solve the issue:
I logged in to my VPS account through Terminal and run following commands:
sudo df -h (This is to check the disk usage. I found Filesystem /dev/vda1 consumes nearly 100% space. See image below)
sudo du -ahx --max-depth=1 / --exclude=/proc --exclude=/sys | sort -h -r | head -n 10 (To find 10 directories that consume large space. Then, I got the list as image attached below. This reveals directory /var is the largest consumer).
sudo du -ahx --max-depth=1 /var | sort -h -r | head -n 10 (To find 10 subdirectories in /var that consume large space and found /var/log as the culprit).
sudo find /var/log -type f -size +1G (To find which logs consume more than 1 GB of space).
sudo truncate -s 0 /var/log/log_name (In my case, there are 2 log_name: syslog and syslog.1. I truncated both of them one by one. The results are depicted below. The space freed up drastically below 10 GB).
You’re absolutely right. I haven’t got any idea why the log files consumed huge space. Definitely I’ll take a look the link you sent me. Thanks so much for sharing the info.
