「已注销」 2020-10-13 01:35 采纳率: 0%
浏览 317

宝塔centos7安装的mysql8.0启动错误???

这个是报错

2020-10-13T01:22:30.906294Z 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.
2020-10-13T01:22:30.906381Z 0 [System] [MY-010116] [Server] /www/server/mysql/bin/mysqld (mysqld 8.0.20) starting as process 5577
2020-10-13T01:22:30.916508Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-13T01:22:31.026536Z 1 [ERROR] [MY-012671] [InnoDB] Encryption algorithm support missing: N
2020-10-13T01:22:31.026624Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0recv.cc:3511:err == DB_SUCCESS thread 47706341713664
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
01:22:31 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x72147a0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 2b637f8d1c00 thread_stack 0x40000
/www/server/mysql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x1e658ee]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x2f3) [0xf19c93]
/lib64/libpthread.so.0(+0xf630) [0x2b6364b2c630]
/lib64/libc.so.6(gsignal+0x37) [0x2b6366705387]
/lib64/libc.so.6(abort+0x148) [0x2b6366706a78]
/www/server/mysql/bin/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x2cf) [0x211ffbf]
/www/server/mysql/bin/mysqld() [0x1fda428]
/www/server/mysql/bin/mysqld(recv_recovery_from_checkpoint_start(log_t&, unsigned long)+0x58d) [0x1fe3a7d]
/www/server/mysql/bin/mysqld(srv_start(bool)+0x1e1d) [0x20cbf8d]
/www/server/mysql/bin/mysqld() [0x1f43636]
/www/server/mysql/bin/mysqld(dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int)+0x81) [0x1bcbf11]
/www/server/mysql/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+0x564) [0x1e31f84]
/www/server/mysql/bin/mysqld() [0xfd69b6]
/www/server/mysql/bin/mysqld() [0x237a1c9]
/lib64/libpthread.so.0(+0x7ea5) [0x2b6364b24ea5]
/lib64/libc.so.6(clone+0x6d) [0x2b63667cd8dd]

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

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

1条回答 默认 最新

  • 憧憬blog 2023-03-15 00:49
    关注

    根据报错,看起来是「Encryption algorithm support missing」这个错误导致了 MySQL 服务器启动失败。MySQL 8.0 版本默认启用了「InnoDB Tablespaces」加密特性,但是服务器缺少了入口支持该加密算法,因此导致 InnoDB 初始化失败和服务器异常退出。

    解决方案可以尝试关闭 InnoDB Tablespaces 加密特性,具体可以在 MySQL 配置文件中添加以下参数:

    innodb_encrypt_tables=OFF
    

    或者在启动 MySQL 命令中添加 --innodb_encrypt_tables=OFF 参数,重新启动 MySQL 服务即可。

    评论

报告相同问题?

悬赏问题

  • ¥20 腾讯企业邮箱邮件可以恢复么
  • ¥15 有人知道怎么将自己的迁移策略布到edgecloudsim上使用吗?
  • ¥15 错误 LNK2001 无法解析的外部符号
  • ¥50 安装pyaudiokits失败
  • ¥15 计组这些题应该咋做呀
  • ¥60 更换迈创SOL6M4AE卡的时候,驱动要重新装才能使用,怎么解决?
  • ¥15 让node服务器有自动加载文件的功能
  • ¥15 jmeter脚本回放有的是对的有的是错的
  • ¥15 r语言蛋白组学相关问题
  • ¥15 Python时间序列如何拟合疏系数模型