Wit debug version I get crash when try to run FLUSH LOGS command:
mysqld: /home/sveta/src/percona-server/sql/sql_error.cc:380: void Diagnostics_area::set_ok_status(ulonglong, ulonglong, const char*): Assertion `! is_set()' failed.
12:14:55 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=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=152
thread_count=3
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61221 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fa158000950
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 = 7fa1a0605e18 thread_stack 0x40000
/home/sveta/build/ps-5.7/bin/mysqld(my_print_stacktrace+0x47)[0x197c087]
/home/sveta/build/ps-5.7/bin/mysqld(handle_fatal_signal+0x440)[0xf06407]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fa1a62b4390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fa1a566d428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fa1a566f02a]
/lib/x86_64-linux-gnu/libc.so.6(+0x2dbd7)[0x7fa1a5665bd7]
/lib/x86_64-linux-gnu/libc.so.6(+0x2dc82)[0x7fa1a5665c82]
/home/sveta/build/ps-5.7/bin/mysqld(_ZN16Diagnostics_area13set_ok_statusEyyPKc+0x75)[0x15cbb23]
/home/sveta/build/ps-5.7/bin/mysqld(_Z5my_okP3THDyyPKc+0x4e)[0xf1b7df]
/home/sveta/build/ps-5.7/bin/mysqld(_Z21mysql_execute_commandP3THDb+0x54cf)[0x161ed32]
/home/sveta/build/ps-5.7/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x720)[0x1622db1]
/home/sveta/build/ps-5.7/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xc41)[0x1617008]
/home/sveta/build/ps-5.7/bin/mysqld(_Z10do_commandP3THD+0x59e)[0x1615e8f]
/home/sveta/build/ps-5.7/bin/mysqld(handle_connection+0x2b1)[0x17655f6]
/home/sveta/build/ps-5.7/bin/mysqld(pfs_spawn_thread+0x173)[0x1e58e67]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fa1a62aa6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa1a573e82d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa1580043d0): flush logs
Connection ID (thread ID): 5
Status: NOT_KILLED
Wit debug version I get crash when try to run FLUSH LOGS command:
mysqld: /home/sveta/ src/percona- server/ sql/sql_ error.cc: 380: void Diagnostics_ area::set_ ok_status( ulonglong, ulonglong, const char*): Assertion `! is_set()' failed. bugs.percona. com/
12:14:55 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://
key_buffer_ size=1048576 size=131072 connections= 1 size)*max_ threads = 61221 K bytes of memory
read_buffer_
max_used_
max_threads=152
thread_count=3
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fa158000950 build/ps- 5.7/bin/ mysqld( my_print_ stacktrace+ 0x47)[0x197c087 ] build/ps- 5.7/bin/ mysqld( handle_ fatal_signal+ 0x440)[ 0xf06407] 64-linux- gnu/libpthread. so.0(+0x11390) [0x7fa1a62b4390 ] 64-linux- gnu/libc. so.6(gsignal+ 0x38)[0x7fa1a56 6d428] 64-linux- gnu/libc. so.6(abort+ 0x16a)[ 0x7fa1a566f02a] 64-linux- gnu/libc. so.6(+0x2dbd7) [0x7fa1a5665bd7 ] 64-linux- gnu/libc. so.6(+0x2dc82) [0x7fa1a5665c82 ] build/ps- 5.7/bin/ mysqld( _ZN16Diagnostic s_area13set_ ok_statusEyyPKc +0x75)[ 0x15cbb23] build/ps- 5.7/bin/ mysqld( _Z5my_okP3THDyy PKc+0x4e) [0xf1b7df] build/ps- 5.7/bin/ mysqld( _Z21mysql_ execute_ commandP3THDb+ 0x54cf) [0x161ed32] build/ps- 5.7/bin/ mysqld( _Z11mysql_ parseP3THDP12Pa rser_state+ 0x720)[ 0x1622db1] build/ps- 5.7/bin/ mysqld( _Z16dispatch_ commandP3THDPK8 COM_DATA19enum_ server_ command+ 0xc41)[ 0x1617008] build/ps- 5.7/bin/ mysqld( _Z10do_ commandP3THD+ 0x59e)[ 0x1615e8f] build/ps- 5.7/bin/ mysqld( handle_ connection+ 0x2b1)[ 0x17655f6] build/ps- 5.7/bin/ mysqld( pfs_spawn_ thread+ 0x173)[ 0x1e58e67] 64-linux- gnu/libpthread. so.0(+0x76ba) [0x7fa1a62aa6ba ] 64-linux- gnu/libc. so.6(clone+ 0x6d)[0x7fa1a57 3e82d]
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 = 7fa1a0605e18 thread_stack 0x40000
/home/sveta/
/home/sveta/
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa1580043d0): flush logs
Connection ID (thread ID): 5
Status: NOT_KILLED