Bug #109869 Connection failure
Submitted: 1 Feb 2023 6:27 Modified: 2 Feb 2023 11:55
Reporter: Zohaib Faruqui Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8 OS:Linux
Assigned to: MySQL Verification Team CPU Architecture:Any

[1 Feb 2023 6:27] Zohaib Faruqui
Description:
2023-01-31T05:28:55.529217Z 13306 [Warning] [MY-013360] [Server] Plugin sha256_password reported: ''sha256_password' is deprecated and 
will be removed in a future release. Please use caching_sha2_password instead'
2023-01-31T08:46:33.082596Z 18678 [ERROR] [MY-013995] [InnoDB] [FATAL] Field number: 38 too large, Total fields in Record: 38.
2023-01-31T08:46:33.082719Z 18678 [ERROR] [MY-013183] [InnoDB] Assertion failure: rem0wrec.cc:142:ib::fatal triggered thread 1402858560
48896
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: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-01-31T08:46:33Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=13fe4cc6857ad6fa2a5024c674977ce812a055cc
Thread pointer: 0x7f966400d410
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 = 7f96d89ddc50 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x5646b2dcffc1]
/usr/sbin/mysqld(print_fatal_signal(int)+0x39b) [0x5646b1c5478b]
/usr/sbin/mysqld(my_server_abort()+0x76) [0x5646b1c548d6]
/usr/sbin/mysqld(my_abort()+0xe) [0x5646b2dc9fae]
/usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x349) [0x5646b3060d39]
/usr/sbin/mysqld(ib::fatal::~fatal()+0xd5) [0x5646b3063545]
/usr/sbin/mysqld(+0x248490e) [0x5646b2f7090e]
/usr/sbin/mysqld(rec_offs_nth_extern(dict_index_t const*, unsigned long const*, unsigned long)+0x5c) [0x5646b2f70b2c]
/usr/sbin/mysqld(+0x24d3be4) [0x5646b2fbfbe4]
/usr/sbin/mysqld(row_sel_store_mysql_rec(unsigned char*, row_prebuilt_t*, unsigned char const*, dtuple_t const*, bool, dict_index_t con
st*, dict_index_t const*, unsigned long const*, bool, lob::undo_vers_t*, mem_block_info_t*&)+0x32e) [0x5646b2fc24ce]
/usr/sbin/mysqld(row_search_mvcc(unsigned char*, page_cur_mode_t, row_prebuilt_t*, unsigned long, unsigned long)+0x3504) [0x5646b2fc7c2
4]
/usr/sbin/mysqld(ha_innobase::index_read(unsigned char*, unsigned char const*, unsigned int, ha_rkey_function)+0x341) [0x5646b2e2c0c1]
/usr/sbin/mysqld(ha_innobase::index_first(unsigned char*)+0x36) [0x5646b2df7466]
/usr/sbin/mysqld(ha_innobase::rnd_next(unsigned char*)+0x47) [0x5646b2e2c727]
/usr/sbin/mysqld(handler::ha_rnd_next(unsigned char*)+0xfe) [0x5646b1d64f0e]
/usr/sbin/mysqld(TableScanIterator::Read()+0x83) [0x5646b1ebd083]
/usr/sbin/mysqld(filesort(THD*, Filesort*, RowIterator*, unsigned long, unsigned long long, Filesort_info*, Sort_result*, unsigned long
 long*)+0x945) [0x5646b1d50675]
/usr/sbin/mysqld(SortingIterator::DoSort()+0x72) [0x5646b1ebec02]
/usr/sbin/mysqld(SortingIterator::Init()+0x34) [0x5646b1ebec94]
/usr/sbin/mysqld(LimitOffsetIterator::Init()+0x1a) [0x5646b203232a]
/usr/sbin/mysqld(Query_expression::ExecuteIteratorQuery(THD*)+0x30d) [0x5646b1bbeb9d]
/usr/sbin/mysqld(Query_expression::execute(THD*)+0x30) [0x5646b1bbeea0]

How to repeat:
Error occurred all of a sudden, to be honest I don't know how to re produce.
It just simply restarting my service again and again and again
[2 Feb 2023 11:55] MySQL Verification Team
Hi,

You have a data corruption. Could happen due to RAM failure, storage system failure or something else. Follow https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html (or, better, contact our support team).