MySQL Bugs: #78619: There is no input in error log indicating stopped corosync or wrong username

Bug #78619	There is no input in error log indicating stopped corosync or wrong username
Submitted:	29 Sep 2015 8:19	Modified:	17 Aug 2016 3:50
Reporter:	Shahriyar Rzayev	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Group Replication	Severity:	S1 (Critical)
Version:	0.5.0-dmr	OS:	Linux (CentOS 7, Ubuntu 14.04)
Assigned to:		CPU Architecture:	Any

Description:
If you try to run START GROUP_REPLICATION statement without starting corosync daemon:

mysql> 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.

But in error log there will no entry indicating corosync did not started or something else.

How to repeat:
Follow all steps from this tutorial:

http://mysqlhighavailability.com/getting-started-with-mysql-group-replication/

Try to start group replication without starting corocsync.

For further reading about corosync refer to -> 
http://mysqlhighavailability.com/mysql-group-replication-a-small-corosync-guide/

Suggested fix:
If it is not related to plugin
(direct error for eg, [ERROR] Plugin group_replication reported: 'The group name option is mandatory') it should be indicated that error depends on external library or something else for further clarification.

On ubuntu 14.04 after compiling plugin with MySQL.
I follow all steps for getting started with group replication plugin:

node1 [localhost] {msandbox} ((none)) > 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.

But there is no input in error log.

In this condition i have started corosync:

sh@shrzayev:~$ sudo service corosync status
 * corosync is running

sh@shrzayev:~$ sudo corosync-cfgtool -s
Printing ring status.
Local node ID 2130706433
RING ID 0
	id	= 127.0.0.1
	status	= ring 0 active with no faults

Looking for further actions to obtain necessary information about problem.

There is no input in error log indicating stopped corosync...

Yes, it's a known issue, but not a easy one since we are dealing with an external service. 
This is under discussion, so I cannot give any further input about this.

Any other corosync issue can be due to the lack of a proper uidgid file, lack of a equal cryptographic key on all group members, bad network configuration, etc. 
Also refer to your corosync log file and check for errors.

When i look at corosync log file as  Pedro advice:

sh@shrzayev:~$ cat /var/log/corosync.log | grep error
Oct 07 16:18:24 [30875] shrzayev corosync error   [MAIN  ] Denied connection attempt from 1000:1000
Oct 07 16:18:24 [30875] shrzayev corosync error   [QB    ] Invalid IPC credentials (30876-29957-19).

1000:1000 is equal to my local 'sh' user, but i put 'mysql' user inside /etc/corosync/uidgid.d. And started MySQL as 'sh' user
So changing from 'mysql' to 'sh' in file will fix this:

sh@shrzayev:~$ cat /etc/corosync/uidgid.d/users 
uidgid {
 uid: sh
 gid: sh
}

in the end, i could start it :)

node1 [localhost] {msandbox} ((none)) > start group_replication;
Query OK, 0 rows affected (0,48 sec)

Version: '5.7.8-rc-debug-log-valgrind'  socket: '/tmp/mysql_sandbox8379.sock'  port: 8379  Group Replication enabled MySQL-5.7.8
2015-10-07T11:27:39.195331Z 3 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='', master_port= 3307, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 3307, master_log_file='', master_log_pos= 4, master_bind=''.
2015-10-07T11:27:39.340502Z 4 [Note] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './mysql-relay-group_replication_applier.000001' position: 4
2015-10-07T11:27:39.340565Z 2 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2015-10-07T11:27:39.356927Z 2 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7'
2015-10-07T11:27:39.356964Z 2 [Note] Plugin group_replication reported: 'auto_increment_offset is set to 101'
2015-10-07T11:27:39.358529Z 0 [Note] Plugin group_replication reported: 'Starting group replication recovery with view_id 1498205086:1'
2015-10-07T11:27:39.359196Z 5 [Note] Plugin group_replication reported: 'Only one server alive. Declaring this server as online within the replication group'
2015-10-07T11:27:39.359889Z 0 [Note] Plugin group_replication reported: 'This server was declared online within the replication group'

For clarification, there will be no indication in MySQL error log when:

1. corosync is stopped
2. when wrong user saved into file in /etc/corosync/uidgid.d/ folder.

Hi Shahriyar,

Any chance you can test with 0.8 and see if helps? While verifying other bugs I found related info in error log:

[umshastr@hod03]/export/umesh/server/source/bugs/mysql-5.7.14-labs: bin/mysql -uroot -S /tmp/mysql_ushastry14115.sock --prompt='node1>'
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 9
Server version: 5.7.14-labs-gr080-log Source distribution

Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

node1>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.
node1>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.
node1>\q

-- in error log

2016-08-11T08:12:50.863953Z 0 [Note] Plugin group_replication reported: '1470903170.863940 /export/umesh/server/source/bugs/mysql-5.7.14-labs-gr080/rapid/plugin/group_replication/libmysqlgcs/src/bindings/xcom/xcom/xcom_base.c:2179 new state x_start'
2016-08-11T08:12:50.863957Z 0 [Note] Plugin group_replication reported: 'state 4115 action xa_exit'
2016-08-11T08:12:50.894335Z 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
2016-08-11T08:12:50.894383Z 0 [Note] Plugin group_replication reported: '1470903170.894373 /export/umesh/server/source/bugs/mysql-5.7.14-labs-gr080/rapid/plugin/group_replication/libmysqlgcs/src/bindings/xcom/xcom/xcom_base.c:2180 new state x_start'
2016-08-11T08:12:50.894464Z 0 [Warning] Plugin group_replication reported: 'read failed'
2016-08-11T08:12:50.903746Z 0 [ERROR] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 10301'
2016-08-11T08:13:20.807766Z 2 [ERROR] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2016-08-11T08:13:20.807796Z 2 [Note] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
2016-08-11T08:13:20.807810Z 2 [ERROR] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'
2016-08-11T08:13:20.807874Z 2 [Note] Plugin group_replication reported: 'Destroying SSL'
2016-08-11T08:13:20.807879Z 2 [Note] Plugin group_replication reported: 'Success destroying SSL'
2016-08-11T08:13:20.807929Z 2 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1'
2016-08-11T08:13:20.807932Z 2 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1'
2016-08-11T08:13:20.808424Z 6 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2016-08-11T08:13:20.808859Z 3 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'
2016-08-11T08:16:58.267557Z 9 [Note] Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"'

Thanks,
Umesh

Well, now this bug can be safely closed. Because there is no corosync lib anymore with 0.8 version as i know.

Thanks for confirming.
Closing it now.