MySQL自动重启如何处理
发布时间：2022-02-12 14:57:05 所属栏目：MySql教程 来源：互联网
导读：本篇文章为大家展示了MySQL自动重启如何解决，内容简明扼要并且容易理解，绝对能使你眼前一亮，通过这篇文章的详细介绍希望你能有所收获。 前言 报错信息如下： 2019-07-24T01:14:53.769512Z 0 [Note] Executing SELECT * FROM INFORMATION_SCHEMA.TABLES; t
|
本篇文章为大家展示了MySQL自动重启如何解决，内容简明扼要并且容易理解，绝对能使你眼前一亮，通过这篇文章的详细介绍希望你能有所收获。 前言 报错信息如下： 2019-07-24T01:14:53.769512Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check. 2019-07-24T01:14:53.769516Z 0 [Note] Beginning of list of non-natively partitioned tables 01:14:53 UTC - mysqld got signal 11 ; 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=33554432 read_buffer_size=8388608 max_used_connections=0 max_threads=501 thread_count=4 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4478400 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f486900e000 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 = 7f4846172820 thread_stack 0x80000 /usr/local/mysql5.7/bin/mysqld(my_print_stacktrace+0x2c)[0xed481c] /usr/local/mysql5.7/bin/mysqld(handle_fatal_signal+0x461)[0x7a15a1] /lib64/libpthread.so.0(+0xf7e0)[0x7f498697c7e0] /usr/local/mysql5.7/bin/mysqld(_ZN12ha_federated7rnd_posEPhS0_+0x2f)[0x12bcc3f] /usr/local/mysql5.7/bin/mysqld(_ZN7handler10ha_rnd_posEPhS0_+0x172)[0x804a12] /usr/local/mysql5.7/bin/mysqld(_ZN14Rows_log_event24do_index_scan_and_updateEPK14Relay_log_info+0x1e3)[0xe50e23] /usr/local/mysql5.7/bin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0x716)[0xe50196] /usr/local/mysql5.7/bin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x6e)[0xe48fde] /usr/local/mysql5.7/bin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x1f0)[0xe8d6f0] /usr/local/mysql5.7/bin/mysqld(handle_slave_sql+0x163d)[0xe9a0fd] /usr/local/mysql5.7/bin/mysqld(pfs_spawn_thread+0x1b4)[0x1209414] /lib64/libpthread.so.0(+0x7aa1)[0x7f4986974aa1] /lib64/libc.so.6(clone+0x6d)[0x7f4984c6bc4d] 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): 2 Status: NOT_KILLED 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. 初探过程 之前出现过类似的情况时，是因为内存不足，因日志中也有对应的提示： key_buffer_size=33554432 read_buffer_size=8388608 max_used_connections=0 max_threads=501 thread_count=4 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4478400 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 此测试环境物理内存确实不大，且剩余内存也不足，而且是作为另一个测试环境的从库，内存分配的也少。 （编辑：91站长网） 【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容! |
