MySQL Bugs: #30605: replication on slave fails: error 1236: 'Misconfigured master

Bug #30605	replication on slave fails: error 1236: 'Misconfigured master - server id
Submitted:	23 Aug 2007 18:53	Modified:	27 Sep 2007 19:49
Reporter:	Shyam Badrinath	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Replication	Severity:	S1 (Critical)
Version:	5.0.46	OS:	Linux (Redhat ES4 Update 4)
Assigned to:		CPU Architecture:	Any

Description:
Trying to setup master/replica on a 2 node system
When starting up the slave mysql, it complains with 
Version: '5.0.46-enterprise-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Enterprise Server (Commercial)
070822 18:07:41 [Note] Slave SQL thread initialized, starting replication in log 'emslinux7-bin.000004' at position 98, relay log '/export/home/dbdata/APPDB/emslinux6-relay-bin.000003' position: 98
070822 18:07:41 [Note] Slave I/O thread: connected to master 'dbimpl_replica@10.6.20.237:3306',  replication started in log 'emslinux7-bin.000004' at position 98
070822 18:07:41 [ERROR] Error reading packet from server: Misconfigured master - server id was not set ( server_errno=1236)070822 18:07:41 [ERROR] Got fatal error 1236: 'Misconfigured master - server id was not set' from master when reading data
from binary log
070822 18:07:41 [Note] Slave I/O thread exiting, read up to log 'emslinux7-bin.000004', position 98

I have checked that the server id is set in my.cnf on the master node and replica node. I have also checked the binary logs on master to see if it contained the server id and it did contain a value of 1.
server id on replica is set to 2.

How to repeat:
I started mysql on node 1 in master mode. Took a backup of the database and ftp'ed  it over to the standby node. Told mysql to start up with the backed up tar file.
After startup, I see the error as shown above.

Thank you for the report.

Please provide all configuration files for both master and slave.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".