I have been using aapanel for several months and I had no problems at all, but recently I got an Aborted connection log on MariaDB Log details: 2021-04-05 9:18:50 783157 [Warning] Aborted connection 783157 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-05 9:46:11 864525 [Warning] Aborted connection 864525 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 2:00:09 3549282 [Warning] Aborted connection 3549282 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 2:00:09 3549266 [Warning] Aborted connection 3549266 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 10:17:20 4865870 [Warning] Aborted connection 4865870 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 10:19:40 4872445 [Warning] Aborted connection 4872445 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 10:22:40 4880302 [Warning] Aborted connection 4880302 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 10:23:20 4882415 [Warning] Aborted connection 4882415 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 10:27:10 4892570 [Warning] Aborted connection 4892570 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 10:30:20 4901213 [Warning] Aborted connection 4901213 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) 2021-04-06 12:41:40 5239106 [Warning] Aborted connection 5239106 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets) if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } Configuration (32GB RAM): [client] #password = your_password port = 3306 socket = /tmp/mysql.sock [mysqld] binlog_cache_size = 256K thread_stack = 512K join_buffer_size = 8192K query_cache_type = 1 max_heap_table_size = 2048M port = 3306 socket = /tmp/mysql.sock datadir = /www/server/data default_storage_engine = InnoDB performance_schema_max_table_instances = 400 table_definition_cache = 400 skip-external-locking key_buffer_size = 1024M max_allowed_packet = 100G table_open_cache = 2048 sort_buffer_size = 4096K net_buffer_length = 4K read_buffer_size = 4096K read_rnd_buffer_size = 2048K myisam_sort_buffer_size = 128M thread_cache_size = 512 query_cache_size = 2048M tmp_table_size = 2048M sql-mode=NO_ENGINE_SUBSTITUTION #skip-name-resolve max_connections = 800 max_connect_errors = 100 open_files_limit = 65535 log-bin=mysql-bin binlog_format=mixed server-id = 1 expire_logs_days = 10 slow_query_log=1 slow-query-log-file=/www/server/data/mysql-slow.log long_query_time=3 #log_queries_not_using_indexes=on innodb_data_home_dir = /www/server/data innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = /www/server/data innodb_buffer_pool_size = 18432M innodb_log_file_size = 1024M innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 innodb_max_dirty_pages_pct = 90 innodb_read_io_threads = 8 innodb_write_io_threads = 8 [mysqldump] quick max_allowed_packet = 5000M [mysql] no-auto-rehash [myisamchk] key_buffer_size = 1024M sort_buffer_size = 4096K read_buffer = 4096K write_buffer = 4096K [mysqlhotcopy] interactive-timeout if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } But the site is running well, I'm just afraid there will be problems in the future , please help me solve this problem. Thanks.

Eseven In fact, Aborted connection alarms are hard to avoid, there will be more or less a small amount of Aborted connection information in the error log, this situation can be ignored, but when you have frequent Aborted connection alarms in the error log, it is time to pay attention to it. It may have a greater impact on the business. Here are a few suggestions to avoid the error, hope you can help. It is recommended that after the business operation is finished, the application logic will close the connection correctly and replace the long connection with a short one. Check to ensure that the max_allowed_packet value is high enough and that the client does not receive a "packet too large" message. Make sure the client application does not abort the connection, for example, if PHP sets max_execution_time to 5 seconds, increasing connect_timeout will not work because PHP will kill the script. Other programming languages and environments have similar security options. Make sure the transaction commits (begin and commit) are committed correctly to ensure that the connection is left in a clean state once the application is finished. Check that skip-name-resolve is enabled and that hosts authenticate based on their IP addresses rather than their host names. Try increasing MySQL's net_read_timeout and net_write_timeout values to see if this reduces the number of errors. Reference： https://dev.mysql.com/doc/refman/5.7/en/communication-errors.html

How to solve the Aborted connection problem on MariaDB

Eseven

I have been using aapanel for several months and I had no problems at all, but recently I got an Aborted connection log on MariaDB

Log details:

2021-04-05  9:18:50 783157 [Warning] Aborted connection 783157 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-05  9:46:11 864525 [Warning] Aborted connection 864525 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06  2:00:09 3549282 [Warning] Aborted connection 3549282 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06  2:00:09 3549266 [Warning] Aborted connection 3549266 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06 10:17:20 4865870 [Warning] Aborted connection 4865870 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06 10:19:40 4872445 [Warning] Aborted connection 4872445 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06 10:22:40 4880302 [Warning] Aborted connection 4880302 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06 10:23:20 4882415 [Warning] Aborted connection 4882415 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06 10:27:10 4892570 [Warning] Aborted connection 4892570 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06 10:30:20 4901213 [Warning] Aborted connection 4901213 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)
2021-04-06 12:41:40 5239106 [Warning] Aborted connection 5239106 to db: 'mydatabase' user: 'mydatabase' host: 'localhost' (Got an error reading communication packets)

Configuration (32GB RAM):

[client]
#password	= your_password
port		= 3306
socket		= /tmp/mysql.sock

[mysqld]
binlog_cache_size = 256K
thread_stack = 512K
join_buffer_size = 8192K
query_cache_type = 1
max_heap_table_size = 2048M
port		= 3306
socket		= /tmp/mysql.sock
datadir = /www/server/data
default_storage_engine = InnoDB
performance_schema_max_table_instances = 400
table_definition_cache = 400
skip-external-locking
key_buffer_size = 1024M
max_allowed_packet = 100G
table_open_cache = 2048
sort_buffer_size = 4096K
net_buffer_length = 4K
read_buffer_size = 4096K
read_rnd_buffer_size = 2048K
myisam_sort_buffer_size = 128M
thread_cache_size = 512
query_cache_size = 2048M
tmp_table_size = 2048M
sql-mode=NO_ENGINE_SUBSTITUTION

#skip-name-resolve
max_connections = 800
max_connect_errors = 100
open_files_limit = 65535

log-bin=mysql-bin
binlog_format=mixed
server-id = 1
expire_logs_days = 10
slow_query_log=1
slow-query-log-file=/www/server/data/mysql-slow.log
long_query_time=3
#log_queries_not_using_indexes=on


innodb_data_home_dir = /www/server/data
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /www/server/data
innodb_buffer_pool_size = 18432M
innodb_log_file_size = 1024M
innodb_log_buffer_size = 256M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
innodb_max_dirty_pages_pct = 90
innodb_read_io_threads = 8
innodb_write_io_threads = 8

[mysqldump]
quick
max_allowed_packet = 5000M

[mysql]
no-auto-rehash

[myisamchk]
key_buffer_size = 1024M
sort_buffer_size = 4096K
read_buffer = 4096K
write_buffer = 4096K

[mysqlhotcopy]
interactive-timeout

But the site is running well, I'm just afraid there will be problems in the future , please help me solve this problem.
Thanks.

aapanel_power

Eseven In fact, Aborted connection alarms are hard to avoid, there will be more or less a small amount of Aborted connection information in the error log, this situation can be ignored, but when you have frequent Aborted connection alarms in the error log, it is time to pay attention to it. It may have a greater impact on the business. Here are a few suggestions to avoid the error, hope you can help.

It is recommended that after the business operation is finished, the application logic will close the connection correctly and replace the long connection with a short one.
Check to ensure that the max_allowed_packet value is high enough and that the client does not receive a "packet too large" message.
Make sure the client application does not abort the connection, for example, if PHP sets max_execution_time to 5 seconds, increasing connect_timeout will not work because PHP will kill the script. Other programming languages and environments have similar security options.
Make sure the transaction commits (begin and commit) are committed correctly to ensure that the connection is left in a clean state once the application is finished.
Check that skip-name-resolve is enabled and that hosts authenticate based on their IP addresses rather than their host names.
Try increasing MySQL's net_read_timeout and net_write_timeout values to see if this reduces the number of errors.
Reference：https://dev.mysql.com/doc/refman/5.7/en/communication-errors.html

Eseven

idflorin

Eseven I'm having this issue for months but It's just a warning
and everything works fine.
btw, if you use mariaDB just on your server your should uncomment
#skip-name-resolve to skip-name-resolve

aaPanel_Captain

Eseven try to modify the max_allowed_packet parameter to 1024M, and restart MySQL to take effect, and then continue to observe whether the problem will be prompted

Eseven

aapanel_power
Thanks for the help, after following your advice I finally understand the cause.

Katerok

Eseven
Hello, excuse me, please tell me how you finally solved the problem?