Bug #108948 Getting mislead error message after successful replication set
Submitted: 1 Nov 2022 7:50 Modified: 21 Nov 2022 11:16
Reporter: Dipeeka Pise Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.6 OS:Windows
Assigned to: MySQL Verification Team CPU Architecture:Any

[1 Nov 2022 7:50] Dipeeka Pise
Description:
Steps:

1. Try to set replication with mysql utility.
2. you will get following logs.
 # master on 172.18.50.28: ... connected.
 # slave on 172.18.50.43: ... connected.
 # Checking for binary logging on master...
 # Setting up replication...
 ERROR: Cannot setup replication.
3. check for slave status

Behavior: Replication was set properly and it is replicating data and status is below:
Slave_IO_State: Waiting for master to send event
                  Master_Host: x.x.x.x
                  Master_User: user
                  Master_Port: xxxxx
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000004
          Read_Master_Log_Pos: 60670
               Relay_Log_File: x-relay-bin.000002
                Relay_Log_Pos: 41351
        Relay_Master_Log_File: mysql-bin.000004
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 60670
              Relay_Log_Space: 41533
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: x
             Master_Info_File: somepath\mysql\data\master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: 
                Auto_Position: 0

IMP: 
why we are getting message as failure, even if we setup replication 
successfully.
even we don't have any logged error in slave status.

How to repeat:
just try to set replication with mysql utility.
[4 Nov 2022 2:56] MySQL Verification Team
Hi,

5.6 is rather old? Have you tried with latest 5.7 or 8.0?

What MySQL utility are you using to setup replication?

thanks
[21 Nov 2022 5:40] Dipeeka Pise
Actually 5.6 is one compatible with my Operating systems. SO looking for same. Can you help on same?
[21 Nov 2022 11:16] MySQL Verification Team
Hi,

No. MySQL 5.6 has reached its EOL in February 2021. This is not a serious/critical/security issue that would warantee a fix so one would not be made for 5.6.