crash when start group replication

Bug #1702055 reported by 神仙
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Expired
Undecided
Unassigned

Bug Description

data dir are created by oracle mysql 5.7. percona server can start successfully. But crashes when start group replication.

version: Percona-Server-5.7.18-15-Linux.x86_64.ssl101
os: Centos 6.8 2.6.32-642.1.1.el6.x86_64

error log:

2017-07-03T10:02:02.700488Z 5 [Note] Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"'
2017-07-03T10:02:02.700634Z 5 [Note] Plugin group_replication reported: '[GCS] Added automatically IP ranges 10.215.20.19/22,127.0.0.1/8 to the whitelist'
2017-07-03T10:02:02.700850Z 5 [Note] Plugin group_replication reported: '[GCS] SSL was not enabled'
2017-07-03T10:02:02.700877Z 5 [Note] Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: "05
e58b03-5bd7-44f4-94a5-b5743702e6be"; group_replication_local_address: "10.215.20.19:4319"; group_replication_group_seeds: "10.215.20.19:4319,10.215.20.22:4322
,10.215.20.24:4324"; group_replication_bootstrap_group: false; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1000000; group_r
eplication_ip_whitelist: "AUTOMATIC"'
10:02:02 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=2097152
read_buffer_size=2097152
max_used_connections=2
max_threads=4001
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 16442405 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f5c9440e000
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 0x30000
/opt/percona-5.7/bin/mysqld(my_print_stacktrace+0x2c)[0xed35ac]
/opt/percona-5.7/bin/mysqld(handle_fatal_signal+0x461)[0x7a15e1]
/lib64/libpthread.so.0(+0xf7e0)[0x7f5dfb16c7e0]
/opt/percona-5.7/bin/mysqld(_ZN16Protocol_classic8init_netEP6st_vio+0x1)[0xc13881]
/opt/mysql-5.7/lib/plugin/group_replication.so(_ZN14Applier_module26set_applier_thread_contextEv+0x63)[0x7f5c525828a3]
/opt/mysql-5.7/lib/plugin/group_replication.so(_ZN14Applier_module21applier_thread_handleEv+0x1c)[0x7f5c5258523c]
/opt/mysql-5.7/lib/plugin/group_replication.so(+0xc6ff9)[0x7f5c52585ff9]
/opt/percona-5.7/bin/mysqld(pfs_spawn_thread+0x1b4)[0x1208a24]
/lib64/libpthread.so.0(+0x7aa1)[0x7f5dfb164aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f5df945caad]

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): 7
Status: NOT_KILLED

神仙 (xiezhenye)
description: updated
Revision history for this message
Sveta Smirnova (svetasmirnova) wrote :

Thank you for the report.

Please describe step-by-step your actions which you did when enabled group replication.

For example:

- stopped mysqld
- added options X, Y, Z (specify which) to the configuraiton file
- started mysqld
- got crash immediately

Please also provide configuration file you use.

Changed in percona-server:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona Server because there has been no activity for 60 days.]

Changed in percona-server:
status: Incomplete → Expired
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.