Backup messed up server

[nickcraig]

I noticed my Vesta panel had not done a backup in over 2 months last night. I logged in and did a manual backup inside of Vesta. I woke up this morning the CPU was at 100% all night and now my disk is full yet no new files in the backup folder.

SQL won't start due to no disk space, any help would be great.

[nickcraig]

gzip is creating tmp. files inside of the /backup folder over and over again. I had 20+ tmp. files. How can I make these stop piling up.

[skurudo]

SQL won't start due to no disk space, any help would be great.

Your disk space ran out?
May be you need more space?

[skurudo]

Please show us /var/log/vesta/backup.log

[nickcraig]

g2017-03-05 16:07:21 database (mysql)
2017-03-05 16:07:21 database (mysql)
sh: 0: getcwd() failed: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent di$
job-working-directory: error retrieving current directory: getcwd: cannot acces$
sh: 0: getcwd() failed: No such file or directory
exim: can't get the current working directory: No such file or directory
Error: dump database failed


Here is an example of an error that just happened

[skurudo]

Try this and reconnect to terminal to check:

Code: Select all

export VESTA=/usr/local/vesta/

[sonix]

Hello,
I have the same problem..
there are 3 domains.. only with one is the problem..
In htop: 100% CPU - gzip -9 - (screen)

Code: Select all

-- WEB --
2018-01-05 15:05:02 domian.pl
2018-01-05 15:07:33 *** 1 domain ***

-- DNS --
2018-01-05 15:07:33 domian.pl
2018-01-05 15:07:33 *** 1 domain ***

-- MAIL --
2018-01-05 15:07:33 domian.pl
2018-01-05 15:07:33 *** 1 domain ***

-- DB --
2018-01-05 15:07:33 baza (mysql)
sh: 0: getcwd() failed: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent di$
sh: 0: getcwd() failed: No such file or directory
exim: can't get the current working directory: No such file or directory
Error: dump baza failed
-- SYSTEM --
2018-01-05 15:10:01 domian.conf
2018-01-05 15:10:01 stats.log
2018-01-05 15:10:01 history.log
2018-01-05 15:10:01 pam

Please help..