Thanks for replying. I do have innodb_buffer_pool_size already, and the size value depends on the size of databases and the memory. So it's not only 100M
The backup was fine, the problem just happened from last 2 days, and the server has no update except DirectAdmin updated yesterday (so the problem was happening before DA update).
The server is running CloudLinux 8 with MariaDB 10.6.11.
Anyway, even I can still export the table with phpMyAdmin, I used phpMyAdmin for analyzing data rows, and found one corrupted. Delete that one, and mysqldump is working fine now.
Hello,
I am encountering a similar issue on a similar configuration: CloudLinux 8 and MariaDB 10.6.
Every 30 seconds, my MySQL logs record an error of this nature:
Code:
Nov 12 10:41:26 calamansi.easyhoster.com mariadbd[72547]: 2023-11-12 10:41:26 55 [Warning] Aborted connection 55 to db: 'mysql' user: 'da_admin' host: 'localhost' (Got an error reading communication packets)
Nov 12 10:41:56 calamansi.easyhoster.com mariadbd[72547]: 2023-11-12 10:41:56 59 [Warning] Aborted connection 59 to db: 'mysql' user: 'da_admin' host: 'localhost' (Got an error reading communication packets)
Nov 12 10:42:26 calamansi.easyhoster.com mariadbd[72547]: 2023-11-12 10:42:26 64 [Warning] Aborted connection 64 to db: 'mysql' user: 'da_admin' host: 'localhost' (Got an error reading communication packets)
Nov 12 10:42:56 calamansi.easyhoster.com mariadbd[72547]: 2023-11-12 10:42:56 69 [Warning] Aborted connection 69 to db: 'mysql' user: 'da_admin' host: 'localhost' (Got an error reading communication packets)
Nov 12 10:43:26 calamansi.easyhoster.com mariadbd[72547]: 2023-11-12 10:43:26 73 [Warning] Aborted connection 73 to db: 'mysql' user: 'da_admin' host: 'localhost' (Got an error reading communication packets)
Nov 12 10:43:56 calamansi.easyhoster.com mariadbd[72547]: 2023-11-12 10:43:56 75 [Warning] Aborted connection 75 to db: 'mysql' user: 'da_admin' host: 'localhost' (Got an error reading communication packets)
Because
@gate2vn have the same issue with the same config (
CloudLinux 8 /
MariaDB 10.6), I suspect there is a compatibility issue between DirectAdmin and CloudLinux (perhaps the SQL Governor?) with the MySQL database "mysql" which need to be regularly accessed by da_admin.
I've attempted to
tweak my /etc/my.cnf in response to this issue, following guidance from here and from
this good article.
I'm not sure what task DirectAdmin is trying to accomplish every 30 seconds with this "mysql" database, but I suspect that this problem is causing my "
System Backup" feature (DA
Sysbk) to fail.
Whenever the System Backup Cron runs, it returns an error
(Stage 3 MySQL backup: MySQL could not be started, aborting...) which causes Sysbk to fail and prevents my backups from being transported via FTP when "MySQL Databases backups" are enabled.
Unlike
@gate2vn, it doesn't appear that I have any corrupted tables. The
mysql.user table has the type of "view", but it seems to be normal, and I am able to properly mysqldump and/or phpMyAdmin export the "mysql" database.
I'm concerned that this error
(Aborted connection … to db: 'mysql' user: 'da_admin' host: 'localhost' (Got an error reading communication packets)) might disrupt other essential features of DirectAdmin?
I plan to contact CloudLinux about this issue to see if it could be related to their components, and to determine if there are any missing things related to this DirectAdmin native mysql table that needs to be accessed by the user "da_admin".
I will update you with their response, but in the meantime, if any DirectAdmin enthusiasts here have suggestions for a solution or workaround to prevent these
Connections from being
Aborted and to fix my DA Sysbk with CloudLinux 8 / MariaDB 10.6, I would greatly appreciate reading them. Thank you!