I am having a similar issue. Followed the directions on the page... can get the first instance to start... every other instance fails to join.
On my first instance... I start the group replication with
START GROUP_REPLICATION;
and then do a check to make sure it's online with a
SELECT * FROM performance_schema.replication_group_members;
and I get
+---------------------------+--------------------------------------+------------------+-------------+--------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+------------------+-------------+--------------+
| group_replication_applier | 348651ae-0e5f-11e7-bdd6-b8ca3a6d23ec | DT2017-Mysql-155 | 3306 | ONLINE |
+---------------------------+--------------------------------------+------------------+-------------+--------------+
Then just create the test table and add a test row to make sure I have something to replicate.
Then on server 2... I add the lines to the my.cnf
server_id=157
gtid_mode=ON
enforce_gtid_consistency=ON
master_info_repository=TABLE
relay_log_info_repository=TABLE
binlog_checksum=NONE
log_slave_updates=ON
log_bin=binlog
binlog_format=ROW
transaction_write_set_extraction=XXHASH64
loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
loose-group_replication_start_on_boot=off
loose-group_replication_local_address= "192.168.1.157:33061"
loose-group_replication_group_seeds= "192.168.1.155:33061,192.168.1.157:33061,192.168.1.158:33061"
loose-group_replication_bootstrap_group=off
restart the server and log in. Then add the replication user to the system
SET SQL_LOG_BIN=0;
create user repl@'%';
GRANT REPLICATION SLAVE ON *.* TO repl@'%' IDENTIFIED BY '<password>';
FLUSH PRIVILEGES;
SET SQL_LOG_BIN=1;
CHANGE MASTER TO MASTER_USER='repl', MASTER_PASSWORD='<password>' FOR CHANNEL 'group_replication_recovery';
then issue the start group_replication;
START GROUP_REPLICATION;
ERROR 3092 (HY000): The server is not configured properly to be an active member of the group. Please see more details on error log.
is there a different command i can run to get you more information?
here is the log
2017-03-21T19:10:31.698974Z 4 [Note] Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"'
2017-03-21T19:10:31.699050Z 4 [Note] Plugin group_replication reported: '[GCS] Unable to probe network interface "igb1" for IP and netmask information. Skipping!'
2017-03-21T19:10:31.699065Z 4 [Note] Plugin group_replication reported: '[GCS] Unable to probe network interface "igb2" for IP and netmask information. Skipping!'
2017-03-21T19:10:31.699076Z 4 [Note] Plugin group_replication reported: '[GCS] Unable to probe network interface "igb3" for IP and netmask information. Skipping!'
2017-03-21T19:10:31.699087Z 4 [Note] Plugin group_replication reported: '[GCS] Unable to probe network interface "ix0" for IP and netmask information. Skipping!'
2017-03-21T19:10:31.699112Z 4 [Note] Plugin group_replication reported: '[GCS] Added automatically IP ranges 127.0.0.1/8,192.168.1.157/24 to the whitelist'
2017-03-21T19:10:31.699248Z 4 [Note] Plugin group_replication reported: '[GCS] SSL was not enabled'
2017-03-21T19:10:31.699272Z 4 [Note] Plugin group_replication reported: 'Initialized group communication with configuration: group_replication_group_name: "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; group_replication_local_address: "192.168.1.157:33061"; group_replication_group_seeds: "192.168.1.155:33061,192.168.1.157:33061,192.168.1.158:33061"; group_replication_bootstrap_group: false; group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1000000; group_replication_ip_whitelist: "AUTOMATIC"'
2017-03-21T19:10:31.699844Z 27 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''.
2017-03-21T19:10:31.702768Z 4 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2017-03-21T19:10:31.702786Z 4 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7'
2017-03-21T19:10:31.702790Z 30 [Note] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './DT2017-Mysql-157-relay-bin-group_replication_applier.000003' position: 4
2017-03-21T19:10:31.702793Z 4 [Note] Plugin group_replication reported: 'auto_increment_offset is set to 157'
2017-03-21T19:10:31.702877Z 0 [Note] Plugin group_replication reported: 'state 4257 action xa_init'
2017-03-21T19:10:31.702919Z 0 [Note] Plugin group_replication reported: 'Successfully bound to 0.0.0.0:33061 (socket=72).'
2017-03-21T19:10:31.702929Z 0 [Note] Plugin group_replication reported: 'Successfully set listen backlog to 32 (socket=72)!'
2017-03-21T19:10:31.702936Z 0 [Note] Plugin group_replication reported: 'Successfully unblocked socket (socket=72)!'
2017-03-21T19:10:31.702981Z 0 [Note] Plugin group_replication reported: 'connecting to 192.168.1.157 33061'
2017-03-21T19:10:31.702984Z 0 [Note] Plugin group_replication reported: 'Ready to accept incoming connections on 0.0.0.0:33061 (socket=72)!'
2017-03-21T19:10:31.703064Z 0 [Note] Plugin group_replication reported: 'client connected to 192.168.1.157 33061 fd 61'
2017-03-21T19:10:31.703276Z 0 [Note] Plugin group_replication reported: 'connecting to 192.168.1.157 33061'
2017-03-21T19:10:31.703319Z 0 [Note] Plugin group_replication reported: 'client connected to 192.168.1.157 33061 fd 76'
2017-03-21T19:10:31.703452Z 0 [Note] Plugin group_replication reported: 'connecting to 192.168.1.157 33061'
2017-03-21T19:10:31.703492Z 0 [Note] Plugin group_replication reported: 'client connected to 192.168.1.157 33061 fd 71'
2017-03-21T19:10:31.703646Z 0 [Note] Plugin group_replication reported: 'connecting to 192.168.1.157 33061'
2017-03-21T19:10:31.703696Z 0 [Note] Plugin group_replication reported: 'client connected to 192.168.1.157 33061 fd 80'
2017-03-21T19:10:31.703816Z 0 [Note] Plugin group_replication reported: 'connecting to 192.168.1.157 33061'
2017-03-21T19:10:31.703856Z 0 [Note] Plugin group_replication reported: 'client connected to 192.168.1.157 33061 fd 75'
2017-03-21T19:10:31.703965Z 0 [Note] Plugin group_replication reported: 'connecting to 192.168.1.157 33061'
2017-03-21T19:10:31.704004Z 0 [Note] Plugin group_replication reported: 'client connected to 192.168.1.157 33061 fd 83'
2017-03-21T19:10:31.704118Z 0 [Note] Plugin group_replication reported: 'connecting to 192.168.1.155 33061'
2017-03-21T19:10:31.704175Z 0 [Note] Plugin group_replication reported: 'client connected to 192.168.1.155 33061 fd 86'
2017-03-21T19:10:32.989634Z 0 [Note] Plugin group_replication reported: 'state 4257 action xa_snapshot'
2017-03-21T19:10:32.989797Z 0 [Note] Plugin group_replication reported: 'new state x_recover'
2017-03-21T19:10:32.989808Z 0 [Note] Plugin group_replication reported: 'state 4277 action xa_complete'
2017-03-21T19:10:32.989898Z 0 [Note] Plugin group_replication reported: 'new state x_run'
2017-03-21T19:10:37.259661Z 0 [ERROR] Plugin group_replication reported: 'This member has more executed transactions than those present in the group. Local transactions: e08201cd-0e60-11e7-baab-b8ca3a6d1298:1 > Group transactions: 348651ae-0e5f-11e7-bdd6-b8ca3a6d23ec:1,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-9'
2017-03-21T19:10:37.259678Z 0 [ERROR] Plugin group_replication reported: 'The member contains transactions not present in the group. The member will now exit the group.'
2017-03-21T19:10:37.259685Z 0 [Note] Plugin group_replication reported: 'To force this member into the group you can use the group_replication_allow_local_disjoint_gtids_join option'
2017-03-21T19:10:37.259740Z 4 [Note] Plugin group_replication reported: 'Going to wait for view modification'
2017-03-21T19:10:37.259881Z 0 [Note] Plugin group_replication reported: 'getstart group_id 4317e324'
2017-03-21T19:10:40.826710Z 0 [Note] Plugin group_replication reported: 'state 4330 action xa_terminate'
2017-03-21T19:10:40.826763Z 0 [Note] Plugin group_replication reported: 'new state x_start'
2017-03-21T19:10:40.826773Z 0 [Note] Plugin group_replication reported: 'state 4257 action xa_exit'
2017-03-21T19:10:40.826793Z 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
2017-03-21T19:10:40.826801Z 0 [Note] Plugin group_replication reported: 'new state x_start'
2017-03-21T19:10:46.164860Z 4 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1'
2017-03-21T19:10:46.164876Z 4 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1'
2017-03-21T19:10:46.165002Z 30 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2017-03-21T19:10:46.165388Z 27 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'