Problem with VESTACP backup file causes disk full

Recently, a site of the micro-demon MySQL can not connect the situation, the thought of a direct restart of MySQL OK, the results found when the restart of MySQL prompts "the partition With/var/lib/mysql is too full!", This problem is mainly due to the disk consumption is full, according to the DF-LH command to see the real local disk is already 100%, this time the VESTACP Web Management panel (https://ip:8083) can not log (502 error). So began the investigation of the trip.

Resolving problems with VESTACP backup files causing disk full

1. View reason: From/folder start, check the size of each folder individually

Du-h--max-depth=1
Find the culprit and find a series of TMP. Random characters files in the/home/backup folder, which are VESTACP local backup files that were automatically deleted after the backup, but were left behind because of some intermediate errors (see log files).

2. Delete tmp*

rm-rf/home/backup/tmp*
3. Restart VESTACP

Service Vesta Restart
4. Enter VESTACP, close local backup

Click "Configure" under "Sever" (is a gear-like icon)

Roll to Backup, select Local No