0

I am trying to setup Master-Master MySQL replication in MySQL 8.

It was working fine until recently. I am able to connect as replication user from slave host to master; however, when I start replication I get following error code in log:

Error_code: MY-003159

Here is the mysql error when I show slave status\G:

               Slave_IO_State: Connecting to master
                  Master_Host: <server_ip>
                  Master_User: ruser
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000030
          Read_Master_Log_Pos: 155
               Relay_Log_File: mysql-relay-bin.000001
                Relay_Log_Pos: 4
        Relay_Master_Log_File: mysql-bin.000030
             Slave_IO_Running: Connecting
            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: 155
              Relay_Log_Space: 155
              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: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 3159
                Last_IO_Error: error connecting to master 'ruser@<server_ip>:3306' - retry-time: 60  retries: 13
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 0
                  Master_UUID:
             Master_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
           Master_Retry_Count: 86400
                  Master_Bind:
      Last_IO_Error_Timestamp: 190126 20:50:58
     Last_SQL_Error_Timestamp:
               Master_SSL_Crl:
           Master_SSL_Crlpath:
           Retrieved_Gtid_Set:
            Executed_Gtid_Set:
                Auto_Position: 0
         Replicate_Rewrite_DB:
                 Channel_Name:
           Master_TLS_Version:
       Master_public_key_path:
        Get_master_public_key: 0

It was successfully connecting before and replication was happening. Suddenly when I checked status a week later, I saw the following error:

Last_IO_Error: error connecting to master 'ruser@<server_ip>:3306' - retry-time: 60

I tried doing setup with a new user. I get same error now. This new user is never able to connect. What am I missing?

  • Local IP addresses? Perhaps the IP address changed? A firewall issue? – Rick James Jan 27 at 4:58
  • Thank you for the reply, i checked the IP and firewall, as i said user is able to connect using command line in server but fails during replication. – Andy natty Jan 27 at 14:48
  • On the Master, check SHOW GRANTS FOR 'ruser'@'<master-ip>';. Oh, was the IP address in that Last_IO_Error you quoted? And is it a "local" IP (10/172/196.x.x.x)? – Rick James Jan 27 at 17:53
  • I figured out the issue, enabled require_secure_transport=ON recently this caused the issue. Now have to figure out how to enable SSL – Andy natty Jan 27 at 20:32
  • When you figure it out, answer your own question (for some number of reputation points). – Rick James Jan 27 at 22:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.