转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

fengzheng081212 · 2022-11-16 07:27:55

Watermelon.Rei · 2022-11-16 09:22:54

用
pacman -Qkk | grep warning
看下哪些包文件有问题，然后试着重新安装一下
看起来有nvidia显卡驱动和fcitx

依云 · 2022-11-16 11:08:28

这些 .old 是怎么回事啊？

btrfs 在线转换可能有问题的，参见 https://xuanwo.io/2018/11/15/record-for … onversion/

fengzheng081212 · 2022-11-16 12:13:19

解决不了，不影响使用，先不管了

依云 · 2022-11-16 12:29:44

那些 .old 的空文件直接删掉就好了。

卑以自牧 · 2022-11-16 13:38:12

我看到也顺便从etx4转换了btrfs，挺快的，可能是我只有700多个包的原因，唯一的问题是mysql起不来

已经执行过了，chattr +C /var/lib/mysql

~ systemctl status mysqld.service
× mysqld.service - MySQL Server
     Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Wed 2022-11-16 13:20:16 CST; 10min ago
       Docs: man:mysqld(8)
             http://dev.mysql.com/doc/refman/en/using-systemd.html
    Process: 2720 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
    Process: 2741 ExecStart=/usr/bin/mysqld $MYSQLD_OPTS (code=exited, status=2)
   Main PID: 2741 (code=exited, status=2)
     Status: "Server startup in progress"
        CPU: 269ms
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
11月 16 13:20:16 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:20:16 archlinux systemd[1]: Failed to start MySQL Server.

~ journalctl -xeu mysqld.service
░░ 结果为“failed”。
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ Automatic restarting of the unit mysqld.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
11月 16 13:20:16 archlinux systemd[1]: Stopped MySQL Server.
░░ Subject: mysqld.service 单元已结束停止操作
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ mysqld.service 单元已结束停止操作。
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit mysqld.service has entered the 'failed' state with result 'exit-code'.
11月 16 13:20:16 archlinux systemd[1]: Failed to start MySQL Server.
░░ Subject: mysqld.service 单元已失败
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ mysqld.service 单元已失败。
░░
░░ 结果为“failed”。

依云 · 2022-11-16 13:51:42

贴日志的时候不要加 -x。最好也不要加 -e，以免漏掉有用的日志。

这里并没有 mysql 的日志。找找看它是不是把错误日志记录在别处了。（又或者是被 -e 过滤掉了？）

另外目录里已有的文件不受 +C 的影响。

卑以自牧 · 2022-11-16 14:31:12

-x -e 是因为

~ sudo systemctl start mysqld.service
[sudo] riven 的密码：
Job for mysqld.service failed because the control process exited with error code.
See "systemctl status mysqld.service" and "journalctl -xeu mysqld.service" for details.

下面是去掉了这俩的

11月 16 11:55:25 archlinux mysqld[568]: 2022-11-16T03:55:25.300252Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.31).
11月 16 11:55:25 archlinux systemd[1]: Stopping MySQL Server...
11月 16 11:55:26 archlinux mysqld[568]: 2022-11-16T03:55:26.452933Z 0 [System] [MY-010910] [Server] /usr/bin/mysqld: Shutdown complete (mysqld 8.0.31)  Source distribution.
11月 16 11:55:26 archlinux systemd[1]: mysqld.service: Deactivated successfully.
11月 16 11:55:26 archlinux systemd[1]: Stopped MySQL Server.
11月 16 11:55:26 archlinux systemd[1]: mysqld.service: Consumed 9min 43.841s CPU time.
-- Boot 9c600d02a8e14d1ba1f762e7ee0b5de6 --
11月 16 12:46:01 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:46:01 archlinux mysqld[597]: 2022-11-16T04:46:01.806794Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:46:01 archlinux mysqld[597]: 2022-11-16T04:46:01.806839Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 597
11月 16 12:46:01 archlinux mysqld[597]: 2022-11-16T04:46:01.813427Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:46:01 archlinux mysqld[597]: 2022-11-16T04:46:01.865645Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:46:01 archlinux mysqld[597]: 2022-11-16T04:46:01.865661Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140333081982656
11月 16 12:46:01 archlinux mysqld[597]: InnoDB: We intentionally generate a memory trap.
11月 16 12:46:01 archlinux mysqld[597]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:46:01 archlinux mysqld[597]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:46:01 archlinux mysqld[597]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:46:01 archlinux mysqld[597]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:46:01 archlinux mysqld[597]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:46:01 archlinux mysqld[597]: InnoDB: about forcing recovery.
11月 16 12:46:01 archlinux mysqld[597]: 2022-11-16T04:46:01Z UTC - mysqld got signal 6 ;
11月 16 12:46:01 archlinux mysqld[597]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:46:01 archlinux mysqld[597]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:46:01 archlinux mysqld[597]: Thread pointer: 0x55addc9d8b30
11月 16 12:46:01 archlinux mysqld[597]: Attempting backtrace. You can use the following information to find out
11月 16 12:46:01 archlinux mysqld[597]: where mysqld died. If you see no messages after this, something went
11月 16 12:46:01 archlinux mysqld[597]: terribly wrong...
11月 16 12:46:01 archlinux mysqld[597]: stack_bottom = 7fa1d7806c50 thread_stack 0x100000
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55add7bcc312]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55add722267f]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55add722282f]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(my_abort()+0xe) [0x55add7bc80ae]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55add7d6e3db]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(+0x1647f28) [0x55add7ca2f28]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55add7cb9999]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55add7d632ca]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(+0x15b21e2) [0x55add7c0d1e2]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55add7a5296b]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55add7bbd6bc]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(+0xc5beda) [0x55add72b6eda]
11月 16 12:46:01 archlinux mysqld[597]: /usr/bin/mysqld(+0x1943283) [0x55add7f9e283]
11月 16 12:46:01 archlinux mysqld[597]: /usr/lib/libc.so.6(+0x868fd) [0x7fa1e5e9f8fd]
11月 16 12:46:01 archlinux mysqld[597]: /usr/lib/libc.so.6(+0x108a60) [0x7fa1e5f21a60]
11月 16 12:46:01 archlinux mysqld[597]: Trying to get some variables.
11月 16 12:46:01 archlinux mysqld[597]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:46:01 archlinux mysqld[597]: Query (0): Connection ID (thread ID): 1
11月 16 12:46:01 archlinux mysqld[597]: Status: NOT_KILLED
11月 16 12:46:01 archlinux mysqld[597]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:46:01 archlinux mysqld[597]: information that should help you find out what is causing the crash.
11月 16 12:46:01 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:46:01 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:46:01 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:46:02 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 1.
11月 16 12:46:02 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:46:02 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:46:02 archlinux mysqld[642]: 2022-11-16T04:46:02.437365Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:46:02 archlinux mysqld[642]: 2022-11-16T04:46:02.437412Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 642
11月 16 12:46:02 archlinux mysqld[642]: 2022-11-16T04:46:02.440953Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:46:02 archlinux mysqld[642]: 2022-11-16T04:46:02.475418Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:46:02 archlinux mysqld[642]: 2022-11-16T04:46:02.475435Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140313649772224
11月 16 12:46:02 archlinux mysqld[642]: InnoDB: We intentionally generate a memory trap.
11月 16 12:46:02 archlinux mysqld[642]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:46:02 archlinux mysqld[642]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:46:02 archlinux mysqld[642]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:46:02 archlinux mysqld[642]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:46:02 archlinux mysqld[642]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:46:02 archlinux mysqld[642]: InnoDB: about forcing recovery.
11月 16 12:46:02 archlinux mysqld[642]: 2022-11-16T04:46:02Z UTC - mysqld got signal 6 ;
11月 16 12:46:02 archlinux mysqld[642]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:46:02 archlinux mysqld[642]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:46:02 archlinux mysqld[642]: Thread pointer: 0x563d679c5b30
11月 16 12:46:02 archlinux mysqld[642]: Attempting backtrace. You can use the following information to find out
11月 16 12:46:02 archlinux mysqld[642]: where mysqld died. If you see no messages after this, something went
11月 16 12:46:02 archlinux mysqld[642]: terribly wrong...
11月 16 12:46:02 archlinux mysqld[642]: stack_bottom = 7f9d51406c50 thread_stack 0x100000
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x563d62c11312]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x563d6226767f]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x563d6226782f]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(my_abort()+0xe) [0x563d62c0d0ae]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x563d62db33db]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(+0x1647f28) [0x563d62ce7f28]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x563d62cfe999]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x563d62da82ca]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(+0x15b21e2) [0x563d62c521e2]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x563d62a9796b]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x563d62c026bc]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(+0xc5beda) [0x563d622fbeda]
11月 16 12:46:02 archlinux mysqld[642]: /usr/bin/mysqld(+0x1943283) [0x563d62fe3283]
11月 16 12:46:02 archlinux mysqld[642]: /usr/lib/libc.so.6(+0x868fd) [0x7f9d5fa9f8fd]
11月 16 12:46:02 archlinux mysqld[642]: /usr/lib/libc.so.6(+0x108a60) [0x7f9d5fb21a60]
11月 16 12:46:02 archlinux mysqld[642]: Trying to get some variables.
11月 16 12:46:02 archlinux mysqld[642]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:46:02 archlinux mysqld[642]: Query (0): Connection ID (thread ID): 1
11月 16 12:46:02 archlinux mysqld[642]: Status: NOT_KILLED
11月 16 12:46:02 archlinux mysqld[642]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:46:02 archlinux mysqld[642]: information that should help you find out what is causing the crash.
11月 16 12:46:02 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:46:02 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:46:02 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:46:02 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 2.
11月 16 12:46:02 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:46:02 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:46:02 archlinux mysqld[713]: 2022-11-16T04:46:02.945565Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:46:02 archlinux mysqld[713]: 2022-11-16T04:46:02.945605Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 713
11月 16 12:46:02 archlinux mysqld[713]: 2022-11-16T04:46:02.948975Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:46:02 archlinux mysqld[713]: 2022-11-16T04:46:02.983819Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:46:02 archlinux mysqld[713]: 2022-11-16T04:46:02.983837Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140021057222336
11月 16 12:46:02 archlinux mysqld[713]: InnoDB: We intentionally generate a memory trap.
11月 16 12:46:02 archlinux mysqld[713]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:46:02 archlinux mysqld[713]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:46:02 archlinux mysqld[713]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:46:02 archlinux mysqld[713]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:46:02 archlinux mysqld[713]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:46:02 archlinux mysqld[713]: InnoDB: about forcing recovery.
11月 16 12:46:02 archlinux mysqld[713]: 2022-11-16T04:46:02Z UTC - mysqld got signal 6 ;
11月 16 12:46:02 archlinux mysqld[713]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:46:02 archlinux mysqld[713]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:46:02 archlinux mysqld[713]: Thread pointer: 0x5591e89b9b30
11月 16 12:46:02 archlinux mysqld[713]: Attempting backtrace. You can use the following information to find out
11月 16 12:46:02 archlinux mysqld[713]: where mysqld died. If you see no messages after this, something went
11月 16 12:46:02 archlinux mysqld[713]: terribly wrong...
11月 16 12:46:02 archlinux mysqld[713]: stack_bottom = 7f5931606c50 thread_stack 0x100000
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5591e3a0c312]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5591e306267f]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5591e306282f]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(my_abort()+0xe) [0x5591e3a080ae]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5591e3bae3db]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(+0x1647f28) [0x5591e3ae2f28]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5591e3af9999]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5591e3ba32ca]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(+0x15b21e2) [0x5591e3a4d1e2]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x5591e389296b]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5591e39fd6bc]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(+0xc5beda) [0x5591e30f6eda]
11月 16 12:46:02 archlinux mysqld[713]: /usr/bin/mysqld(+0x1943283) [0x5591e3dde283]
11月 16 12:46:02 archlinux mysqld[713]: /usr/lib/libc.so.6(+0x868fd) [0x7f593fc9f8fd]
11月 16 12:46:02 archlinux mysqld[713]: /usr/lib/libc.so.6(+0x108a60) [0x7f593fd21a60]
11月 16 12:46:02 archlinux mysqld[713]: Trying to get some variables.
11月 16 12:46:02 archlinux mysqld[713]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:46:02 archlinux mysqld[713]: Query (0): Connection ID (thread ID): 1
11月 16 12:46:02 archlinux mysqld[713]: Status: NOT_KILLED
11月 16 12:46:02 archlinux mysqld[713]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:46:02 archlinux mysqld[713]: information that should help you find out what is causing the crash.
11月 16 12:46:03 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:46:03 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:46:03 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:46:03 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 3.
11月 16 12:46:03 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:46:03 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:46:03 archlinux mysqld[766]: 2022-11-16T04:46:03.388049Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:46:03 archlinux mysqld[766]: 2022-11-16T04:46:03.388093Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 766
11月 16 12:46:03 archlinux mysqld[766]: 2022-11-16T04:46:03.391945Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:46:03 archlinux mysqld[766]: 2022-11-16T04:46:03.428680Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:46:03 archlinux mysqld[766]: 2022-11-16T04:46:03.428697Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140134453634752
11月 16 12:46:03 archlinux mysqld[766]: InnoDB: We intentionally generate a memory trap.
11月 16 12:46:03 archlinux mysqld[766]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:46:03 archlinux mysqld[766]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:46:03 archlinux mysqld[766]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:46:03 archlinux mysqld[766]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:46:03 archlinux mysqld[766]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:46:03 archlinux mysqld[766]: InnoDB: about forcing recovery.
11月 16 12:46:03 archlinux mysqld[766]: 2022-11-16T04:46:03Z UTC - mysqld got signal 6 ;
11月 16 12:46:03 archlinux mysqld[766]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:46:03 archlinux mysqld[766]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:46:03 archlinux mysqld[766]: Thread pointer: 0x55a0f2187b30
11月 16 12:46:03 archlinux mysqld[766]: Attempting backtrace. You can use the following information to find out
11月 16 12:46:03 archlinux mysqld[766]: where mysqld died. If you see no messages after this, something went
11月 16 12:46:03 archlinux mysqld[766]: terribly wrong...
11月 16 12:46:03 archlinux mysqld[766]: stack_bottom = 7f7398545c50 thread_stack 0x100000
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55a0ec491312]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55a0ebae767f]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55a0ebae782f]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(my_abort()+0xe) [0x55a0ec48d0ae]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55a0ec6333db]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(+0x1647f28) [0x55a0ec567f28]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55a0ec57e999]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55a0ec6282ca]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(+0x15b21e2) [0x55a0ec4d21e2]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55a0ec31796b]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55a0ec4826bc]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(+0xc5beda) [0x55a0ebb7beda]
11月 16 12:46:03 archlinux mysqld[766]: /usr/bin/mysqld(+0x1943283) [0x55a0ec863283]
11月 16 12:46:03 archlinux mysqld[766]: /usr/lib/libc.so.6(+0x868fd) [0x7f73a6a9f8fd]
11月 16 12:46:03 archlinux mysqld[766]: /usr/lib/libc.so.6(+0x108a60) [0x7f73a6b21a60]
11月 16 12:46:03 archlinux mysqld[766]: Trying to get some variables.
11月 16 12:46:03 archlinux mysqld[766]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:46:03 archlinux mysqld[766]: Query (0): Connection ID (thread ID): 1
11月 16 12:46:03 archlinux mysqld[766]: Status: NOT_KILLED
11月 16 12:46:03 archlinux mysqld[766]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:46:03 archlinux mysqld[766]: information that should help you find out what is causing the crash.
11月 16 12:46:03 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:46:03 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:46:03 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:46:03 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 4.
11月 16 12:46:03 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:46:03 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:46:03 archlinux mysqld[912]: 2022-11-16T04:46:03.928440Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:46:03 archlinux mysqld[912]: 2022-11-16T04:46:03.928485Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 912
11月 16 12:46:03 archlinux mysqld[912]: 2022-11-16T04:46:03.932011Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:46:03 archlinux mysqld[912]: 2022-11-16T04:46:03.966867Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:46:03 archlinux mysqld[912]: 2022-11-16T04:46:03.966883Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140060347365056
11月 16 12:46:03 archlinux mysqld[912]: InnoDB: We intentionally generate a memory trap.
11月 16 12:46:03 archlinux mysqld[912]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:46:03 archlinux mysqld[912]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:46:03 archlinux mysqld[912]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:46:03 archlinux mysqld[912]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:46:03 archlinux mysqld[912]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:46:03 archlinux mysqld[912]: InnoDB: about forcing recovery.
11月 16 12:46:03 archlinux mysqld[912]: 2022-11-16T04:46:03Z UTC - mysqld got signal 6 ;
11月 16 12:46:03 archlinux mysqld[912]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:46:03 archlinux mysqld[912]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:46:03 archlinux mysqld[912]: Thread pointer: 0x55d069240b30
11月 16 12:46:03 archlinux mysqld[912]: Attempting backtrace. You can use the following information to find out
11月 16 12:46:03 archlinux mysqld[912]: where mysqld died. If you see no messages after this, something went
11月 16 12:46:03 archlinux mysqld[912]: terribly wrong...
11月 16 12:46:03 archlinux mysqld[912]: stack_bottom = 7f6257406c50 thread_stack 0x100000
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55d063755312]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55d062dab67f]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55d062dab82f]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(my_abort()+0xe) [0x55d0637510ae]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55d0638f73db]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(+0x1647f28) [0x55d06382bf28]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55d063842999]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55d0638ec2ca]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(+0x15b21e2) [0x55d0637961e2]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55d0635db96b]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55d0637466bc]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(+0xc5beda) [0x55d062e3feda]
11月 16 12:46:03 archlinux mysqld[912]: /usr/bin/mysqld(+0x1943283) [0x55d063b27283]
11月 16 12:46:03 archlinux mysqld[912]: /usr/lib/libc.so.6(+0x868fd) [0x7f6265a9f8fd]
11月 16 12:46:03 archlinux mysqld[912]: /usr/lib/libc.so.6(+0x108a60) [0x7f6265b21a60]
11月 16 12:46:03 archlinux mysqld[912]: Trying to get some variables.
11月 16 12:46:03 archlinux mysqld[912]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:46:03 archlinux mysqld[912]: Query (0): Connection ID (thread ID): 1
11月 16 12:46:03 archlinux mysqld[912]: Status: NOT_KILLED
11月 16 12:46:03 archlinux mysqld[912]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:46:03 archlinux mysqld[912]: information that should help you find out what is causing the crash.
11月 16 12:46:04 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:46:04 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:46:04 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:46:04 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
11月 16 12:46:04 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:46:04 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 12:46:04 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:46:04 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:50:58 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:50:58 archlinux mysqld[3817]: 2022-11-16T04:50:58.450922Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:50:58 archlinux mysqld[3817]: 2022-11-16T04:50:58.450963Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 3817
11月 16 12:50:58 archlinux mysqld[3817]: 2022-11-16T04:50:58.454435Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:50:58 archlinux mysqld[3817]: 2022-11-16T04:50:58.524201Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:50:58 archlinux mysqld[3817]: 2022-11-16T04:50:58.524224Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140460284602048
11月 16 12:50:58 archlinux mysqld[3817]: InnoDB: We intentionally generate a memory trap.
11月 16 12:50:58 archlinux mysqld[3817]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:50:58 archlinux mysqld[3817]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:50:58 archlinux mysqld[3817]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:50:58 archlinux mysqld[3817]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:50:58 archlinux mysqld[3817]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:50:58 archlinux mysqld[3817]: InnoDB: about forcing recovery.
11月 16 12:50:58 archlinux mysqld[3817]: 2022-11-16T04:50:58Z UTC - mysqld got signal 6 ;
11月 16 12:50:58 archlinux mysqld[3817]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:50:58 archlinux mysqld[3817]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:50:58 archlinux mysqld[3817]: Thread pointer: 0x55bfa3f9ab10
11月 16 12:50:58 archlinux mysqld[3817]: Attempting backtrace. You can use the following information to find out
11月 16 12:50:58 archlinux mysqld[3817]: where mysqld died. If you see no messages after this, something went
11月 16 12:50:58 archlinux mysqld[3817]: terribly wrong...
11月 16 12:50:58 archlinux mysqld[3817]: stack_bottom = 7fbf755e5c50 thread_stack 0x100000
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55bf9e9c0312]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55bf9e01667f]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55bf9e01682f]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(my_abort()+0xe) [0x55bf9e9bc0ae]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55bf9eb623db]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(+0x1647f28) [0x55bf9ea96f28]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55bf9eaad999]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55bf9eb572ca]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(+0x15b21e2) [0x55bf9ea011e2]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55bf9e84696b]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55bf9e9b16bc]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(+0xc5beda) [0x55bf9e0aaeda]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/bin/mysqld(+0x1943283) [0x55bf9ed92283]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/lib/libc.so.6(+0x868fd) [0x7fbf83c9f8fd]
11月 16 12:50:58 archlinux mysqld[3817]: /usr/lib/libc.so.6(+0x108a60) [0x7fbf83d21a60]
11月 16 12:50:58 archlinux mysqld[3817]: Trying to get some variables.
11月 16 12:50:58 archlinux mysqld[3817]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:50:58 archlinux mysqld[3817]: Query (0): Connection ID (thread ID): 1
11月 16 12:50:58 archlinux mysqld[3817]: Status: NOT_KILLED
11月 16 12:50:58 archlinux mysqld[3817]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:50:58 archlinux mysqld[3817]: information that should help you find out what is causing the crash.
11月 16 12:50:58 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:50:58 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:50:58 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:50:58 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 1.
11月 16 12:50:58 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:50:58 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:50:59 archlinux mysqld[3858]: 2022-11-16T04:50:59.068035Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:50:59 archlinux mysqld[3858]: 2022-11-16T04:50:59.068077Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 3858
11月 16 12:50:59 archlinux mysqld[3858]: 2022-11-16T04:50:59.071655Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:50:59 archlinux mysqld[3858]: 2022-11-16T04:50:59.109786Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:50:59 archlinux mysqld[3858]: 2022-11-16T04:50:59.109809Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139801522366144
11月 16 12:50:59 archlinux mysqld[3858]: InnoDB: We intentionally generate a memory trap.
11月 16 12:50:59 archlinux mysqld[3858]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:50:59 archlinux mysqld[3858]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:50:59 archlinux mysqld[3858]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:50:59 archlinux mysqld[3858]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:50:59 archlinux mysqld[3858]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:50:59 archlinux mysqld[3858]: InnoDB: about forcing recovery.
11月 16 12:50:59 archlinux mysqld[3858]: 2022-11-16T04:50:59Z UTC - mysqld got signal 6 ;
11月 16 12:50:59 archlinux mysqld[3858]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:50:59 archlinux mysqld[3858]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:50:59 archlinux mysqld[3858]: Thread pointer: 0x55fb90801b10
11月 16 12:50:59 archlinux mysqld[3858]: Attempting backtrace. You can use the following information to find out
11月 16 12:50:59 archlinux mysqld[3858]: where mysqld died. If you see no messages after this, something went
11月 16 12:50:59 archlinux mysqld[3858]: terribly wrong...
11月 16 12:50:59 archlinux mysqld[3858]: stack_bottom = 7f2614145c50 thread_stack 0x100000
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55fb8b488312]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55fb8aade67f]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55fb8aade82f]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(my_abort()+0xe) [0x55fb8b4840ae]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55fb8b62a3db]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(+0x1647f28) [0x55fb8b55ef28]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55fb8b575999]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55fb8b61f2ca]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(+0x15b21e2) [0x55fb8b4c91e2]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55fb8b30e96b]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55fb8b4796bc]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(+0xc5beda) [0x55fb8ab72eda]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/bin/mysqld(+0x1943283) [0x55fb8b85a283]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/lib/libc.so.6(+0x868fd) [0x7f262269f8fd]
11月 16 12:50:59 archlinux mysqld[3858]: /usr/lib/libc.so.6(+0x108a60) [0x7f2622721a60]
11月 16 12:50:59 archlinux mysqld[3858]: Trying to get some variables.
11月 16 12:50:59 archlinux mysqld[3858]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:50:59 archlinux mysqld[3858]: Query (0): Connection ID (thread ID): 1
11月 16 12:50:59 archlinux mysqld[3858]: Status: NOT_KILLED
11月 16 12:50:59 archlinux mysqld[3858]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:50:59 archlinux mysqld[3858]: information that should help you find out what is causing the crash.
11月 16 12:50:59 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:50:59 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:50:59 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:50:59 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 2.
11月 16 12:50:59 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:50:59 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:50:59 archlinux mysqld[3895]: 2022-11-16T04:50:59.559868Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:50:59 archlinux mysqld[3895]: 2022-11-16T04:50:59.559910Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 3895
11月 16 12:50:59 archlinux mysqld[3895]: 2022-11-16T04:50:59.563463Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:50:59 archlinux mysqld[3895]: 2022-11-16T04:50:59.598925Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:50:59 archlinux mysqld[3895]: 2022-11-16T04:50:59.598947Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139653121197760
11月 16 12:50:59 archlinux mysqld[3895]: InnoDB: We intentionally generate a memory trap.
11月 16 12:50:59 archlinux mysqld[3895]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:50:59 archlinux mysqld[3895]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:50:59 archlinux mysqld[3895]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:50:59 archlinux mysqld[3895]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:50:59 archlinux mysqld[3895]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:50:59 archlinux mysqld[3895]: InnoDB: about forcing recovery.
11月 16 12:50:59 archlinux mysqld[3895]: 2022-11-16T04:50:59Z UTC - mysqld got signal 6 ;
11月 16 12:50:59 archlinux mysqld[3895]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:50:59 archlinux mysqld[3895]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:50:59 archlinux mysqld[3895]: Thread pointer: 0x5570284b9b10
11月 16 12:50:59 archlinux mysqld[3895]: Attempting backtrace. You can use the following information to find out
11月 16 12:50:59 archlinux mysqld[3895]: where mysqld died. If you see no messages after this, something went
11月 16 12:50:59 archlinux mysqld[3895]: terribly wrong...
11月 16 12:50:59 archlinux mysqld[3895]: stack_bottom = 7f0386ae3c50 thread_stack 0x100000
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5570227f0312]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x557021e4667f]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x557021e4682f]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(my_abort()+0xe) [0x5570227ec0ae]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5570229923db]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(+0x1647f28) [0x5570228c6f28]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5570228dd999]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5570229872ca]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(+0x15b21e2) [0x5570228311e2]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55702267696b]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5570227e16bc]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(+0xc5beda) [0x557021edaeda]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/bin/mysqld(+0x1943283) [0x557022bc2283]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/lib/libc.so.6(+0x868fd) [0x7f039509f8fd]
11月 16 12:50:59 archlinux mysqld[3895]: /usr/lib/libc.so.6(+0x108a60) [0x7f0395121a60]
11月 16 12:50:59 archlinux mysqld[3895]: Trying to get some variables.
11月 16 12:50:59 archlinux mysqld[3895]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:50:59 archlinux mysqld[3895]: Query (0): Connection ID (thread ID): 1
11月 16 12:50:59 archlinux mysqld[3895]: Status: NOT_KILLED
11月 16 12:50:59 archlinux mysqld[3895]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:50:59 archlinux mysqld[3895]: information that should help you find out what is causing the crash.
11月 16 12:50:59 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:50:59 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:50:59 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:50:59 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 3.
11月 16 12:50:59 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:50:59 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:51:00 archlinux mysqld[3932]: 2022-11-16T04:51:00.068187Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:51:00 archlinux mysqld[3932]: 2022-11-16T04:51:00.068229Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 3932
11月 16 12:51:00 archlinux mysqld[3932]: 2022-11-16T04:51:00.071876Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:51:00 archlinux mysqld[3932]: 2022-11-16T04:51:00.110603Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:51:00 archlinux mysqld[3932]: 2022-11-16T04:51:00.110625Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140399177131712
11月 16 12:51:00 archlinux mysqld[3932]: InnoDB: We intentionally generate a memory trap.
11月 16 12:51:00 archlinux mysqld[3932]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:51:00 archlinux mysqld[3932]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:51:00 archlinux mysqld[3932]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:51:00 archlinux mysqld[3932]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:51:00 archlinux mysqld[3932]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:51:00 archlinux mysqld[3932]: InnoDB: about forcing recovery.
11月 16 12:51:00 archlinux mysqld[3932]: 2022-11-16T04:51:00Z UTC - mysqld got signal 6 ;
11月 16 12:51:00 archlinux mysqld[3932]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:51:00 archlinux mysqld[3932]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:51:00 archlinux mysqld[3932]: Thread pointer: 0x557aff085b10
11月 16 12:51:00 archlinux mysqld[3932]: Attempting backtrace. You can use the following information to find out
11月 16 12:51:00 archlinux mysqld[3932]: where mysqld died. If you see no messages after this, something went
11月 16 12:51:00 archlinux mysqld[3932]: terribly wrong...
11月 16 12:51:00 archlinux mysqld[3932]: stack_bottom = 7fb13b145c50 thread_stack 0x100000
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x557afa55f312]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x557af9bb567f]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x557af9bb582f]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(my_abort()+0xe) [0x557afa55b0ae]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x557afa7013db]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(+0x1647f28) [0x557afa635f28]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x557afa64c999]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x557afa6f62ca]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(+0x15b21e2) [0x557afa5a01e2]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x557afa3e596b]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x557afa5506bc]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(+0xc5beda) [0x557af9c49eda]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/bin/mysqld(+0x1943283) [0x557afa931283]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/lib/libc.so.6(+0x868fd) [0x7fb14969f8fd]
11月 16 12:51:00 archlinux mysqld[3932]: /usr/lib/libc.so.6(+0x108a60) [0x7fb149721a60]
11月 16 12:51:00 archlinux mysqld[3932]: Trying to get some variables.
11月 16 12:51:00 archlinux mysqld[3932]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:51:00 archlinux mysqld[3932]: Query (0): Connection ID (thread ID): 1
11月 16 12:51:00 archlinux mysqld[3932]: Status: NOT_KILLED
11月 16 12:51:00 archlinux mysqld[3932]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:51:00 archlinux mysqld[3932]: information that should help you find out what is causing the crash.
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:51:00 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 4.
11月 16 12:51:00 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:51:00 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:51:00 archlinux mysqld[3969]: 2022-11-16T04:51:00.540088Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:51:00 archlinux mysqld[3969]: 2022-11-16T04:51:00.540132Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 3969
11月 16 12:51:00 archlinux mysqld[3969]: 2022-11-16T04:51:00.543518Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:51:00 archlinux mysqld[3969]: 2022-11-16T04:51:00.582012Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:51:00 archlinux mysqld[3969]: 2022-11-16T04:51:00.582035Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139913438258880
11月 16 12:51:00 archlinux mysqld[3969]: InnoDB: We intentionally generate a memory trap.
11月 16 12:51:00 archlinux mysqld[3969]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:51:00 archlinux mysqld[3969]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:51:00 archlinux mysqld[3969]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:51:00 archlinux mysqld[3969]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:51:00 archlinux mysqld[3969]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:51:00 archlinux mysqld[3969]: InnoDB: about forcing recovery.
11月 16 12:51:00 archlinux mysqld[3969]: 2022-11-16T04:51:00Z UTC - mysqld got signal 6 ;
11月 16 12:51:00 archlinux mysqld[3969]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:51:00 archlinux mysqld[3969]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:51:00 archlinux mysqld[3969]: Thread pointer: 0x5568de555b10
11月 16 12:51:00 archlinux mysqld[3969]: Attempting backtrace. You can use the following information to find out
11月 16 12:51:00 archlinux mysqld[3969]: where mysqld died. If you see no messages after this, something went
11月 16 12:51:00 archlinux mysqld[3969]: terribly wrong...
11月 16 12:51:00 archlinux mysqld[3969]: stack_bottom = 7f4022c95c50 thread_stack 0x100000
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5568d85a4312]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5568d7bfa67f]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5568d7bfa82f]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(my_abort()+0xe) [0x5568d85a00ae]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5568d87463db]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(+0x1647f28) [0x5568d867af28]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5568d8691999]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5568d873b2ca]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(+0x15b21e2) [0x5568d85e51e2]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x5568d842a96b]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5568d85956bc]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(+0xc5beda) [0x5568d7c8eeda]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/bin/mysqld(+0x1943283) [0x5568d8976283]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/lib/libc.so.6(+0x868fd) [0x7f403129f8fd]
11月 16 12:51:00 archlinux mysqld[3969]: /usr/lib/libc.so.6(+0x108a60) [0x7f4031321a60]
11月 16 12:51:00 archlinux mysqld[3969]: Trying to get some variables.
11月 16 12:51:00 archlinux mysqld[3969]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:51:00 archlinux mysqld[3969]: Query (0): Connection ID (thread ID): 1
11月 16 12:51:00 archlinux mysqld[3969]: Status: NOT_KILLED
11月 16 12:51:00 archlinux mysqld[3969]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:51:00 archlinux mysqld[3969]: information that should help you find out what is causing the crash.
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:51:00 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
11月 16 12:51:00 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 12:51:00 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:51:00 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:57:47 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:57:47 archlinux mysqld[4527]: 2022-11-16T04:57:47.600292Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:57:47 archlinux mysqld[4527]: 2022-11-16T04:57:47.600336Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 4527
11月 16 12:57:47 archlinux mysqld[4527]: 2022-11-16T04:57:47.603938Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:57:47 archlinux mysqld[4527]: 2022-11-16T04:57:47.642423Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:57:47 archlinux mysqld[4527]: 2022-11-16T04:57:47.642445Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139696725317312
11月 16 12:57:47 archlinux mysqld[4527]: InnoDB: We intentionally generate a memory trap.
11月 16 12:57:47 archlinux mysqld[4527]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:57:47 archlinux mysqld[4527]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:57:47 archlinux mysqld[4527]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:57:47 archlinux mysqld[4527]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:57:47 archlinux mysqld[4527]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:57:47 archlinux mysqld[4527]: InnoDB: about forcing recovery.
11月 16 12:57:47 archlinux mysqld[4527]: 2022-11-16T04:57:47Z UTC - mysqld got signal 6 ;
11月 16 12:57:47 archlinux mysqld[4527]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:57:47 archlinux mysqld[4527]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:57:47 archlinux mysqld[4527]: Thread pointer: 0x5574c1b49b10
11月 16 12:57:47 archlinux mysqld[4527]: Attempting backtrace. You can use the following information to find out
11月 16 12:57:47 archlinux mysqld[4527]: where mysqld died. If you see no messages after this, something went
11月 16 12:57:47 archlinux mysqld[4527]: terribly wrong...
11月 16 12:57:47 archlinux mysqld[4527]: stack_bottom = 7f0dadb04c50 thread_stack 0x100000
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5574bd1c4312]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5574bc81a67f]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5574bc81a82f]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(my_abort()+0xe) [0x5574bd1c00ae]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5574bd3663db]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(+0x1647f28) [0x5574bd29af28]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5574bd2b1999]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5574bd35b2ca]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(+0x15b21e2) [0x5574bd2051e2]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x5574bd04a96b]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5574bd1b56bc]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(+0xc5beda) [0x5574bc8aeeda]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/bin/mysqld(+0x1943283) [0x5574bd596283]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/lib/libc.so.6(+0x868fd) [0x7f0dbc09f8fd]
11月 16 12:57:47 archlinux mysqld[4527]: /usr/lib/libc.so.6(+0x108a60) [0x7f0dbc121a60]
11月 16 12:57:47 archlinux mysqld[4527]: Trying to get some variables.
11月 16 12:57:47 archlinux mysqld[4527]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:57:47 archlinux mysqld[4527]: Query (0): Connection ID (thread ID): 1
11月 16 12:57:47 archlinux mysqld[4527]: Status: NOT_KILLED
11月 16 12:57:47 archlinux mysqld[4527]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:57:47 archlinux mysqld[4527]: information that should help you find out what is causing the crash.
11月 16 12:57:47 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:57:47 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:57:47 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:57:47 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 1.
11月 16 12:57:47 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:57:47 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:57:48 archlinux mysqld[4570]: 2022-11-16T04:57:48.069819Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:57:48 archlinux mysqld[4570]: 2022-11-16T04:57:48.069862Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 4570
11月 16 12:57:48 archlinux mysqld[4570]: 2022-11-16T04:57:48.073496Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:57:48 archlinux mysqld[4570]: 2022-11-16T04:57:48.111782Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:57:48 archlinux mysqld[4570]: 2022-11-16T04:57:48.111805Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140132045702848
11月 16 12:57:48 archlinux mysqld[4570]: InnoDB: We intentionally generate a memory trap.
11月 16 12:57:48 archlinux mysqld[4570]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:57:48 archlinux mysqld[4570]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:57:48 archlinux mysqld[4570]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:57:48 archlinux mysqld[4570]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:57:48 archlinux mysqld[4570]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:57:48 archlinux mysqld[4570]: InnoDB: about forcing recovery.
11月 16 12:57:48 archlinux mysqld[4570]: 2022-11-16T04:57:48Z UTC - mysqld got signal 6 ;
11月 16 12:57:48 archlinux mysqld[4570]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:57:48 archlinux mysqld[4570]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:57:48 archlinux mysqld[4570]: Thread pointer: 0x5640d52fdb10
11月 16 12:57:48 archlinux mysqld[4570]: Attempting backtrace. You can use the following information to find out
11月 16 12:57:48 archlinux mysqld[4570]: where mysqld died. If you see no messages after this, something went
11月 16 12:57:48 archlinux mysqld[4570]: terribly wrong...
11月 16 12:57:48 archlinux mysqld[4570]: stack_bottom = 7f7308ce3c50 thread_stack 0x100000
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5640cf487312]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5640ceadd67f]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5640ceadd82f]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(my_abort()+0xe) [0x5640cf4830ae]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5640cf6293db]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(+0x1647f28) [0x5640cf55df28]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5640cf574999]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5640cf61e2ca]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(+0x15b21e2) [0x5640cf4c81e2]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x5640cf30d96b]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5640cf4786bc]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(+0xc5beda) [0x5640ceb71eda]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/bin/mysqld(+0x1943283) [0x5640cf859283]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/lib/libc.so.6(+0x868fd) [0x7f731729f8fd]
11月 16 12:57:48 archlinux mysqld[4570]: /usr/lib/libc.so.6(+0x108a60) [0x7f7317321a60]
11月 16 12:57:48 archlinux mysqld[4570]: Trying to get some variables.
11月 16 12:57:48 archlinux mysqld[4570]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:57:48 archlinux mysqld[4570]: Query (0): Connection ID (thread ID): 1
11月 16 12:57:48 archlinux mysqld[4570]: Status: NOT_KILLED
11月 16 12:57:48 archlinux mysqld[4570]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:57:48 archlinux mysqld[4570]: information that should help you find out what is causing the crash.
11月 16 12:57:48 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:57:48 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:57:48 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:57:48 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 2.
11月 16 12:57:48 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:57:48 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:57:48 archlinux mysqld[4607]: 2022-11-16T04:57:48.550304Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:57:48 archlinux mysqld[4607]: 2022-11-16T04:57:48.550347Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 4607
11月 16 12:57:48 archlinux mysqld[4607]: 2022-11-16T04:57:48.553808Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:57:48 archlinux mysqld[4607]: 2022-11-16T04:57:48.592900Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:57:48 archlinux mysqld[4607]: 2022-11-16T04:57:48.592919Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140648248276672
11月 16 12:57:48 archlinux mysqld[4607]: InnoDB: We intentionally generate a memory trap.
11月 16 12:57:48 archlinux mysqld[4607]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:57:48 archlinux mysqld[4607]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:57:48 archlinux mysqld[4607]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:57:48 archlinux mysqld[4607]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:57:48 archlinux mysqld[4607]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:57:48 archlinux mysqld[4607]: InnoDB: about forcing recovery.
11月 16 12:57:48 archlinux mysqld[4607]: 2022-11-16T04:57:48Z UTC - mysqld got signal 6 ;
11月 16 12:57:48 archlinux mysqld[4607]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:57:48 archlinux mysqld[4607]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:57:48 archlinux mysqld[4607]: Thread pointer: 0x55d0498fab10
11月 16 12:57:48 archlinux mysqld[4607]: Attempting backtrace. You can use the following information to find out
11月 16 12:57:48 archlinux mysqld[4607]: where mysqld died. If you see no messages after this, something went
11月 16 12:57:48 archlinux mysqld[4607]: terribly wrong...
11月 16 12:57:48 archlinux mysqld[4607]: stack_bottom = 7feb38e06c50 thread_stack 0x100000
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55d0442a6312]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55d0438fc67f]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55d0438fc82f]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(my_abort()+0xe) [0x55d0442a20ae]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55d0444483db]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(+0x1647f28) [0x55d04437cf28]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55d044393999]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55d04443d2ca]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(+0x15b21e2) [0x55d0442e71e2]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55d04412c96b]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55d0442976bc]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(+0xc5beda) [0x55d043990eda]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/bin/mysqld(+0x1943283) [0x55d044678283]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/lib/libc.so.6(+0x868fd) [0x7feb4749f8fd]
11月 16 12:57:48 archlinux mysqld[4607]: /usr/lib/libc.so.6(+0x108a60) [0x7feb47521a60]
11月 16 12:57:48 archlinux mysqld[4607]: Trying to get some variables.
11月 16 12:57:48 archlinux mysqld[4607]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:57:48 archlinux mysqld[4607]: Query (0): Connection ID (thread ID): 1
11月 16 12:57:48 archlinux mysqld[4607]: Status: NOT_KILLED
11月 16 12:57:48 archlinux mysqld[4607]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:57:48 archlinux mysqld[4607]: information that should help you find out what is causing the crash.
11月 16 12:57:48 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:57:48 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:57:48 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:57:48 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 3.
11月 16 12:57:48 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:57:48 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:57:49 archlinux mysqld[4644]: 2022-11-16T04:57:49.049173Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:57:49 archlinux mysqld[4644]: 2022-11-16T04:57:49.049215Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 4644
11月 16 12:57:49 archlinux mysqld[4644]: 2022-11-16T04:57:49.052597Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:57:49 archlinux mysqld[4644]: 2022-11-16T04:57:49.091442Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:57:49 archlinux mysqld[4644]: 2022-11-16T04:57:49.091461Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139731398588096
11月 16 12:57:49 archlinux mysqld[4644]: InnoDB: We intentionally generate a memory trap.
11月 16 12:57:49 archlinux mysqld[4644]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:57:49 archlinux mysqld[4644]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:57:49 archlinux mysqld[4644]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:57:49 archlinux mysqld[4644]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:57:49 archlinux mysqld[4644]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:57:49 archlinux mysqld[4644]: InnoDB: about forcing recovery.
11月 16 12:57:49 archlinux mysqld[4644]: 2022-11-16T04:57:49Z UTC - mysqld got signal 6 ;
11月 16 12:57:49 archlinux mysqld[4644]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:57:49 archlinux mysqld[4644]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:57:49 archlinux mysqld[4644]: Thread pointer: 0x55a9f5751b10
11月 16 12:57:49 archlinux mysqld[4644]: Attempting backtrace. You can use the following information to find out
11月 16 12:57:49 archlinux mysqld[4644]: where mysqld died. If you see no messages after this, something went
11月 16 12:57:49 archlinux mysqld[4644]: terribly wrong...
11月 16 12:57:49 archlinux mysqld[4644]: stack_bottom = 7f15c0606c50 thread_stack 0x100000
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55a9ef167312]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55a9ee7bd67f]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55a9ee7bd82f]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(my_abort()+0xe) [0x55a9ef1630ae]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55a9ef3093db]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(+0x1647f28) [0x55a9ef23df28]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55a9ef254999]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55a9ef2fe2ca]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(+0x15b21e2) [0x55a9ef1a81e2]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55a9eefed96b]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55a9ef1586bc]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(+0xc5beda) [0x55a9ee851eda]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/bin/mysqld(+0x1943283) [0x55a9ef539283]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/lib/libc.so.6(+0x868fd) [0x7f15cec9f8fd]
11月 16 12:57:49 archlinux mysqld[4644]: /usr/lib/libc.so.6(+0x108a60) [0x7f15ced21a60]
11月 16 12:57:49 archlinux mysqld[4644]: Trying to get some variables.
11月 16 12:57:49 archlinux mysqld[4644]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:57:49 archlinux mysqld[4644]: Query (0): Connection ID (thread ID): 1
11月 16 12:57:49 archlinux mysqld[4644]: Status: NOT_KILLED
11月 16 12:57:49 archlinux mysqld[4644]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:57:49 archlinux mysqld[4644]: information that should help you find out what is causing the crash.
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:57:49 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 4.
11月 16 12:57:49 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:57:49 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:57:49 archlinux mysqld[4682]: 2022-11-16T04:57:49.549262Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:57:49 archlinux mysqld[4682]: 2022-11-16T04:57:49.549305Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 4682
11月 16 12:57:49 archlinux mysqld[4682]: 2022-11-16T04:57:49.552643Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:57:49 archlinux mysqld[4682]: 2022-11-16T04:57:49.592337Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:57:49 archlinux mysqld[4682]: 2022-11-16T04:57:49.592356Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140156822648512
11月 16 12:57:49 archlinux mysqld[4682]: InnoDB: We intentionally generate a memory trap.
11月 16 12:57:49 archlinux mysqld[4682]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:57:49 archlinux mysqld[4682]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:57:49 archlinux mysqld[4682]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:57:49 archlinux mysqld[4682]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:57:49 archlinux mysqld[4682]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:57:49 archlinux mysqld[4682]: InnoDB: about forcing recovery.
11月 16 12:57:49 archlinux mysqld[4682]: 2022-11-16T04:57:49Z UTC - mysqld got signal 6 ;
11月 16 12:57:49 archlinux mysqld[4682]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:57:49 archlinux mysqld[4682]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:57:49 archlinux mysqld[4682]: Thread pointer: 0x55e39aa5fb10
11月 16 12:57:49 archlinux mysqld[4682]: Attempting backtrace. You can use the following information to find out
11月 16 12:57:49 archlinux mysqld[4682]: where mysqld died. If you see no messages after this, something went
11月 16 12:57:49 archlinux mysqld[4682]: terribly wrong...
11月 16 12:57:49 archlinux mysqld[4682]: stack_bottom = 7f78cda06c50 thread_stack 0x100000
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55e394ed8312]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55e39452e67f]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55e39452e82f]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(my_abort()+0xe) [0x55e394ed40ae]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55e39507a3db]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(+0x1647f28) [0x55e394faef28]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55e394fc5999]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55e39506f2ca]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(+0x15b21e2) [0x55e394f191e2]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55e394d5e96b]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55e394ec96bc]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(+0xc5beda) [0x55e3945c2eda]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/bin/mysqld(+0x1943283) [0x55e3952aa283]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/lib/libc.so.6(+0x868fd) [0x7f78dc09f8fd]
11月 16 12:57:49 archlinux mysqld[4682]: /usr/lib/libc.so.6(+0x108a60) [0x7f78dc121a60]
11月 16 12:57:49 archlinux mysqld[4682]: Trying to get some variables.
11月 16 12:57:49 archlinux mysqld[4682]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:57:49 archlinux mysqld[4682]: Query (0): Connection ID (thread ID): 1
11月 16 12:57:49 archlinux mysqld[4682]: Status: NOT_KILLED
11月 16 12:57:49 archlinux mysqld[4682]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:57:49 archlinux mysqld[4682]: information that should help you find out what is causing the crash.
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:57:49 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
11月 16 12:57:49 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 12:57:49 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:57:49 archlinux systemd[1]: Failed to start MySQL Server.
-- Boot 68f7bd108bde43d4afbe336494f05495 --
11月 16 12:59:11 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:59:11 archlinux mysqld[600]: 2022-11-16T04:59:11.804596Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:59:11 archlinux mysqld[600]: 2022-11-16T04:59:11.804639Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 600
11月 16 12:59:11 archlinux mysqld[600]: 2022-11-16T04:59:11.811513Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:59:11 archlinux mysqld[600]: 2022-11-16T04:59:11.864054Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:59:11 archlinux mysqld[600]: 2022-11-16T04:59:11.864075Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140500994180800
11月 16 12:59:11 archlinux mysqld[600]: InnoDB: We intentionally generate a memory trap.
11月 16 12:59:11 archlinux mysqld[600]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:59:11 archlinux mysqld[600]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:59:11 archlinux mysqld[600]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:59:11 archlinux mysqld[600]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:59:11 archlinux mysqld[600]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:59:11 archlinux mysqld[600]: InnoDB: about forcing recovery.
11月 16 12:59:11 archlinux mysqld[600]: 2022-11-16T04:59:11Z UTC - mysqld got signal 6 ;
11月 16 12:59:11 archlinux mysqld[600]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:59:11 archlinux mysqld[600]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:59:11 archlinux mysqld[600]: Thread pointer: 0x5608bbe05b30
11月 16 12:59:11 archlinux mysqld[600]: Attempting backtrace. You can use the following information to find out
11月 16 12:59:11 archlinux mysqld[600]: where mysqld died. If you see no messages after this, something went
11月 16 12:59:11 archlinux mysqld[600]: terribly wrong...
11月 16 12:59:11 archlinux mysqld[600]: stack_bottom = 7fc8efd93c50 thread_stack 0x100000
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5608b6e11312]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5608b646767f]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5608b646782f]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(my_abort()+0xe) [0x5608b6e0d0ae]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5608b6fb33db]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(+0x1647f28) [0x5608b6ee7f28]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5608b6efe999]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5608b6fa82ca]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(+0x15b21e2) [0x5608b6e521e2]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x5608b6c9796b]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5608b6e026bc]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(+0xc5beda) [0x5608b64fbeda]
11月 16 12:59:11 archlinux mysqld[600]: /usr/bin/mysqld(+0x1943283) [0x5608b71e3283]
11月 16 12:59:11 archlinux mysqld[600]: /usr/lib/libc.so.6(+0x868fd) [0x7fc8fe29f8fd]
11月 16 12:59:11 archlinux mysqld[600]: /usr/lib/libc.so.6(+0x108a60) [0x7fc8fe321a60]
11月 16 12:59:11 archlinux mysqld[600]: Trying to get some variables.
11月 16 12:59:11 archlinux mysqld[600]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:59:11 archlinux mysqld[600]: Query (0): Connection ID (thread ID): 1
11月 16 12:59:11 archlinux mysqld[600]: Status: NOT_KILLED
11月 16 12:59:11 archlinux mysqld[600]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:59:11 archlinux mysqld[600]: information that should help you find out what is causing the crash.
11月 16 12:59:11 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:59:11 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:59:11 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:59:12 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 1.
11月 16 12:59:12 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:59:12 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:59:12 archlinux mysqld[643]: 2022-11-16T04:59:12.467064Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:59:12 archlinux mysqld[643]: 2022-11-16T04:59:12.467107Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 643
11月 16 12:59:12 archlinux mysqld[643]: 2022-11-16T04:59:12.470624Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:59:12 archlinux mysqld[643]: 2022-11-16T04:59:12.505125Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:59:12 archlinux mysqld[643]: 2022-11-16T04:59:12.505144Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139999127303872
11月 16 12:59:12 archlinux mysqld[643]: InnoDB: We intentionally generate a memory trap.
11月 16 12:59:12 archlinux mysqld[643]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:59:12 archlinux mysqld[643]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:59:12 archlinux mysqld[643]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:59:12 archlinux mysqld[643]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:59:12 archlinux mysqld[643]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:59:12 archlinux mysqld[643]: InnoDB: about forcing recovery.
11月 16 12:59:12 archlinux mysqld[643]: 2022-11-16T04:59:12Z UTC - mysqld got signal 6 ;
11月 16 12:59:12 archlinux mysqld[643]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:59:12 archlinux mysqld[643]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:59:12 archlinux mysqld[643]: Thread pointer: 0x55accd52ab30
11月 16 12:59:12 archlinux mysqld[643]: Attempting backtrace. You can use the following information to find out
11月 16 12:59:12 archlinux mysqld[643]: where mysqld died. If you see no messages after this, something went
11月 16 12:59:12 archlinux mysqld[643]: terribly wrong...
11月 16 12:59:12 archlinux mysqld[643]: stack_bottom = 7f5416406c50 thread_stack 0x100000
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55acc8326312]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55acc797c67f]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55acc797c82f]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(my_abort()+0xe) [0x55acc83220ae]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55acc84c83db]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(+0x1647f28) [0x55acc83fcf28]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55acc8413999]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55acc84bd2ca]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(+0x15b21e2) [0x55acc83671e2]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55acc81ac96b]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55acc83176bc]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(+0xc5beda) [0x55acc7a10eda]
11月 16 12:59:12 archlinux mysqld[643]: /usr/bin/mysqld(+0x1943283) [0x55acc86f8283]
11月 16 12:59:12 archlinux mysqld[643]: /usr/lib/libc.so.6(+0x868fd) [0x7f5424a9f8fd]
11月 16 12:59:12 archlinux mysqld[643]: /usr/lib/libc.so.6(+0x108a60) [0x7f5424b21a60]
11月 16 12:59:12 archlinux mysqld[643]: Trying to get some variables.
11月 16 12:59:12 archlinux mysqld[643]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:59:12 archlinux mysqld[643]: Query (0): Connection ID (thread ID): 1
11月 16 12:59:12 archlinux mysqld[643]: Status: NOT_KILLED
11月 16 12:59:12 archlinux mysqld[643]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:59:12 archlinux mysqld[643]: information that should help you find out what is causing the crash.
11月 16 12:59:12 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:59:12 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:59:12 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:59:12 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 2.
11月 16 12:59:12 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:59:12 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:59:13 archlinux mysqld[714]: 2022-11-16T04:59:13.127518Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:59:13 archlinux mysqld[714]: 2022-11-16T04:59:13.127563Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 714
11月 16 12:59:13 archlinux mysqld[714]: 2022-11-16T04:59:13.131109Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:59:13 archlinux mysqld[714]: 2022-11-16T04:59:13.166759Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:59:13 archlinux mysqld[714]: 2022-11-16T04:59:13.166774Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139896729663168
11月 16 12:59:13 archlinux mysqld[714]: InnoDB: We intentionally generate a memory trap.
11月 16 12:59:13 archlinux mysqld[714]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:59:13 archlinux mysqld[714]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:59:13 archlinux mysqld[714]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:59:13 archlinux mysqld[714]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:59:13 archlinux mysqld[714]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:59:13 archlinux mysqld[714]: InnoDB: about forcing recovery.
11月 16 12:59:13 archlinux mysqld[714]: 2022-11-16T04:59:13Z UTC - mysqld got signal 6 ;
11月 16 12:59:13 archlinux mysqld[714]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:59:13 archlinux mysqld[714]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:59:13 archlinux mysqld[714]: Thread pointer: 0x560f2ec61b30
11月 16 12:59:13 archlinux mysqld[714]: Attempting backtrace. You can use the following information to find out
11月 16 12:59:13 archlinux mysqld[714]: where mysqld died. If you see no messages after this, something went
11月 16 12:59:13 archlinux mysqld[714]: terribly wrong...
11月 16 12:59:13 archlinux mysqld[714]: stack_bottom = 7f3c3ee06c50 thread_stack 0x100000
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x560f298ad312]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x560f28f0367f]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x560f28f0382f]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(my_abort()+0xe) [0x560f298a90ae]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x560f29a4f3db]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(+0x1647f28) [0x560f29983f28]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x560f2999a999]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x560f29a442ca]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(+0x15b21e2) [0x560f298ee1e2]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x560f2973396b]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x560f2989e6bc]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(+0xc5beda) [0x560f28f97eda]
11月 16 12:59:13 archlinux mysqld[714]: /usr/bin/mysqld(+0x1943283) [0x560f29c7f283]
11月 16 12:59:13 archlinux mysqld[714]: /usr/lib/libc.so.6(+0x868fd) [0x7f3c4d49f8fd]
11月 16 12:59:13 archlinux mysqld[714]: /usr/lib/libc.so.6(+0x108a60) [0x7f3c4d521a60]
11月 16 12:59:13 archlinux mysqld[714]: Trying to get some variables.
11月 16 12:59:13 archlinux mysqld[714]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:59:13 archlinux mysqld[714]: Query (0): Connection ID (thread ID): 1
11月 16 12:59:13 archlinux mysqld[714]: Status: NOT_KILLED
11月 16 12:59:13 archlinux mysqld[714]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:59:13 archlinux mysqld[714]: information that should help you find out what is causing the crash.
11月 16 12:59:13 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:59:13 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:59:13 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:59:13 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 3.
11月 16 12:59:13 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:59:13 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:59:13 archlinux mysqld[831]: 2022-11-16T04:59:13.536276Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:59:13 archlinux mysqld[831]: 2022-11-16T04:59:13.536320Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 831
11月 16 12:59:13 archlinux mysqld[831]: 2022-11-16T04:59:13.539998Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:59:13 archlinux mysqld[831]: 2022-11-16T04:59:13.576080Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:59:13 archlinux mysqld[831]: 2022-11-16T04:59:13.576101Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139762187462336
11月 16 12:59:13 archlinux mysqld[831]: InnoDB: We intentionally generate a memory trap.
11月 16 12:59:13 archlinux mysqld[831]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:59:13 archlinux mysqld[831]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:59:13 archlinux mysqld[831]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:59:13 archlinux mysqld[831]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:59:13 archlinux mysqld[831]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:59:13 archlinux mysqld[831]: InnoDB: about forcing recovery.
11月 16 12:59:13 archlinux mysqld[831]: 2022-11-16T04:59:13Z UTC - mysqld got signal 6 ;
11月 16 12:59:13 archlinux mysqld[831]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:59:13 archlinux mysqld[831]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:59:13 archlinux mysqld[831]: Thread pointer: 0x55ba72974b30
11月 16 12:59:13 archlinux mysqld[831]: Attempting backtrace. You can use the following information to find out
11月 16 12:59:13 archlinux mysqld[831]: where mysqld died. If you see no messages after this, something went
11月 16 12:59:13 archlinux mysqld[831]: terribly wrong...
11月 16 12:59:13 archlinux mysqld[831]: stack_bottom = 7f1ceb895c50 thread_stack 0x100000
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55ba6d687312]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55ba6ccdd67f]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55ba6ccdd82f]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(my_abort()+0xe) [0x55ba6d6830ae]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55ba6d8293db]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(+0x1647f28) [0x55ba6d75df28]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55ba6d774999]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55ba6d81e2ca]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(+0x15b21e2) [0x55ba6d6c81e2]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55ba6d50d96b]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55ba6d6786bc]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(+0xc5beda) [0x55ba6cd71eda]
11月 16 12:59:13 archlinux mysqld[831]: /usr/bin/mysqld(+0x1943283) [0x55ba6da59283]
11月 16 12:59:13 archlinux mysqld[831]: /usr/lib/libc.so.6(+0x868fd) [0x7f1cf9e9f8fd]
11月 16 12:59:13 archlinux mysqld[831]: /usr/lib/libc.so.6(+0x108a60) [0x7f1cf9f21a60]
11月 16 12:59:13 archlinux mysqld[831]: Trying to get some variables.
11月 16 12:59:13 archlinux mysqld[831]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:59:13 archlinux mysqld[831]: Query (0): Connection ID (thread ID): 1
11月 16 12:59:13 archlinux mysqld[831]: Status: NOT_KILLED
11月 16 12:59:13 archlinux mysqld[831]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:59:13 archlinux mysqld[831]: information that should help you find out what is causing the crash.
11月 16 12:59:13 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:59:13 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:59:13 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:59:13 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 4.
11月 16 12:59:13 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:59:13 archlinux systemd[1]: Starting MySQL Server...
11月 16 12:59:13 archlinux mysqld[923]: 2022-11-16T04:59:13.977035Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 12:59:13 archlinux mysqld[923]: 2022-11-16T04:59:13.977078Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 923
11月 16 12:59:13 archlinux mysqld[923]: 2022-11-16T04:59:13.981060Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 12:59:14 archlinux mysqld[923]: 2022-11-16T04:59:14.016477Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 12:59:14 archlinux mysqld[923]: 2022-11-16T04:59:14.016497Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140368680666816
11月 16 12:59:14 archlinux mysqld[923]: InnoDB: We intentionally generate a memory trap.
11月 16 12:59:14 archlinux mysqld[923]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 12:59:14 archlinux mysqld[923]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 12:59:14 archlinux mysqld[923]: InnoDB: immediately after the mysqld startup, there may be
11月 16 12:59:14 archlinux mysqld[923]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 12:59:14 archlinux mysqld[923]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 12:59:14 archlinux mysqld[923]: InnoDB: about forcing recovery.
11月 16 12:59:14 archlinux mysqld[923]: 2022-11-16T04:59:14Z UTC - mysqld got signal 6 ;
11月 16 12:59:14 archlinux mysqld[923]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 12:59:14 archlinux mysqld[923]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 12:59:14 archlinux mysqld[923]: Thread pointer: 0x5647b7411b30
11月 16 12:59:14 archlinux mysqld[923]: Attempting backtrace. You can use the following information to find out
11月 16 12:59:14 archlinux mysqld[923]: where mysqld died. If you see no messages after this, something went
11月 16 12:59:14 archlinux mysqld[923]: terribly wrong...
11月 16 12:59:14 archlinux mysqld[923]: stack_bottom = 7faa21593c50 thread_stack 0x100000
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5647b2249312]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5647b189f67f]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5647b189f82f]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(my_abort()+0xe) [0x5647b22450ae]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5647b23eb3db]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(+0x1647f28) [0x5647b231ff28]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5647b2336999]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5647b23e02ca]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(+0x15b21e2) [0x5647b228a1e2]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x5647b20cf96b]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5647b223a6bc]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(+0xc5beda) [0x5647b1933eda]
11月 16 12:59:14 archlinux mysqld[923]: /usr/bin/mysqld(+0x1943283) [0x5647b261b283]
11月 16 12:59:14 archlinux mysqld[923]: /usr/lib/libc.so.6(+0x868fd) [0x7faa2fa9f8fd]
11月 16 12:59:14 archlinux mysqld[923]: /usr/lib/libc.so.6(+0x108a60) [0x7faa2fb21a60]
11月 16 12:59:14 archlinux mysqld[923]: Trying to get some variables.
11月 16 12:59:14 archlinux mysqld[923]: Some pointers may be invalid and cause the dump to abort.
11月 16 12:59:14 archlinux mysqld[923]: Query (0): Connection ID (thread ID): 1
11月 16 12:59:14 archlinux mysqld[923]: Status: NOT_KILLED
11月 16 12:59:14 archlinux mysqld[923]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 12:59:14 archlinux mysqld[923]: information that should help you find out what is causing the crash.
11月 16 12:59:14 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 12:59:14 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:59:14 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 12:59:14 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
11月 16 12:59:14 archlinux systemd[1]: Stopped MySQL Server.
11月 16 12:59:14 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 12:59:14 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 12:59:14 archlinux systemd[1]: Failed to start MySQL Server.
-- Boot 41debd8748b5460e9205679c4356f2a4 --
11月 16 13:16:44 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:16:44 archlinux mysqld[599]: 2022-11-16T05:16:44.251017Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:16:44 archlinux mysqld[599]: 2022-11-16T05:16:44.251061Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 599
11月 16 13:16:44 archlinux mysqld[599]: 2022-11-16T05:16:44.257872Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:16:44 archlinux mysqld[599]: 2022-11-16T05:16:44.308382Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:16:44 archlinux mysqld[599]: 2022-11-16T05:16:44.308402Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139864120256192
11月 16 13:16:44 archlinux mysqld[599]: InnoDB: We intentionally generate a memory trap.
11月 16 13:16:44 archlinux mysqld[599]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:16:44 archlinux mysqld[599]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:16:44 archlinux mysqld[599]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:16:44 archlinux mysqld[599]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:16:44 archlinux mysqld[599]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:16:44 archlinux mysqld[599]: InnoDB: about forcing recovery.
11月 16 13:16:44 archlinux mysqld[599]: 2022-11-16T05:16:44Z UTC - mysqld got signal 6 ;
11月 16 13:16:44 archlinux mysqld[599]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:16:44 archlinux mysqld[599]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:16:44 archlinux mysqld[599]: Thread pointer: 0x55817f2c5b30
11月 16 13:16:44 archlinux mysqld[599]: Attempting backtrace. You can use the following information to find out
11月 16 13:16:44 archlinux mysqld[599]: where mysqld died. If you see no messages after this, something went
11月 16 13:16:44 archlinux mysqld[599]: terribly wrong...
11月 16 13:16:44 archlinux mysqld[599]: stack_bottom = 7f34a7345c50 thread_stack 0x100000
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55817a5db312]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x558179c3167f]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x558179c3182f]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(my_abort()+0xe) [0x55817a5d70ae]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55817a77d3db]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(+0x1647f28) [0x55817a6b1f28]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55817a6c8999]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55817a7722ca]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(+0x15b21e2) [0x55817a61c1e2]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55817a46196b]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55817a5cc6bc]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(+0xc5beda) [0x558179cc5eda]
11月 16 13:16:44 archlinux mysqld[599]: /usr/bin/mysqld(+0x1943283) [0x55817a9ad283]
11月 16 13:16:44 archlinux mysqld[599]: /usr/lib/libc.so.6(+0x868fd) [0x7f34b589f8fd]
11月 16 13:16:44 archlinux mysqld[599]: /usr/lib/libc.so.6(+0x108a60) [0x7f34b5921a60]
11月 16 13:16:44 archlinux mysqld[599]: Trying to get some variables.
11月 16 13:16:44 archlinux mysqld[599]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:16:44 archlinux mysqld[599]: Query (0): Connection ID (thread ID): 1
11月 16 13:16:44 archlinux mysqld[599]: Status: NOT_KILLED
11月 16 13:16:44 archlinux mysqld[599]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:16:44 archlinux mysqld[599]: information that should help you find out what is causing the crash.
11月 16 13:16:44 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:16:44 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:16:44 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:16:44 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 1.
11月 16 13:16:44 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:16:44 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:16:44 archlinux mysqld[643]: 2022-11-16T05:16:44.943212Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:16:44 archlinux mysqld[643]: 2022-11-16T05:16:44.943256Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 643
11月 16 13:16:44 archlinux mysqld[643]: 2022-11-16T05:16:44.947172Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:16:44 archlinux mysqld[643]: 2022-11-16T05:16:44.983031Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:16:44 archlinux mysqld[643]: 2022-11-16T05:16:44.983051Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140647691740864
11月 16 13:16:44 archlinux mysqld[643]: InnoDB: We intentionally generate a memory trap.
11月 16 13:16:44 archlinux mysqld[643]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:16:44 archlinux mysqld[643]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:16:44 archlinux mysqld[643]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:16:44 archlinux mysqld[643]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:16:44 archlinux mysqld[643]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:16:44 archlinux mysqld[643]: InnoDB: about forcing recovery.
11月 16 13:16:44 archlinux mysqld[643]: 2022-11-16T05:16:44Z UTC - mysqld got signal 6 ;
11月 16 13:16:44 archlinux mysqld[643]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:16:44 archlinux mysqld[643]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:16:44 archlinux mysqld[643]: Thread pointer: 0x559b83ecdb30
11月 16 13:16:44 archlinux mysqld[643]: Attempting backtrace. You can use the following information to find out
11月 16 13:16:44 archlinux mysqld[643]: where mysqld died. If you see no messages after this, something went
11月 16 13:16:44 archlinux mysqld[643]: terribly wrong...
11月 16 13:16:44 archlinux mysqld[643]: stack_bottom = 7feb17b45c50 thread_stack 0x100000
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x559b7dcc1312]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x559b7d31767f]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x559b7d31782f]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(my_abort()+0xe) [0x559b7dcbd0ae]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x559b7de633db]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(+0x1647f28) [0x559b7dd97f28]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x559b7ddae999]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x559b7de582ca]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(+0x15b21e2) [0x559b7dd021e2]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x559b7db4796b]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x559b7dcb26bc]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(+0xc5beda) [0x559b7d3abeda]
11月 16 13:16:44 archlinux mysqld[643]: /usr/bin/mysqld(+0x1943283) [0x559b7e093283]
11月 16 13:16:44 archlinux mysqld[643]: /usr/lib/libc.so.6(+0x868fd) [0x7feb2609f8fd]
11月 16 13:16:44 archlinux mysqld[643]: /usr/lib/libc.so.6(+0x108a60) [0x7feb26121a60]
11月 16 13:16:44 archlinux mysqld[643]: Trying to get some variables.
11月 16 13:16:44 archlinux mysqld[643]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:16:44 archlinux mysqld[643]: Query (0): Connection ID (thread ID): 1
11月 16 13:16:44 archlinux mysqld[643]: Status: NOT_KILLED
11月 16 13:16:44 archlinux mysqld[643]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:16:44 archlinux mysqld[643]: information that should help you find out what is causing the crash.
11月 16 13:16:45 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:16:45 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:16:45 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:16:45 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 2.
11月 16 13:16:45 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:16:45 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:16:45 archlinux mysqld[712]: 2022-11-16T05:16:45.614819Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:16:45 archlinux mysqld[712]: 2022-11-16T05:16:45.614864Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 712
11月 16 13:16:45 archlinux mysqld[712]: 2022-11-16T05:16:45.618452Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:16:45 archlinux mysqld[712]: 2022-11-16T05:16:45.669705Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:16:45 archlinux mysqld[712]: 2022-11-16T05:16:45.669723Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140157982959296
11月 16 13:16:45 archlinux mysqld[712]: InnoDB: We intentionally generate a memory trap.
11月 16 13:16:45 archlinux mysqld[712]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:16:45 archlinux mysqld[712]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:16:45 archlinux mysqld[712]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:16:45 archlinux mysqld[712]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:16:45 archlinux mysqld[712]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:16:45 archlinux mysqld[712]: InnoDB: about forcing recovery.
11月 16 13:16:45 archlinux mysqld[712]: 2022-11-16T05:16:45Z UTC - mysqld got signal 6 ;
11月 16 13:16:45 archlinux mysqld[712]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:16:45 archlinux mysqld[712]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:16:45 archlinux mysqld[712]: Thread pointer: 0x55dcf1809b30
11月 16 13:16:45 archlinux mysqld[712]: Attempting backtrace. You can use the following information to find out
11月 16 13:16:45 archlinux mysqld[712]: where mysqld died. If you see no messages after this, something went
11月 16 13:16:45 archlinux mysqld[712]: terribly wrong...
11月 16 13:16:45 archlinux mysqld[712]: stack_bottom = 7f7912c95c50 thread_stack 0x100000
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55dcebb99312]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55dceb1ef67f]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55dceb1ef82f]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(my_abort()+0xe) [0x55dcebb950ae]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55dcebd3b3db]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(+0x1647f28) [0x55dcebc6ff28]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55dcebc86999]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55dcebd302ca]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(+0x15b21e2) [0x55dcebbda1e2]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55dceba1f96b]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55dcebb8a6bc]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(+0xc5beda) [0x55dceb283eda]
11月 16 13:16:45 archlinux mysqld[712]: /usr/bin/mysqld(+0x1943283) [0x55dcebf6b283]
11月 16 13:16:45 archlinux mysqld[712]: /usr/lib/libc.so.6(+0x868fd) [0x7f792129f8fd]
11月 16 13:16:45 archlinux mysqld[712]: /usr/lib/libc.so.6(+0x108a60) [0x7f7921321a60]
11月 16 13:16:45 archlinux mysqld[712]: Trying to get some variables.
11月 16 13:16:45 archlinux mysqld[712]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:16:45 archlinux mysqld[712]: Query (0): Connection ID (thread ID): 1
11月 16 13:16:45 archlinux mysqld[712]: Status: NOT_KILLED
11月 16 13:16:45 archlinux mysqld[712]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:16:45 archlinux mysqld[712]: information that should help you find out what is causing the crash.
11月 16 13:16:45 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:16:45 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:16:45 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:16:45 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 3.
11月 16 13:16:45 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:16:45 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:16:46 archlinux mysqld[841]: 2022-11-16T05:16:46.063451Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:16:46 archlinux mysqld[841]: 2022-11-16T05:16:46.063494Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 841
11月 16 13:16:46 archlinux mysqld[841]: 2022-11-16T05:16:46.067331Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:16:46 archlinux mysqld[841]: 2022-11-16T05:16:46.102627Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:16:46 archlinux mysqld[841]: 2022-11-16T05:16:46.102653Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140502518490816
11月 16 13:16:46 archlinux mysqld[841]: InnoDB: We intentionally generate a memory trap.
11月 16 13:16:46 archlinux mysqld[841]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:16:46 archlinux mysqld[841]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:16:46 archlinux mysqld[841]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:16:46 archlinux mysqld[841]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:16:46 archlinux mysqld[841]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:16:46 archlinux mysqld[841]: InnoDB: about forcing recovery.
11月 16 13:16:46 archlinux mysqld[841]: 2022-11-16T05:16:46Z UTC - mysqld got signal 6 ;
11月 16 13:16:46 archlinux mysqld[841]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:16:46 archlinux mysqld[841]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:16:46 archlinux mysqld[841]: Thread pointer: 0x557bc4651b30
11月 16 13:16:46 archlinux mysqld[841]: Attempting backtrace. You can use the following information to find out
11月 16 13:16:46 archlinux mysqld[841]: where mysqld died. If you see no messages after this, something went
11月 16 13:16:46 archlinux mysqld[841]: terribly wrong...
11月 16 13:16:46 archlinux mysqld[841]: stack_bottom = 7fc94ab45c50 thread_stack 0x100000
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x557bbee4f312]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x557bbe4a567f]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x557bbe4a582f]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(my_abort()+0xe) [0x557bbee4b0ae]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x557bbeff13db]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(+0x1647f28) [0x557bbef25f28]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x557bbef3c999]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x557bbefe62ca]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(+0x15b21e2) [0x557bbee901e2]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x557bbecd596b]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x557bbee406bc]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(+0xc5beda) [0x557bbe539eda]
11月 16 13:16:46 archlinux mysqld[841]: /usr/bin/mysqld(+0x1943283) [0x557bbf221283]
11月 16 13:16:46 archlinux mysqld[841]: /usr/lib/libc.so.6(+0x868fd) [0x7fc95909f8fd]
11月 16 13:16:46 archlinux mysqld[841]: /usr/lib/libc.so.6(+0x108a60) [0x7fc959121a60]
11月 16 13:16:46 archlinux mysqld[841]: Trying to get some variables.
11月 16 13:16:46 archlinux mysqld[841]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:16:46 archlinux mysqld[841]: Query (0): Connection ID (thread ID): 1
11月 16 13:16:46 archlinux mysqld[841]: Status: NOT_KILLED
11月 16 13:16:46 archlinux mysqld[841]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:16:46 archlinux mysqld[841]: information that should help you find out what is causing the crash.
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:16:46 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 4.
11月 16 13:16:46 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:16:46 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:16:46 archlinux mysqld[927]: 2022-11-16T05:16:46.426091Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:16:46 archlinux mysqld[927]: 2022-11-16T05:16:46.426135Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 927
11月 16 13:16:46 archlinux mysqld[927]: 2022-11-16T05:16:46.429726Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:16:46 archlinux mysqld[927]: 2022-11-16T05:16:46.465705Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:16:46 archlinux mysqld[927]: 2022-11-16T05:16:46.465729Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139817256576704
11月 16 13:16:46 archlinux mysqld[927]: InnoDB: We intentionally generate a memory trap.
11月 16 13:16:46 archlinux mysqld[927]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:16:46 archlinux mysqld[927]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:16:46 archlinux mysqld[927]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:16:46 archlinux mysqld[927]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:16:46 archlinux mysqld[927]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:16:46 archlinux mysqld[927]: InnoDB: about forcing recovery.
11月 16 13:16:46 archlinux mysqld[927]: 2022-11-16T05:16:46Z UTC - mysqld got signal 6 ;
11月 16 13:16:46 archlinux mysqld[927]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:16:46 archlinux mysqld[927]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:16:46 archlinux mysqld[927]: Thread pointer: 0x560090965b30
11月 16 13:16:46 archlinux mysqld[927]: Attempting backtrace. You can use the following information to find out
11月 16 13:16:46 archlinux mysqld[927]: where mysqld died. If you see no messages after this, something went
11月 16 13:16:46 archlinux mysqld[927]: terribly wrong...
11月 16 13:16:46 archlinux mysqld[927]: stack_bottom = 7f29bde95c50 thread_stack 0x100000
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x56008be56312]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x56008b4ac67f]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x56008b4ac82f]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(my_abort()+0xe) [0x56008be520ae]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x56008bff83db]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(+0x1647f28) [0x56008bf2cf28]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x56008bf43999]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x56008bfed2ca]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(+0x15b21e2) [0x56008be971e2]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x56008bcdc96b]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x56008be476bc]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(+0xc5beda) [0x56008b540eda]
11月 16 13:16:46 archlinux mysqld[927]: /usr/bin/mysqld(+0x1943283) [0x56008c228283]
11月 16 13:16:46 archlinux mysqld[927]: /usr/lib/libc.so.6(+0x868fd) [0x7f29cc49f8fd]
11月 16 13:16:46 archlinux mysqld[927]: /usr/lib/libc.so.6(+0x108a60) [0x7f29cc521a60]
11月 16 13:16:46 archlinux mysqld[927]: Trying to get some variables.
11月 16 13:16:46 archlinux mysqld[927]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:16:46 archlinux mysqld[927]: Query (0): Connection ID (thread ID): 1
11月 16 13:16:46 archlinux mysqld[927]: Status: NOT_KILLED
11月 16 13:16:46 archlinux mysqld[927]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:16:46 archlinux mysqld[927]: information that should help you find out what is causing the crash.
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:16:46 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
11月 16 13:16:46 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 13:16:46 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:16:46 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:20:14 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:20:14 archlinux mysqld[2589]: 2022-11-16T05:20:14.707570Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:20:14 archlinux mysqld[2589]: 2022-11-16T05:20:14.707612Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 2589
11月 16 13:20:14 archlinux mysqld[2589]: 2022-11-16T05:20:14.711064Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:20:14 archlinux mysqld[2589]: 2022-11-16T05:20:14.750498Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:20:14 archlinux mysqld[2589]: 2022-11-16T05:20:14.750516Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140489898620608
11月 16 13:20:14 archlinux mysqld[2589]: InnoDB: We intentionally generate a memory trap.
11月 16 13:20:14 archlinux mysqld[2589]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:20:14 archlinux mysqld[2589]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:20:14 archlinux mysqld[2589]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:20:14 archlinux mysqld[2589]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:20:14 archlinux mysqld[2589]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:20:14 archlinux mysqld[2589]: InnoDB: about forcing recovery.
11月 16 13:20:14 archlinux mysqld[2589]: 2022-11-16T05:20:14Z UTC - mysqld got signal 6 ;
11月 16 13:20:14 archlinux mysqld[2589]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:20:14 archlinux mysqld[2589]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:20:14 archlinux mysqld[2589]: Thread pointer: 0x55f74baeeb10
11月 16 13:20:14 archlinux mysqld[2589]: Attempting backtrace. You can use the following information to find out
11月 16 13:20:14 archlinux mysqld[2589]: where mysqld died. If you see no messages after this, something went
11月 16 13:20:14 archlinux mysqld[2589]: terribly wrong...
11月 16 13:20:14 archlinux mysqld[2589]: stack_bottom = 7fc65a806c50 thread_stack 0x100000
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55f747001312]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x55f74665767f]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x55f74665782f]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(my_abort()+0xe) [0x55f746ffd0ae]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55f7471a33db]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(+0x1647f28) [0x55f7470d7f28]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x55f7470ee999]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x55f7471982ca]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(+0x15b21e2) [0x55f7470421e2]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55f746e8796b]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55f746ff26bc]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(+0xc5beda) [0x55f7466ebeda]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/bin/mysqld(+0x1943283) [0x55f7473d3283]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/lib/libc.so.6(+0x868fd) [0x7fc668e9f8fd]
11月 16 13:20:14 archlinux mysqld[2589]: /usr/lib/libc.so.6(+0x108a60) [0x7fc668f21a60]
11月 16 13:20:14 archlinux mysqld[2589]: Trying to get some variables.
11月 16 13:20:14 archlinux mysqld[2589]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:20:14 archlinux mysqld[2589]: Query (0): Connection ID (thread ID): 1
11月 16 13:20:14 archlinux mysqld[2589]: Status: NOT_KILLED
11月 16 13:20:14 archlinux mysqld[2589]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:20:14 archlinux mysqld[2589]: information that should help you find out what is causing the crash.
11月 16 13:20:14 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:20:14 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:20:14 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:20:14 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 1.
11月 16 13:20:14 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:20:14 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:20:15 archlinux mysqld[2629]: 2022-11-16T05:20:15.135984Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:20:15 archlinux mysqld[2629]: 2022-11-16T05:20:15.136026Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 2629
11月 16 13:20:15 archlinux mysqld[2629]: 2022-11-16T05:20:15.139733Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:20:15 archlinux mysqld[2629]: 2022-11-16T05:20:15.178770Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:20:15 archlinux mysqld[2629]: 2022-11-16T05:20:15.178793Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139977714325184
11月 16 13:20:15 archlinux mysqld[2629]: InnoDB: We intentionally generate a memory trap.
11月 16 13:20:15 archlinux mysqld[2629]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:20:15 archlinux mysqld[2629]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:20:15 archlinux mysqld[2629]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:20:15 archlinux mysqld[2629]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:20:15 archlinux mysqld[2629]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:20:15 archlinux mysqld[2629]: InnoDB: about forcing recovery.
11月 16 13:20:15 archlinux mysqld[2629]: 2022-11-16T05:20:15Z UTC - mysqld got signal 6 ;
11月 16 13:20:15 archlinux mysqld[2629]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:20:15 archlinux mysqld[2629]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:20:15 archlinux mysqld[2629]: Thread pointer: 0x556736491b10
11月 16 13:20:15 archlinux mysqld[2629]: Attempting backtrace. You can use the following information to find out
11月 16 13:20:15 archlinux mysqld[2629]: where mysqld died. If you see no messages after this, something went
11月 16 13:20:15 archlinux mysqld[2629]: terribly wrong...
11月 16 13:20:15 archlinux mysqld[2629]: stack_bottom = 7f4f19f04c50 thread_stack 0x100000
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x55673138c312]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5567309e267f]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5567309e282f]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(my_abort()+0xe) [0x5567313880ae]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x55673152e3db]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(+0x1647f28) [0x556731462f28]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x556731479999]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5567315232ca]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(+0x15b21e2) [0x5567313cd1e2]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x55673121296b]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x55673137d6bc]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(+0xc5beda) [0x556730a76eda]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/bin/mysqld(+0x1943283) [0x55673175e283]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/lib/libc.so.6(+0x868fd) [0x7f4f2849f8fd]
11月 16 13:20:15 archlinux mysqld[2629]: /usr/lib/libc.so.6(+0x108a60) [0x7f4f28521a60]
11月 16 13:20:15 archlinux mysqld[2629]: Trying to get some variables.
11月 16 13:20:15 archlinux mysqld[2629]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:20:15 archlinux mysqld[2629]: Query (0): Connection ID (thread ID): 1
11月 16 13:20:15 archlinux mysqld[2629]: Status: NOT_KILLED
11月 16 13:20:15 archlinux mysqld[2629]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:20:15 archlinux mysqld[2629]: information that should help you find out what is causing the crash.
11月 16 13:20:15 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:20:15 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:20:15 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:20:15 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 2.
11月 16 13:20:15 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:20:15 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:20:15 archlinux mysqld[2666]: 2022-11-16T05:20:15.666922Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:20:15 archlinux mysqld[2666]: 2022-11-16T05:20:15.666964Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 2666
11月 16 13:20:15 archlinux mysqld[2666]: 2022-11-16T05:20:15.670384Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:20:15 archlinux mysqld[2666]: 2022-11-16T05:20:15.709547Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:20:15 archlinux mysqld[2666]: 2022-11-16T05:20:15.709571Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140268009850560
11月 16 13:20:15 archlinux mysqld[2666]: InnoDB: We intentionally generate a memory trap.
11月 16 13:20:15 archlinux mysqld[2666]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:20:15 archlinux mysqld[2666]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:20:15 archlinux mysqld[2666]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:20:15 archlinux mysqld[2666]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:20:15 archlinux mysqld[2666]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:20:15 archlinux mysqld[2666]: InnoDB: about forcing recovery.
11月 16 13:20:15 archlinux mysqld[2666]: 2022-11-16T05:20:15Z UTC - mysqld got signal 6 ;
11月 16 13:20:15 archlinux mysqld[2666]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:20:15 archlinux mysqld[2666]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:20:15 archlinux mysqld[2666]: Thread pointer: 0x559b808f2b10
11月 16 13:20:15 archlinux mysqld[2666]: Attempting backtrace. You can use the following information to find out
11月 16 13:20:15 archlinux mysqld[2666]: where mysqld died. If you see no messages after this, something went
11月 16 13:20:15 archlinux mysqld[2666]: terribly wrong...
11月 16 13:20:15 archlinux mysqld[2666]: stack_bottom = 7f92b0e67c50 thread_stack 0x100000
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x559b7bfc3312]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x559b7b61967f]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x559b7b61982f]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(my_abort()+0xe) [0x559b7bfbf0ae]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x559b7c1653db]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(+0x1647f28) [0x559b7c099f28]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x559b7c0b0999]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x559b7c15a2ca]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(+0x15b21e2) [0x559b7c0041e2]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x559b7be4996b]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x559b7bfb46bc]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(+0xc5beda) [0x559b7b6adeda]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/bin/mysqld(+0x1943283) [0x559b7c395283]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/lib/libc.so.6(+0x868fd) [0x7f92bf49f8fd]
11月 16 13:20:15 archlinux mysqld[2666]: /usr/lib/libc.so.6(+0x108a60) [0x7f92bf521a60]
11月 16 13:20:15 archlinux mysqld[2666]: Trying to get some variables.
11月 16 13:20:15 archlinux mysqld[2666]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:20:15 archlinux mysqld[2666]: Query (0): Connection ID (thread ID): 1
11月 16 13:20:15 archlinux mysqld[2666]: Status: NOT_KILLED
11月 16 13:20:15 archlinux mysqld[2666]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:20:15 archlinux mysqld[2666]: information that should help you find out what is causing the crash.
11月 16 13:20:15 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:20:15 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:20:15 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:20:15 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 3.
11月 16 13:20:15 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:20:15 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:20:16 archlinux mysqld[2704]: 2022-11-16T05:20:16.164595Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:20:16 archlinux mysqld[2704]: 2022-11-16T05:20:16.164636Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 2704
11月 16 13:20:16 archlinux mysqld[2704]: 2022-11-16T05:20:16.168248Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:20:16 archlinux mysqld[2704]: 2022-11-16T05:20:16.206882Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:20:16 archlinux mysqld[2704]: 2022-11-16T05:20:16.206905Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 139663114528448
11月 16 13:20:16 archlinux mysqld[2704]: InnoDB: We intentionally generate a memory trap.
11月 16 13:20:16 archlinux mysqld[2704]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:20:16 archlinux mysqld[2704]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:20:16 archlinux mysqld[2704]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:20:16 archlinux mysqld[2704]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:20:16 archlinux mysqld[2704]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:20:16 archlinux mysqld[2704]: InnoDB: about forcing recovery.
11月 16 13:20:16 archlinux mysqld[2704]: 2022-11-16T05:20:16Z UTC - mysqld got signal 6 ;
11月 16 13:20:16 archlinux mysqld[2704]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:20:16 archlinux mysqld[2704]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:20:16 archlinux mysqld[2704]: Thread pointer: 0x559f2e0efb10
11月 16 13:20:16 archlinux mysqld[2704]: Attempting backtrace. You can use the following information to find out
11月 16 13:20:16 archlinux mysqld[2704]: where mysqld died. If you see no messages after this, something went
11月 16 13:20:16 archlinux mysqld[2704]: terribly wrong...
11月 16 13:20:16 archlinux mysqld[2704]: stack_bottom = 7f05da545c50 thread_stack 0x100000
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x559f287f8312]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x559f27e4e67f]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x559f27e4e82f]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(my_abort()+0xe) [0x559f287f40ae]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x559f2899a3db]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(+0x1647f28) [0x559f288cef28]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x559f288e5999]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x559f2898f2ca]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(+0x15b21e2) [0x559f288391e2]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x559f2867e96b]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x559f287e96bc]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(+0xc5beda) [0x559f27ee2eda]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/bin/mysqld(+0x1943283) [0x559f28bca283]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/lib/libc.so.6(+0x868fd) [0x7f05e8a9f8fd]
11月 16 13:20:16 archlinux mysqld[2704]: /usr/lib/libc.so.6(+0x108a60) [0x7f05e8b21a60]
11月 16 13:20:16 archlinux mysqld[2704]: Trying to get some variables.
11月 16 13:20:16 archlinux mysqld[2704]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:20:16 archlinux mysqld[2704]: Query (0): Connection ID (thread ID): 1
11月 16 13:20:16 archlinux mysqld[2704]: Status: NOT_KILLED
11月 16 13:20:16 archlinux mysqld[2704]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:20:16 archlinux mysqld[2704]: information that should help you find out what is causing the crash.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:20:16 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 4.
11月 16 13:20:16 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:20:16 archlinux systemd[1]: Starting MySQL Server...
11月 16 13:20:16 archlinux mysqld[2741]: 2022-11-16T05:20:16.676530Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
11月 16 13:20:16 archlinux mysqld[2741]: 2022-11-16T05:20:16.676573Z 0 [System] [MY-010116] [Server] /usr/bin/mysqld (mysqld 8.0.31) starting as process 2741
11月 16 13:20:16 archlinux mysqld[2741]: 2022-11-16T05:20:16.680009Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
11月 16 13:20:16 archlinux mysqld[2741]: 2022-11-16T05:20:16.718967Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
11月 16 13:20:16 archlinux mysqld[2741]: 2022-11-16T05:20:16.718990Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3709:err == DB_SUCCESS thread 140320692594368
11月 16 13:20:16 archlinux mysqld[2741]: InnoDB: We intentionally generate a memory trap.
11月 16 13:20:16 archlinux mysqld[2741]: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
11月 16 13:20:16 archlinux mysqld[2741]: InnoDB: If you get repeated assertion failures or crashes, even
11月 16 13:20:16 archlinux mysqld[2741]: InnoDB: immediately after the mysqld startup, there may be
11月 16 13:20:16 archlinux mysqld[2741]: InnoDB: corruption in the InnoDB tablespace. Please refer to
11月 16 13:20:16 archlinux mysqld[2741]: InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
11月 16 13:20:16 archlinux mysqld[2741]: InnoDB: about forcing recovery.
11月 16 13:20:16 archlinux mysqld[2741]: 2022-11-16T05:20:16Z UTC - mysqld got signal 6 ;
11月 16 13:20:16 archlinux mysqld[2741]: Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
11月 16 13:20:16 archlinux mysqld[2741]: BuildID[sha1]=a1d09b045d25585336b087e480215ac7f317ae79
11月 16 13:20:16 archlinux mysqld[2741]: Thread pointer: 0x5596dc07ab10
11月 16 13:20:16 archlinux mysqld[2741]: Attempting backtrace. You can use the following information to find out
11月 16 13:20:16 archlinux mysqld[2741]: where mysqld died. If you see no messages after this, something went
11月 16 13:20:16 archlinux mysqld[2741]: terribly wrong...
11月 16 13:20:16 archlinux mysqld[2741]: stack_bottom = 7f9ef5095c50 thread_stack 0x100000
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x42) [0x5596d7226312]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(print_fatal_signal(int)+0x2bf) [0x5596d687c67f]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(my_server_abort()+0x6f) [0x5596d687c82f]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(my_abort()+0xe) [0x5596d72220ae]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x17b) [0x5596d73c83db]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(+0x1647f28) [0x5596d72fcf28]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0xee9) [0x5596d7313999]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(srv_start(bool)+0xeea) [0x5596d73bd2ca]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(+0x15b21e2) [0x5596d72671e2]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0xdb) [0x5596d70ac96b]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x23c) [0x5596d72176bc]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(+0xc5beda) [0x5596d6910eda]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/bin/mysqld(+0x1943283) [0x5596d75f8283]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/lib/libc.so.6(+0x868fd) [0x7f9f0369f8fd]
11月 16 13:20:16 archlinux mysqld[2741]: /usr/lib/libc.so.6(+0x108a60) [0x7f9f03721a60]
11月 16 13:20:16 archlinux mysqld[2741]: Trying to get some variables.
11月 16 13:20:16 archlinux mysqld[2741]: Some pointers may be invalid and cause the dump to abort.
11月 16 13:20:16 archlinux mysqld[2741]: Query (0): Connection ID (thread ID): 1
11月 16 13:20:16 archlinux mysqld[2741]: Status: NOT_KILLED
11月 16 13:20:16 archlinux mysqld[2741]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
11月 16 13:20:16 archlinux mysqld[2741]: information that should help you find out what is causing the crash.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:20:16 archlinux systemd[1]: Failed to start MySQL Server.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Scheduled restart job, restart counter is at 5.
11月 16 13:20:16 archlinux systemd[1]: Stopped MySQL Server.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Start request repeated too quickly.
11月 16 13:20:16 archlinux systemd[1]: mysqld.service: Failed with result 'exit-code'.
11月 16 13:20:16 archlinux systemd[1]: Failed to start MySQL Server.

依云 · 2022-11-16 17:41:59

这样才对嘛。
猜测是数据库的日志损坏了。

fengzheng081212 · 2022-11-16 18:23:52

依云说：

那些 .old 的空文件直接删掉就好了。

谢谢，可以了！

卑以自牧 · 2022-11-16 22:00:35

起初my.cnf中加了innodb_force_recovery=6就能启动了，改回来还是不能启动，然后删了ibdata1，就起不来了，后面全给删了，重新初始化了

Arch Linux

#1 2022-11-16 07:27:55

转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#2 2022-11-16 09:22:54

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#3 2022-11-16 11:08:28

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#4 2022-11-16 12:13:19

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#5 2022-11-16 12:29:44

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#6 2022-11-16 13:38:12

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#7 2022-11-16 13:51:42

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#8 2022-11-16 14:31:12

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#9 2022-11-16 17:41:59

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#10 2022-11-16 18:23:52

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

#11 2022-11-16 22:00:35

Re: 转btrfs后，好像有文件丢失了，更新一直报错，帮忙看看怎么解决

页脚