percona 5.7.16 bug-问答-阿里云开发者社区-阿里云

开发者社区> 问答> 正文
阿里云
为了无法计算的价值
打开APP
阿里云APP内打开

percona 5.7.16 bug

2017-03-01 10:21:59 3732 1

2017-03-01T02:06:28.098477Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.17-11-log) starting as process 117548 ...
2017-03-01T02:06:28.101658Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2017-03-01T02:06:28.101678Z 0 [Warning] InnoDB: Using innodb_file_format_max is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2017-03-01T02:06:28.101722Z 0 [Note] InnoDB: PUNCH HOLE support available
2017-03-01T02:06:28.101728Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-03-01T02:06:28.101730Z 0 [Note] InnoDB: Uses event mutexes
2017-03-01T02:06:28.101733Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-03-01T02:06:28.101736Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2017-03-01T02:06:28.101738Z 0 [Note] InnoDB: Using Linux native AIO
2017-03-01T02:06:28.102704Z 0 [Note] InnoDB: Number of pools: 1
2017-03-01T02:06:28.102791Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-03-01T02:06:28.105548Z 0 [Note] InnoDB: Initializing buffer pool, total size = 200G, instances = 16, chunk size = 128M
2017-03-01T02:06:28.105560Z 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_INTERLEAVE
2017-03-01T02:06:33.567127Z 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_DEFAULT
2017-03-01T02:06:33.567156Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-03-01T02:06:34.965669Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2017-03-01T02:06:34.977998Z 0 [Note] InnoDB: Recovering partial pages from the parallel doublewrite buffer at /var/lib/mysql/xb_doublewrite
2017-03-01T02:06:34.980687Z 0 [Note] InnoDB: Opened 3 undo tablespaces
2017-03-01T02:06:34.980696Z 0 [Note] InnoDB: 3 undo tablespaces made active
2017-03-01T02:06:34.980874Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-01T02:06:35.909477Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 43724088852
2017-03-01T02:06:36.036472Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43729331712
2017-03-01T02:06:36.197614Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43734574592
2017-03-01T02:06:36.338243Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43739817472
2017-03-01T02:06:36.503259Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43745060352
2017-03-01T02:06:37.542996Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43726710272
2017-03-01T02:06:37.728222Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43731953152
2017-03-01T02:06:37.875146Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43737196032
2017-03-01T02:06:38.053155Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43742438912
2017-03-01T02:06:38.206974Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43747681792
2017-03-01T02:06:38.372973Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43752924672
2017-03-01T02:06:38.544097Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43758167552
2017-03-01T02:06:38.689065Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43763410432
2017-03-01T02:06:38.822492Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 43767254868
2017-03-01T02:06:38.822957Z 0 [ERROR] [FATAL] InnoDB: Missing MLOG_FILE_NAME or MLOG_FILE_DELETE for redo log record 41 (page 4278124286:4278124286) at 43767234886.
2017-03-01 10:06:38 0x7ff88e714840 InnoDB: Assertion failure in thread 140705518405696 in file ut0ut.cc line 917
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/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:06:38 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=8388608
read_buffer_size=16777216
max_used_connections=0
max_threads=2001
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 98340377 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xeff3ab]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0x79ff11]
/lib64/libpthread.so.0(+0xf100)[0x7ff88e2f9100]
/lib64/libc.so.6(gsignal+0x37)[0x7ff88c4835f7]
/lib64/libc.so.6(abort+0x148)[0x7ff88c484ce8]
/usr/sbin/mysqld[0x76e15c]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0xfd)[0x11a093d]
/usr/sbin/mysqld[0x106e7ff]
/usr/sbin/mysqld(_Z18recv_parse_log_recP9mlog_id_tPhS1_PmS2_bPS1_+0xe2)[0x1071ad2]
/usr/sbin/mysqld[0x107290e]
/usr/sbin/mysqld[0x1073259]
/usr/sbin/mysqld(_Z35recv_recovery_from_checkpoint_startm+0x1f52)[0x1075512]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x45af)[0x114cf1f]
/usr/sbin/mysqld[0x10067f0]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x51)[0x801e61]
/usr/sbin/mysqld[0xcf5145]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x610)[0xcfc5d0]
/usr/sbin/mysqld[0x7985cb]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x656)[0x799bc6]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7ff88c46fb15]
/usr/sbin/mysqld[0x78f505]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

取消 提交回答
全部回答(1)
  • 韩逸
    2019-07-17 20:51:25

    2017-03-01T02:06:38.822957Z 0 [ERROR] [FATAL] InnoDB: Missing MLOG_FILE_NAME or MLOG_FILE_DELETE for redo log record 41 (page 4278124286:4278124286) at 43767234886.
    从这行可以看出,应该是在做奔溃恢复的时候解析到错误的redolog了。检查一下磁盘有没有问题。

    0 0
相关问答

1

回答

函数计算ai 环境怎么部署上去的,光torch就1.7G了函数计算大小限制好像只有500M

2022-06-17 10:31:23 372浏览量 回答数 1

1

回答

iReport解决导出PDF解决不支持中文这个bug怎么解决?

2021-10-22 15:11:36 299浏览量 回答数 1

1

回答

在AOS 使用 DaoBuilderConsole时,启动报错 。数据选择的是?报错

2020-06-14 14:40:22 322浏览量 回答数 1

1

回答

perconna xtrabackup 全备mysql5.5还原到5.6上报错?报错

2020-06-08 17:38:22 265浏览量 回答数 1

0

回答

使用Brew安装的PostgreSQL 11.5,在添加pg_trgm后还是没法搜索中文

2019-10-04 22:26:49 474浏览量 回答数 0

2

回答

镜像复制 从华东1复制到华东2 问题:1、后台看不到复制镜像; 2、镜像大小是30G,从华东1复制到

2019-03-22 12:24:00 668浏览量 回答数 2

1

回答

[@wangccsy][¥20]mysql优化时,怎么避免using filesort、using temporary?

2018-12-07 11:49:11 1778浏览量 回答数 1

1

回答

linux 编译php 的时候 ./buildconf --force 什么作用?

2016-06-13 15:38:08 3255浏览量 回答数 1

1

回答

DWORD_PTR是什么类型?

2016-06-07 21:08:51 2225浏览量 回答数 1

2

回答

邮箱搜索有BUG

2015-01-15 11:06:31 3600浏览量 回答数 2
+关注
18
文章
2
问答
问答排行榜
最热
最新
相关电子书
更多
低代码开发师(初级)实战教程
立即下载
阿里巴巴DevOps 最佳实践手册
立即下载
冬季实战营第三期:MySQL数据库进阶实战
立即下载