MySQL Bugs: #17105: replication does not work when master port != 3306

Bug #17105	replication does not work when master port != 3306
Submitted:	3 Feb 2006 18:54	Modified:	12 Feb 2006 6:21
Reporter:	Julian Dunn	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.18	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
When using a MySQL 5.0.18 slave, if the master is listening on any port other than 3306, replication fails even when master_port is set to the correct listening port on the master.

How to repeat:
- Verify that replication is working between two servers
- Change the master's listener port to something arbitrary (e.g. 50000) by specifying "port=50000" in [mysqld] section in my.cnf
- Restart master
- Verify connectivity to master on port 50000 at the command line using the replication user
- On slave, do

mysql> stop slave;
mysql> change master to master_port = 50000;
mysql> start slave;

- Observe that SHOW SLAVE STATUS shows "connecting to master"
- Observe that in the mysqld.log (with sufficient warnings & errors turned on) the following is observed:

060203 13:52:16 [ERROR] Slave I/O thread: error connecting to master 'repl@master:50000': Error: 'Can't connect to MySQL server on 'master' (13)'  errno: 2003  retry-time: 60  retries: 86400

Thank you for a problem report. What version of MySQL is used on master? 

I am replicating from master version 4.0.27-BK on port 3340 to slave version 5.0.19-BK without any problems right now. I used 4.1.19-BK as master on that same port also. 

Please, try with 3340, just to be sure, and inform about the results.

Hmm... it seems fine now. Perhaps it was user error from my standpoint. Thanks for looking into it!

Closed as requested by reporter. No bug, really.