MySQL 5.7.37-40-57 crashed, mysqld got signal 11

2024-05-24T20:31:25.517560Z 20147 [Note] Got an error reading communication packets

20:31:29 UTC - mysqld got signal 11 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

Attempting to collect some information that could help diagnose the problem.

As this is a crash and something is definitely wrong, the information

collection process might fail.

Please help us make Percona XtraDB Cluster better by reporting any

bugs at https://jira.percona.com/projects/PXC/issues

key_buffer_size=8388608

read_buffer_size=131072

max_used_connections=4803

max_threads=7201

thread_count=324

connection_count=322

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2879375 K bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Build ID: 3ab991126ba08dd57d862ef49514368c805019b9

Server Version: 5.7.37-40-57-log Percona XtraDB Cluster (GPL), Release rel40, Revision ce3b993, WSREP version 31.57, wsrep_31.57

Thread pointer: 0x7fcbcc000b20

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 7fe558102670 thread_stack 0x40000

/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf7c0eb]

/usr/sbin/mysqld(handle_fatal_signal+0x505)[0xd8d7a5]

/lib64/libpthread.so.0(+0x118e0)[0x7fe5665f38e0]

/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcm+0x1081)[0xeea111]

/usr/sbin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x6d)[0xee7b9d]

/usr/sbin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x4d4)[0xf326b4]

/usr/sbin/mysqld(handle_slave_sql+0x1ae5)[0xf40715]

/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xf94b64]

/lib64/libpthread.so.0(+0x744b)[0x7fe5665e944b]

/lib64/libc.so.6(clone+0x3f)[0x7fe56472240f]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (7fca1000ea68): is an invalid pointer

Connection ID (thread ID): 2

Status: NOT_KILLED

You may download the Percona XtraDB Cluster operations manual by visiting

http://www.percona.com/software/percona-xtradb-cluster/. You may find information

in the manual which will help you identify the cause of the crash.

2024-05-24T20:31:38.219705Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2024-05-24T20:31:38.220811Z 0 [Warning] WSREP: Node is not a cluster node. Disabling pxc_strict_mode

2024-05-24T20:31:38.220823Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.37-40-57-log) starting as process 2930 ...

2024-05-24T20:31:38.224186Z 0 [Note] InnoDB: PUNCH HOLE support available

2024-05-24T20:31:38.224198Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2024-05-24T20:31:38.224200Z 0 [Note] InnoDB: Uses event mutexes

2024-05-24T20:31:38.224202Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2024-05-24T20:31:38.224203Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7

2024-05-24T20:31:38.224205Z 0 [Note] InnoDB: Using Linux native AIO

2024-05-24T20:31:38.226146Z 0 [Note] InnoDB: Number of pools: 1

2024-05-24T20:31:38.226228Z 0 [Note] InnoDB: Using CPU crc32 instructions

2024-05-24T20:31:38.228554Z 0 [Note] InnoDB: Initializing buffer pool, total size = 96G, instances = 8, chunk size = 128M

2024-05-24T20:31:40.212848Z 0 [Note] InnoDB: Completed initialization of buffer pool

2024-05-24T20:31:40.943090Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2024-05-24T20:31:40.958869Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite

2024-05-24T20:31:40.970267Z 0 [Note] InnoDB: Highest supported file format is Barracuda.

2024-05-24T20:31:41.571082Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 46371714822876

2024-05-24T20:31:41.592257Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46371720065536

2024-05-24T20:31:41.608644Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 46371725308416