ZipperZapper
Verified User
- Joined
- Nov 30, 2015
- Messages
- 142
This weekend I upgraded my server from Ubuntu 14.04 (EOL) tot Ubuntu 16.04.
All seems to be working quite fine, apart from the scheduled Admin Backup.
It throws up this error for all users/databases:
And in the end:
A search on the forum showed me this topic with the same problem.
I checked the location:
This confirms the "/tmp/mysql.sock" the backup process is trying to use isn't the right one.
Then I checked /etc/my.cnf and it only contains the following three lines:
I added "socket = /home/mysql/mysql.sock" to it and rebooted the server, but the backup process still throws up the same error.
Can anyone point me in the right direction here?
All seems to be working quite fine, apart from the scheduled Admin Backup.
It throws up this error for all users/databases:
Code:
Error while backing up database XXXX
Error while backing up database XXXX: The sql file is 0 bytes in size: /home/tmp/XX.3892/XX/backup/XXXX.sql
mysqldump error output: mysqldump: Got error: 2002: "Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)" when trying to connect
And in the end:
Code:
Error Compressing the backup file /home/tmp/XX.3892/XX/backup/home.tar.gz : /bin/tar: backup: Function open() failed: permission denied
/bin/tar: Stopped due to earlier errors
A search on the forum showed me this topic with the same problem.
I checked the location:
Code:
- locate mysql.sock
>> /home/mysql/mysql.sock
This confirms the "/tmp/mysql.sock" the backup process is trying to use isn't the right one.
Then I checked /etc/my.cnf and it only contains the following three lines:
Code:
[mysqld]
local-infile=0
innodb_file_per_table
I added "socket = /home/mysql/mysql.sock" to it and rebooted the server, but the backup process still throws up the same error.
Can anyone point me in the right direction here?