Re: Error connecting to master: Can't connect to MySQL server on ' # MUST BE SET' (111)

[Terence]

I found that restarting the mysql server does not recreate the 
master.info file in the data directory. Although I had changed some 
settings in the /etc/my.cnf they did not populate the master.info file. 
So after banging my head for so many hours I deleted the master.info 
file and restarted the server. So that's where the # MU came from.

On a seperate note for those experiencing problems on error 1189 Net 
error reading from master - the problem appears to be innodb tables 
which are not supported by LOAD TABLE FROM MASTER. That's going to be an 
extremely tough one to get around.

Thanks Gleb for your help.
Gleb Paharenko wrote:
Hello.
When you are connecting using mysql, you usually don't specify the destination 
port.
By default it's 3306.
And at the same time master-port=1111. Send us complete contents of config
files. What is in master error log? Check to what port slave instance is trying
to connect (with tcpdump, netstat for example).
Terence <[EMAIL PROTECTED]> wrote:
 

Hi,
I am trying to setup replication on MySQL.
Version 4.1.0alpha
Using:
./bin/mysql -h <IPADDR> -u replication -p
I can connect successfully, but my error logs show
041221  1:12:41  Slave I/O thread: error connecting to master 
'replication # MU@<IPADDR> # MUST BE SET:3306': Error: 'Can't connect to 
MySQL server on '<IPADDR> # MUST BE SET' (111)'  errno: 2003  
retry-time: 60  retries: 86400

Google hasnt turned up anything useful. Any ideas anyone? What am I 
doing wrong.

Master
# The MySQL server
[mysqld]
server-id=1
log-bin
Slave
# The MySQL server
[mysqld]
server-id=9
master-host=<IPADDR>
master-port=1111
master-user=replication
master-password=<password>
show master status
   

bin.0001 position: 4486513
     

thanks!
   


 

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]