The backup process is failing, and temporary folders (tmp) are being created during the backup attempt

1

root@www:/backup# ll
total 33041500
drwxr-xr-x 10 root root 4096 Aug 3 16:50 ./
drwxr-xr-x 22 root root 4096 Aug 2 19:39 …/
-rw-r----- 1 admin admin 21147924480 Jun 24 05:13 admin.2024-06-24_05-12-27.tar
-rw-r–r-- 1 root root 874 Aug 3 05:11 admin.log
-rw-r----- 1 admin eiml 12686510080 Jun 24 05:18 eiml.2024-06-24_05-17-14.tar
-rw-r–r-- 1 root root 1554 Aug 3 16:53 eiml.log
drwx------ 8 root root 4096 Aug 3 16:23 tmp.25ykAHlmAx/
drwx------ 8 root root 4096 Aug 3 16:33 tmp.8g1IcY6nxL/
drwx------ 8 root root 4096 Aug 3 16:48 tmp.B7w9E6PvMk/

The only backup available is from June 24th, and there are no recent backups for either the admin or eiml users, which is a serious issue. Without recent backups, data recovery in case of any problems will be impossible. Additionally, the tmp.* directories are created by the operating system—why are these temporary files appearing?

Please assist with resolving this issue.

2

rm -fr tmp.*

And then run v-backup-user

3

we have run the command, but is shows the error.

root@www:/backup# v-backup-user eiml
/usr/local/hestia/bin/v-backup-user: line 180: Error: Connection to localhost failed * 2: syntax error in expression (error token is “: Connection to localhost failed * 2”)
/usr/local/hestia/bin/v-backup-user: line 183: [: : integer expression expected

and again created a tmp folder

root@www:~# cd /backup
root@www:/backup# ll
total 33041480
drwxr-xr-x 5 root root 4096 Aug 3 17:20 ./
drwxr-xr-x 22 root root 4096 Aug 2 19:39 …/
-rw-r----- 1 admin admin 21147924480 Jun 24 05:13 admin.2024-06-24_05-12-27.tar
-rw-r–r-- 1 root root 874 Aug 3 05:11 admin.log
-rw-r----- 1 admin eiml 12686510080 Jun 24 05:18 eiml.2024-06-24_05-17-14.tar
-rw-r–r-- 1 root root 1015 Aug 3 17:20 eiml.log
drwxr-xr-x 4 root root 4096 Aug 3 17:18 tmp.nlJN3MwVqZ/
drwx------ 7 root root 4096 Aug 3 17:20 tmp.QTsmqRZYSz/
drwx------ 5 root root 4096 Aug 3 17:20 tmp.tX6frQGXyy/
root@www:/backup#

4

It is unable to connect to mysql did you change the root password?

1 Like
5

Hello,

No changes were made.
Please let us know what to do next? Are you asking for MySQL logins?
Also deleting the tmp files and rerunning backup is causing backup misisng. So could you please suggest a permanent fix to avoid this from happening.
We want the backup to run as scheduled .
Please suggest.

6

Do you have any .mysql.* file?

ls -la /usr/local/hestia/conf/.mysql*

Show the output of these commands:

mysql -uroot -e 'show databases;'
mysql --defaults-file=/usr/local/hestia/conf/.mysql.localhost -uroot -e 'show databases;'

If you see any error, compare the password used in these files:

/root/.my.cnf
/usr/local/hestia/conf/.mysql.localhost
/usr/local/hestia/conf/mysql.conf