Re: Misconfigured master - server id was not set

[Jan Schneider]

Gleb Paharenko wrote:
> Hello.
> 
> 
> 
> Setting master to 127.0.0.1 could produce a problem. 
> 
> 
> 
> "MASTER_HOST and MASTER_PORT  are the hostname (or IP address) of the
> 
> master host and its TCP/IP port. Note that if MASTER_HOST is equal to
> 
> localhost, then, like in other parts of MySQL, the port may be ignored
> 
> (if Unix socket files can be used, for example)."

I got hit by that already when I tried to use "localhost" for the master 
host, and the slave tried to connect to itself. This was fixed by using 
"127.0.0.1", and the authentication as the replication user that I 
created on the master works fine since then.

> Jan Schneider <jan@stripped> wrote:
> 
>>Hi,
> 
> 
>>I have slave-master-setup that is special in two ways:
> 
>>1) The slave connects through an stunnel
> 
>>2) The slave replicates only one db
> 
> 
>>As soon as I start the slave process, the server connects but fails with 
> 
>>the following log messages:
> 
> 
>>Jul  6 14:58:11 ijssel1 mysqld[11755]: 050706 14:58:11 Slave SQL thread 
> 
>>initialized, starting replication in log 'mysql-bin.001' at position 
> 
>>227973, relay log './ijssel1-relay-bin.001' position: 4
> 
>>Jul  6 14:58:11 ijssel1 mysqld[11755]: 050706 14:58:11 Slave I/O thread: 
> 
>>connected to master 'replication@stripped:3307',  replication started 
> 
>>in log 'mysql-bin.001' at position 227973
> 
>>Jul  6 14:58:11 ijssel1 mysqld[11755]: 050706 14:58:11 Error reading 
> 
>>packet from server: Misconfigured master - server id was not set 
> 
>>(server_errno=1236)
> 
>>Jul  6 14:58:11 ijssel1 mysqld[11755]: 050706 14:58:11 Got fatal error 
> 
>>1236: 'Misconfigured master - server id was not set' from master when 
> 
>>reading data from binary log
> 
>>Jul  6 14:58:11 ijssel1 mysqld[11755]: 050706 14:58:11 Slave I/O thread 
> 
>>exiting, read up to log 'mysql-bin.001', position 227973
> 
>>Jul  6 14:58:18 ijssel1 mysqld[11755]: 050706 14:58:18 Error reading 
> 
>>relay log event: slave SQL thread was killed
> 
> 
>>On the master side I see the stunnel connecting.
> 
> 
>>To rule out corrupted binary logs, I did a RESET MASTER on the master. I 
> 
>>verified with "SHOW VARIABLES" and "SHOW BINLOG EVENTS" that the master 
> 
>>has server-id 1, the slave 2, and the server-id 1 is correctly used in 
> 
>>the binlogs.
> 
> 
>>Any ideas?
> 
> 
>>Jan.
> 
> 
> 
> 
>