Bug #108282 mysql server have restarted in a while time
Submitted: 25 Aug 2022 14:04 Modified: 26 Aug 2022 11:37
Reporter: czxin czxin Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0.29 OS:CentOS
Assigned to: CPU Architecture:Any

[25 Aug 2022 14:04] czxin czxin
After I upgraded my MySQL version from 8.0.28 to 8.0.29, my mysql-server often restarted in a white time,and the error log is :

2022-08-25T15:35:06.269918+08:00 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2022-08-25T15:35:06.269970+08:00 0 [Warning] [MY-011068] [Server] The syntax 'slave_skip_errors' is deprecated and will be removed in a future release. Please use replica_skip_errors instead.
2022-08-25T15:35:06.270185+08:00 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2022-08-25T15:35:06.270290+08:00 0 [System] [MY-010116] [Server] /u01/app/mysql-8.0.29/bin/mysqld (mysqld 8.0.29) starting as process 10686
2022-08-25T15:35:06.307016+08:00 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-08-25T15:35:10.748115+08:00 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-08-25T15:35:26.783633+08:00 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: btr0cur.cc:3654:rec thread 140706231158528
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.
07:35:26 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7ff8ac014670
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 = 7ff8b8ecfcc8 thread_stack 0x100000
/u01/app/mysql-8.0.29/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x1f80d4e]
/u01/app/mysql-8.0.29/bin/mysqld(print_fatal_signal(int)+0x2eb) [0x103587b]
/u01/app/mysql-8.0.29/bin/mysqld(my_server_abort()+0x5e) [0x103597e]
/u01/app/mysql-8.0.29/bin/mysqld(my_abort()+0xa) [0x1f7b4fa]
/u01/app/mysql-8.0.29/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x30c) [0x223b96c]
/u01/app/mysql-8.0.29/bin/mysqld() [0x227c25e]
/u01/app/mysql-8.0.29/bin/mysqld() [0x24154ab]
/u01/app/mysql-8.0.29/bin/mysqld() [0x241586a]
/u01/app/mysql-8.0.29/bin/mysqld(row_undo_mod(undo_node_t*, que_thr_t*)+0xcef) [0x24191ef]
/u01/app/mysql-8.0.29/bin/mysqld(row_undo_step(que_thr_t*)+0x52) [0x21b66e2]
/u01/app/mysql-8.0.29/bin/mysqld(que_run_threads(que_thr_t*)+0xc98) [0x215baa8]
/u01/app/mysql-8.0.29/bin/mysqld(trx_rollback_or_clean_recovered(bool)+0x1343) [0x2212513]
/u01/app/mysql-8.0.29/bin/mysqld(trx_recovery_rollback_thread()+0x1b) [0x221357b]
/u01/app/mysql-8.0.29/bin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, void (*)()> > >::_M_run()+0xac) [0x20ffdcc]
/u01/app/mysql-8.0.29/bin/mysqld() [0x277a69f]
/lib64/libpthread.so.0(+0x7e65) [0x7ffb45480e65]
/lib64/libc.so.6(clone+0x6d) [0x7ffb4378a88d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
What can i do to solve the problem
[26 Aug 2022 11:37] MySQL Verification Team
Hi Mr. czxin,

Thank you for your bug report.

There were a significant number of internal bugs that have caused great problems when upgraded to 8.0.29. All those bugs have been fixed and published in 8.0.30.

Hence, 8.0.29 is no longer a release that we support, when it comes to upgrades. Just use 8.0.30.