We recently completed a project where all of our production servers were
replaced. As part of this project, one of the new servers acted as a
replication-slave to one of the old servers, which was the
replication-master. I had replication up and running just fine on
multiple slaves for a couple of years. Last weekend I moved all
functionality from the old server to the new server so that the new
server is now setup at the replication-master. I am trying to setup
replication-slaves on some of the other new servers and have run into
problems doing so.
In the my.ini for the master, there is:
The master is creating the binary-log and index. There is a replication
account setup on the master called "replication".
The slave is creating a relay-log and index, has what appears to be
correct master.info and relay-log.info files. When I start the slave I
get the following in the error log:
090325 9:03:30 [Note] Slave SQL thread initialized, starting
replication in log 'mysql_bin.000004' at position 10120038, relay log
'.\AMSCD2-relay-bin.000002' position: 4
090325 9:03:30 [Note] Slave I/O thread: connected to master
'replication@amstcop:3306', replication started in log
'mysql_bin.000004' at position 10120038
090325 9:03:30 [ERROR] Error reading packet from server: Could not find
first log file name in binary log index file (server_errno=1236)
090325 9:03:30 [ERROR] Got fatal error 1236: 'Could not find first log
file name in binary log index file' from master when reading data from
I'm sure that I've overlooked something, well, stupid, but have
struggled with it the last few days to no avail. All servers are using
the same version of 4.1.22-community-nt.
I feel a bit naked without the replication so your assistance in helping
me getting it up and running will be very appreciated.
Dirk Bremer - Senior Systems Engineer - Utility - AMS
NISC Lake St. Louis MO - USA Central Time Zone
636-755-2652 fax 636-755-2502