2 improved spelling of proper names; corrected a type; improved formatting
source | link

MasterI have a master running mysqlMySQL 5.6.17 on win10Windows 10, and a slave running mysqlMySQL 5.7.25 on an Ubuntu 17.10 box on a (Windows) LAN.

Replication ran fine until Ubuntu upgrade to 18.04. Now slave repeatedly gives the following error ...

"Slave I/O for channel '': error connecting to master 'repl@xxxxxx:3306' - retry-time: 60 retries: 12, Error_code: 2005" (master server name x'd out).

"Slave I/O for channel '': error connecting to master 'repl@xxxxxx:3306' - retry-time: 60 retries: 12, Error_code: 2005" (master server name x'd out).

The 'repl'repl user connects fine to the mysqlMySQL instance on the master from the mysql client program running on the slave machine terminal. (AdAnd vice versa).

Resetting the master then running ...:

STOP SLAVE; CHANGE MASTER TO master_host='xxxxxx', master_port=3306, master_user='repl', master_password='xxxxxx', master_heartbeat_period=1, MASTER_LOG_FILE='xxxxxx-binlog.000001', MASTER_LOG_POS=120 ; START SLAVE;

STOP SLAVE;
CHANGE MASTER TO
    master_host='xxxxxx',
    master_port=3306,
    master_user='repl',
    master_password='xxxxxx',
    master_heartbeat_period=1,
    MASTER_LOG_FILE='xxxxxx-binlog.000001', 
    MASTER_LOG_POS=120 
;
START SLAVE;

... (again identifying names x'd out) yielded no change.

I'm at a loss. Anybody?

Master running mysql 5.6.17 on win10, slave running mysql 5.7.25 on an Ubuntu 17.10 box on a (Windows) LAN.

Replication ran fine until Ubuntu upgrade to 18.04. Now slave repeatedly gives the following error ...

"Slave I/O for channel '': error connecting to master 'repl@xxxxxx:3306' - retry-time: 60 retries: 12, Error_code: 2005" (master server name x'd out).

The 'repl' user connects fine to the mysql instance on the master from the mysql client program running on the slave machine terminal. (Ad vice versa).

Resetting the master then running ...

STOP SLAVE; CHANGE MASTER TO master_host='xxxxxx', master_port=3306, master_user='repl', master_password='xxxxxx', master_heartbeat_period=1, MASTER_LOG_FILE='xxxxxx-binlog.000001', MASTER_LOG_POS=120 ; START SLAVE;

... (again identifying names x'd out) yielded no change.

I'm at a loss. Anybody?

I have a master running MySQL 5.6.17 on Windows 10, and a slave running MySQL 5.7.25 on an Ubuntu 17.10 box on a (Windows) LAN.

Replication ran fine until Ubuntu upgrade to 18.04. Now slave repeatedly gives the following error:

"Slave I/O for channel '': error connecting to master 'repl@xxxxxx:3306' - retry-time: 60 retries: 12, Error_code: 2005" (master server name x'd out).

The repl user connects fine to the MySQL instance on the master from the mysql client program running on the slave machine terminal. (And vice versa).

Resetting the master then running:

STOP SLAVE;
CHANGE MASTER TO
    master_host='xxxxxx',
    master_port=3306,
    master_user='repl',
    master_password='xxxxxx',
    master_heartbeat_period=1,
    MASTER_LOG_FILE='xxxxxx-binlog.000001', 
    MASTER_LOG_POS=120 
;
START SLAVE;

... (again identifying names x'd out) yielded no change.

I'm at a loss. Anybody?

1
source | link

MySQL slave connect to master error_code 2005

Master running mysql 5.6.17 on win10, slave running mysql 5.7.25 on an Ubuntu 17.10 box on a (Windows) LAN.

Replication ran fine until Ubuntu upgrade to 18.04. Now slave repeatedly gives the following error ...

"Slave I/O for channel '': error connecting to master 'repl@xxxxxx:3306' - retry-time: 60 retries: 12, Error_code: 2005" (master server name x'd out).

The 'repl' user connects fine to the mysql instance on the master from the mysql client program running on the slave machine terminal. (Ad vice versa).

Resetting the master then running ...

STOP SLAVE; CHANGE MASTER TO master_host='xxxxxx', master_port=3306, master_user='repl', master_password='xxxxxx', master_heartbeat_period=1, MASTER_LOG_FILE='xxxxxx-binlog.000001', MASTER_LOG_POS=120 ; START SLAVE;

... (again identifying names x'd out) yielded no change.

I'm at a loss. Anybody?