01:36:24 UTC - mysqld got signal 11

我在关闭数据库时,使用kill -9,后来启动时,直接报错:

200322 09:36:24 mysqld_safe Starting mysqld daemon with databases from /data01/3308/data

2020-03-22 09:36:24 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2020-03-22 09:36:24 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.25-log) starting as process 3935 ...

2020-03-22 09:36:24 3935 [Note] Plugin 'FEDERATED' is disabled.

01:36:24 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.

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed,

something is definitely wrong and this may fail.

 

key_buffer_size=33554432

read_buffer_size=4194304

max_used_connections=0

max_threads=100

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 = 648446 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

 

Thread pointer: 0x7ffe19b73a60

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 = 7ffe19b76d80 thread_stack 0x40000

/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x90cb35]

/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x3d8)[0x673c48]

/lib64/libpthread.so.0(+0xf6d0)[0x7fc567a8c6d0]

/usr/local/mysql/bin/mysqld(_Z18ha_resolve_by_nameP3THDPK19st_mysql_lex_stringb+0x70)[0x590700]

/usr/local/mysql/bin/mysqld(_Z14open_table_defP3THDP11TABLE_SHAREj+0x2e0d)[0x78e8bd]

/usr/local/mysql/bin/mysqld(_Z15get_table_shareP3THDP10TABLE_LISTPKcjjPij+0x189)[0x6a2db9]

/usr/local/mysql/bin/mysqld[0x6a4b3c]

/usr/local/mysql/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x846)[0x6ab7d6]

/usr/local/mysql/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0xbbc)[0x6aed1c]

/usr/local/mysql/bin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x4e)[0x6aef7e]

/usr/local/mysql/bin/mysqld(_Z11plugin_initPiPPci+0x1015)[0x702fc5]

/usr/local/mysql/bin/mysqld[0x5858d0]

/usr/local/mysql/bin/mysqld(_Z11mysqld_mainiPPc+0x345)[0x586765]

/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fc56666d445]

/usr/local/mysql/bin/mysqld(__gxx_personality_v0+0x2e9)[0x57a969]

 

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): 0

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.

200322 09:36:24 mysqld_safe mysqld from pid file /data01/3308/tmp/mysql.pid ended

发布了577 篇原创文章 · 获赞 90 · 访问量 53万+

猜你喜欢

转载自blog.csdn.net/w892824196/article/details/105022837
UTC