Issues
- InnoDB: Assertion failure in thread in file rem0rec.cc line 592PXC-4391Resolved issue: PXC-4391
- One Galera node runing MySQL 5.7.31-34-57 Crash with InnoDB: Assertion failure in thread 140463094810368 in file rem0rec.cc line 592PXC-4331Resolved issue: PXC-4331
- The joining node kick out the donor node off the cluster during SST/ISTPXC-4005Resolved issue: PXC-4005puneet.kaushik
- Galera node stuck in MDL conflict and halted cluster writesPXC-3773Resolved issue: PXC-3773
- Modify processing to not allow threads/queries to be killed if the thread is in TOIPXC-3536Resolved issue: PXC-3536KennT
- Wrong summary for Percona-XtraDB-Cluster-shared-compat packagesPXC-3535Resolved issue: PXC-3535Alex Miroshnychenko
- length mismatch in the column name table_name on mysql/innodb_table_stats and mysql/innodb_index_statsPXC-3524Resolved issue: PXC-3524
- Explicitly set the dhparam option with socat to bypass the use of the old certsPXC-3508Resolved issue: PXC-3508KennT
- HA_ERR_ROW_IS_REFERENCED - FK constraint fail, node consistency compromised - after PXC updates onlyPXC-3487Resolved issue: PXC-3487Venkatesh Prasad
- Resolve package conflict when installing PXC 5.7 on RHEL/CentOS8PXC-3468Resolved issue: PXC-3468Evgeniy Patlan
- Uninstall audit_plugin does not work well on replicated nodes.PXC-3467Resolved issue: PXC-3467
11 of 11
We’re using 5.7.31 Galera node which crash randomly with the exact same error message
2024-03-04 04:19:12 0x7f1c46dab700 InnoDB: Assertion failure in thread 139759424550656 in file rem0rec.cc line 592
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB:
InnoDB: about forcing recovery.
04:19:12 UTC - mysqld got signal 6 ;
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
Thread pointer: 0x7f1cf57d5280
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 = 7f1c46daae50 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x40)[0x55970daedb10]
/usr/sbin/mysqld(handle_fatal_signal+0x589)[0x55970d2faa29]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f1e604b7420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f1e5ffa600b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f1e5ff85859]
/usr/sbin/mysqld(+0x67079a)[0x55970d2b779a]
/usr/sbin/mysqld(+0x65e289)[0x55970d2a5289]
/usr/sbin/mysqld(_Z25wsrep_rec_get_foreign_keyPhPmPKhP12dict_index_tS4_m+0x7b)[0x55970dc6ff1b]
/usr/sbin/mysqld(_Z24wsrep_append_foreign_keyP5trx_tP14dict_foreign_tPKhP12dict_index_tm14wsrep_key_type+0x1c9)[0x55970dba2729]
/usr/sbin/mysqld(_Z32row_ins_check_foreign_constraintmP14dict_foreign_tP12dict_table_tP8dtuple_tP9que_thr_t+0x1837)[0x55970dc8c5c7]
/usr/sbin/mysqld(+0x1099451)[0x55970dce0451]
/usr/sbin/mysqld(+0x109e140)[0x55970dce5140]
/usr/sbin/mysqld(_Z7row_updP10upd_node_tP9que_thr_t+0x208)[0x55970dce7508]
/usr/sbin/mysqld(_Z12row_upd_stepP9que_thr_t+0x67)[0x55970dce75d7]
/usr/sbin/mysqld(+0x105e17e)[0x55970dca517e]
/usr/sbin/mysqld(_Z20row_update_for_mysqlPKhP14row_prebuilt_t+0x43)[0x55970dca98a3]
/usr/sbin/mysqld(_ZN11ha_innobase10delete_rowEPKh+0x1a0)[0x55970db9f980]
/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x143)[0x55970d37a563]
/usr/sbin/mysqld(_ZN14Sql_cmd_delete12mysql_deleteEP3THDy+0x11be)[0x55970da134be]
/usr/sbin/mysqld(_ZN14Sql_cmd_delete7executeEP3THD+0xf1)[0x55970da13bf1]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x5c52)[0x55970d89a852]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_stateb+0x565)[0x55970d89d585]
/usr/sbin/mysqld(+0xc5666d)[0x55970d89d66d]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x1de2)[0x55970d89fcb2]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x2ea)[0x55970d8a102a]
/usr/sbin/mysqld(handle_connection+0x388)[0x55970d96d488]
/usr/sbin/mysqld(pfs_spawn_thread+0x168)[0x55970db0b3d8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f1e604ab609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f1e60082353]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f1cf560fa90): is an invalid pointer
Connection ID (thread ID): 5024550
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting
You may find information
in the manual which will help you identify the cause of the crash