Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: 2024-10-21T22:22:20.010101Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.39-0ubuntu0.20.04.1) starting as process 14496
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: 2024-10-21T22:22:20.022266Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: 2024-10-21T22:22:20.381325Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: fut0lst.ic:82:addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA thread 139651898754816
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: InnoDB: We intentionally generate a memory trap.
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: InnoDB: If you get repeated assertion failures or crashes, even
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: InnoDB: immediately after the mysqld startup, there may be
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: InnoDB: corruption in the InnoDB tablespace. Please refer to
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: InnoDB: about forcing recovery.
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: 2024-10-21T22:22:20Z UTC - mysqld got signal 6 ;
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: BuildID[sha1]=26eb959d4d27330a3b28319eb9ea144b2a96f707
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: Thread pointer: 0x0
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: Attempting backtrace. You can use the following information to find out
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: where mysqld died. If you see no messages after this, something went
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: terribly wrong...
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: stack_bottom = 0 thread_stack 0x100000
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x56136621c771]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(print_fatal_signal(int)+0x39b) [0x56136508ed6b]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(my_server_abort()+0x76) [0x56136508eeb6]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(my_abort()+0xe) [0x56136621670e]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x349) [0x5613664ba2e9]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(trx_undo_lists_init(trx_rseg_t*)+0x918) [0x5613664b92d8]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(trx_rseg_init_thread(void*, unsigned long)+0x4b6) [0x56136649b1d6]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, void (*)(void*, unsigned long), void*, unsigned long> > >::_M_run()+0xcc) [0x56>
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xd6df4) [0x7f03699cddf4]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7f0369ae9609]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f03696ba353]
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
- Oct 21 22:22:20 hhmgritinv001 mysqld[14496]: information that should help you find out what is causing the crash.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement