percona-server-5.7.19-17 crash

Bug #1739772 reported by jianhaiqing on 2017-12-22
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Incomplete
Undecided
Unassigned

Bug Description

1. the following part is crash information.
04:42:11 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=67108864
read_buffer_size=131072
max_used_connections=225
max_threads=2001
thread_count=220
connection_count=219
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4445706 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f4b6800a3e0
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 = 7f4a87fbde80 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xed0f8c]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x461)[0x7aecc1]
/lib64/libpthread.so.0(+0xf370)[0x7f4c2a50c370]
/lib64/libc.so.6(+0x149295)[0x7f4c29009295]
/usr/local/mysql/bin/mysqld(_ZN10Field_blob15copy_blob_valueEP11st_mem_root+0x75)[0x7ecef5]
/usr/local/mysql/bin/mysqld(_Z25mysql_prepare_blob_valuesP3THDR4ListI4ItemEP11st_mem_root+0x298)[0xe1c9c8]
/usr/local/mysql/bin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0x9a0)[0xe1d6a0]
/usr/local/mysql/bin/mysqld(_ZN14Sql_cmd_insert12mysql_insertEP3THDP10TABLE_LIST+0x80d)[0xe1e0fd]
/usr/local/mysql/bin/mysqld(_ZN14Sql_cmd_insert7executeEP3THD+0xc2)[0xe1e8f2]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THDb+0xf57)[0xcb0027]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5c5)[0xcb6ae5]
/usr/local/mysql/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xa69)[0xcb75d9]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcb8f67]
/usr/local/mysql/bin/mysqld(handle_connection+0x2a0)[0xd7a950]
/usr/local/mysql/bin/mysqld(pfs_spawn_thread+0x1b1)[0x124c551]
/lib64/libpthread.so.0(+0x7dc5)[0x7f4c2a504dc5]
/lib64/libc.so.6(clone+0x6d)[0x7f4c28fb776d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f4b6800f100): is an invalid pointer
Connection ID (thread ID): 122
Status: NOT_KILLED

2. my.cnf as follows
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
# *** DO NOT EDIT THIS FILE. It's a template which will be copied to the
# *** default location during install, and will be replaced if you
# *** upgrade to a newer version of MySQL.
[client]
#default-character-set=utf8mb4

[mysqld_multi]
mysqld = /usr/local/mysql/bin/mysqld_safe
mysqladmin = /usr/local/mysql/bin/mysqladmin
log = /usr/local/mysql/log/mysqld_multi.log
user = root

[mysqld1]
port=3306
pid-file=/usr/local/mysql/run/mysql3306.pid
log-error=/usr/local/mysql/log/mysql3306.err
socket=/usr/local/mysql/run/mysql3306.sock
datadir=/usr/local/mysql/data
slow_query_log_file=/usr/local/mysql/log/slow-log-mysqld1
log-bin=/usr/local/mysql/binlogs/bin-log-mysqld1
log-bin-index=/usr/local/mysql/binlogs/bin-log-mysqld1.index
relay-log=/usr/local/mysql/relaylogs/relay-log-mysqld1
relay-log-index=/usr/local/mysql/relaylogs/relay-log-mysqld1.index
innodb_buffer_pool_size=2G
innodb_buffer_pool_instances=2
server-id=603306

[mysqld2]
port=3307
pid-file=/usr/local/mysql/run/mysql3307.pid
log-error=/usr/local/mysql/log/mysql3307.err
socket=/usr/local/mysql/run/mysql3307.sock
datadir=/usr/local/mysql/data2
slow_query_log_file=/usr/local/mysql/log/slow-log-mysqld2
log-bin=/usr/local/mysql/binlogs/bin-log-mysqld2
log-bin-index=/usr/local/mysql/binlogs/bin-log-mysqld2.index
relay-log=/usr/local/mysql/relaylogs/relay-log-mysqld2
relay-log-index=/usr/local/mysql/relaylogs/relay-log-mysqld2.index
innodb_buffer_pool_size=1G
innodb_buffer_pool_instances=2
server-id=603307

slave-skip-errors=1032,1062
# 因为 3307 原本是用默认设置12M, 假如改为1G启动,则会报
innodb_data_file_path=ibdata1:12M:autoextend

[mysqld3]
port=3308
pid-file=/usr/local/mysql/run/mysql3308.pid
log-error=/usr/local/mysql/log/mysql3308.err
socket=/usr/local/mysql/run/mysql3308.sock
datadir=/usr/local/mysql/data3
slow_query_log_file=/usr/local/mysql/log/slow-log-mysqld3
log-bin=/usr/local/mysql/binlogs/bin-log-mysqld3
log-bin-index=/usr/local/mysql/binlogs/bin-log-mysqld3.index
relay-log=/usr/local/mysql/relaylogs/relay-log-mysqld3
relay-log-index=/usr/local/mysql/relaylogs/relay-log-mysqld3.index
innodb_buffer_pool_size=1G
innodb_buffer_pool_instances=4
server-id=603308
read-only=1

[mysqld4]
port=3309
pid-file=/usr/local/mysql/run/mysql3309.pid
log-error=/usr/local/mysql/log/mysql3309.err
socket=/usr/local/mysql/run/mysql3309.sock
datadir=/usr/local/mysql/data4
slow_query_log_file=/usr/local/mysql/log/slow-log-mysqld4
log-bin=/usr/local/mysql/binlogs/bin-log-mysqld4
log-bin-index=/usr/local/mysql/binlogs/bin-log-mysqld4.index
relay-log=/usr/local/mysql/relaylogs/relay-log-mysqld4
relay-log-index=/usr/local/mysql/relaylogs/relay-log-mysqld4.index
innodb_buffer_pool_size=2G
innodb_buffer_pool_instances=2
server-id=603309
#binlog_checksum=none
read-only=1

[mysqld]
basedir=/usr/local/mysql
skip-external-locking

# gtid set on
enforce_gtid_consistency = on
gtid_mode = on
master_info_repository=TABLE
relay_log_info_repository=TABLE
relay_log_recovery=ON

#skip-federated
character-set-server=utf8mb4
init_connect='SET collation_connection = utf8mb4_general_ci'
init_connect='SET NAMES utf8mb4'
#init_connect='SET GLOBAL MASTER_INFO_REPOSITORY = TABLE'
#init_connect='SET GLOBAL RELAY_LOG_INFO_REPOSITORY = TABLE'

#character-set-server=utf8mb4_general_ci
collation-server=utf8mb4_general_ci
skip-character-set-client-handshake

#skip-grant-tables

user = mysql
lower_case_table_names = 0
innodb_file_per_table = on
skip-name-resolve
key_buffer_size=64M
max_allowed_packet=64M
table_open_cache=2048
sort_buffer_size=2M
myisam_sort_buffer_size=64M
thread_cache_size=8
#thread_cache_size=64
query_cache_size=32M
max_binlog_size=1024M
binlog_cache_size=184320
wait_timeout=3600
interactive_timeout=3600

read_rnd_buffer_size=1572864
join_buffer_size=2097152
tmp_table_size=16777216
max_heap_table_size=16777216

max_connections=2000
max_connect_errors=99999999999
expire_logs_days=10
event-scheduler=on

log-bin-trust-function-creators=1
binlog_format=ROW

innodb_stats_persistent_sample_pages=1000
innodb_log_file_size=256M
innodb_log_buffer_size=8M
innodb_log_files_in_group =4
innodb_flush_log_at_trx_commit=0
innodb_lock_wait_timeout=50
#innodb_file_io_threads=4
innodb_flush_method=O_DIRECT
explicit_defaults_for_timestamp=true
innodb_print_all_deadlocks=1
innodb_data_file_path=ibdata1:1G:autoextend

log_slave_updates
slave_compressed_protocol=on
binlog-ignore-db=mysql
binlog-ignore-db=sys
replicate-ignore-db=mysql
replicate-ignore-db=sys
replicate-wild-ignore-table=mysql.%
slave-skip-errors = 1062

# mcafee_ 变量没有落盘
#auto_increment_offset=1
#auto_increment_increment=2

# slave
#slave-parallel-type=LOGICAL_CLOCK
#slave-parallel-workers=8

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

[mysqld_safe]
#malloc-lib = /usr/local/lib/libtcmalloc_minimal.so
#malloc-lib = tcmalloc

[mysqldump]
quick
max_allowed_packet=512M

[mysql]
#no-auto-rehash
#prompt=\U|d>

#default-character-set=utf8mb4

[isamchk]
sort_buffer_size=256M
read_buffer=2M
write_buffer=2M

[mysqlhotcopy]
interactive-timeout

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

3. server version: as the title describing: percona-server-5.7.19-17

jianhaiqing (jianhaiqing) wrote :

before crashing, there are many access denied by server due to the password modified for the user.
i don't know whether it matters or not. I will try to reproduce the bug .

Changed in percona-server:
assignee: nobody → Vishal kasle (vishal.percona)
Vishal kasle (vishal.percona) wrote :

Hello,
    Looking at the crash report it is unclear what was happening just before the crash. Can you please add the complete error log so we can check what was happening when the instance crashed. It would be great if you give us some more information like queries being executed during the time.
    I also double checked the backtrace and looking into the bugs database its a possibility that you could be hitting https://bugs.launchpad.net/percona-server/+bug/1686340 which has been confirmed.
    Can you please provide requested information or try to reproduce it in your environment.

Changed in percona-server:
status: New → Incomplete
assignee: Vishal kasle (vishal.percona) → nobody

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3769

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers