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

开发者社区> cell_liu> 正文

percona 5.7.16 bug

2017-03-01 10:21:59 3328 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
相关问答

17

回答

【大咖问答】对话PostgreSQL 中国社区发起人之一,阿里云数据库高级专家 德哥

阿里ACE 彭飞 2019-07-10 09:36:10 971236浏览量 回答数 17

162

回答

惊喜翻倍:免费ECS+免费环境配置~!(ECS免费体验6个月活动3月31日结束)

豆妹 2014-10-29 17:52:21 223029浏览量 回答数 162

8

回答

OceanBase 使用动画(持续更新)

mq4096 2019-02-20 17:16:36 333892浏览量 回答数 8

18

回答

阿里云开放端口权限

xcxx 2016-07-20 15:03:33 643177浏览量 回答数 18

38

回答

安全组详解,新手必看教程

我的中国 2017-11-30 15:23:46 256885浏览量 回答数 38

294

回答

Linux Bash严重漏洞修复紧急通知(已全部给出最终修复方案)

qilu 2014-09-25 13:26:50 431630浏览量 回答数 294

249

回答

阿里云LNAMP(Linux + Nginx + Apache + MySQL + PHP)环境一键安装脚本

云代维 2014-02-14 15:26:06 302621浏览量 回答数 249

40

回答

阿里云ecs从购买到环境搭建和建站!!(phpstudy一件包)

梦丫头 2014-07-29 20:51:49 162120浏览量 回答数 40

24

回答

【精品问答】python技术1000问(1)

问问小秘 2019-11-15 13:25:00 471477浏览量 回答数 24

2

回答

区域选择帮助

fanyue88888 2012-12-07 15:54:30 204020浏览量 回答数 2
+关注
18
文章
2
问答
推荐问答
相关电子书
更多
文娱运维技术
立即下载
《SaaS模式云原生数据仓库应用场景实践》
立即下载
《看见新力量:二》电子书
立即下载