...
If your replication has been blocked by a command line that cannot process on the slave server, it may have gotten out of synch to an extent that the easiest way is to resynch with a data duplication. To do this simply follow the original instructions to backup the master and restore to the slave found on the Running A Backup Server for Bannister Lake Products with DMan Backup in the section that starts with: Making a Copy of the Primary Database For Import On the Backup Server.
Slave IO Connection Error
If the slave is not able to connect to the master you might see an IO Error message like this:
| Warning |
|---|
error connecting to master 'blbackup@10.21.31.52:3306' - retry-time: 60 retries: 4 message: Authentication plugin 'caching_sha2_password' reported error: Authentication requires secure connection. |
This error is telling you that the slave is failing to connect to the master server.
Possible Solutions
Connect Manually First
You might be able to solve this problem by creating a manual connection in a MySQL tool like Workbench. This solution provided by this documented bug in MySQL 8.
| Code Block |
|---|
STOP SLAVE; |
Connect to the Primary Server using another connection tab in MySQL Workbench (or another tool).
using the
blbackupuser
After you have successfully connected using the blbackup user and password - restart the slave.
| Code Block |
|---|
START SLAVE; |
Assuming the slave starts - check the status
| Code Block |
|---|
SHOW SLAVE STATUS; |
Hopefully the slave is now successfully connected.
Confirm User Credentials
Another tip is to check that the login for blbackup exists on the Primary server and has been given appropriate privileges. Then confirm that the slave has been setup with the correct settings (SET MASTER TO…)
See: https://bannisterlake.atlassian.net/wiki/spaces/ST/pages/12615688/Configuring+MySQL+Users#Recommended-Replication-User for details on how to define the user.