MySQL Bugs: #2486: Replication problem

Bug #2486	Replication problem
Submitted:	23 Jan 2004 2:26	Modified:	23 Jan 2004 5:07
Reporter:	Luca Tocco	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	4.0.17	OS:	Linux (Linux-Mandrake)
Assigned to:		CPU Architecture:	Any

Description:
I can't update slave machine.
I have reset master and slave but the error is persistent.
The file " 'smarty2-bin.index'" exist in master and work fine.
Thanks.
Luca Tocco.

How to repeat:
/disco1/mysql4017/libexec/mysqld: ready for connections.
Version: '4.0.17'  socket: '/tmp/mysql.sock'  port: 3306
040123 11:10:06  Slave I/O thread: connected to master 'repl_rank@192.168.1.8:3306',  replication started in log 'smarty2-bin.index' at position 4
040123 11:10:06  Error reading packet from server: Could not find first log file name in binary log index file (server_errno=1236)
040123 11:10:06  Got fatal error 1236: 'Could not find first log file name in binary log index file' from master when reading data from binary log
040123 11:10:06  Slave I/O thread exiting, read up to log 'smarty2-bin.index', position 4
040123 11:15:46  Slave I/O thread: connected to master 'repl_rank@192.168.1.8:3306',  replication started in log 'smarty2-bin.index' at position 4
040123 11:15:46  Error reading packet from server: Could not find first log file name in binary log index file (server_errno=1236)
040123 11:15:46  Got fatal error 1236: 'Could not find first log file name in binary log index file' from master when reading data from binary log
040123 11:15:46  Slave I/O thread exiting, read up to log 'smarty2-bin.index', position 4
040123 11:16:54  Slave I/O thread: connected to master 'repl_rank@192.168.1.8:3306',  replication started in log 'smarty2-bin.index' at position 4
040123 11:16:54  Error reading packet from server: Could not find first log file name in binary log index file (server_errno=1236)
040123 11:16:54  Got fatal error 1236: 'Could not find first log file name in binary log index file' from master when reading data from binary log
040123 11:16:54  Slave I/O thread exiting, read up to log 'smarty2-bin.index', position 4

I have set master log file:
MASTER_LOG_FILE='smarty2-bin.001';

and it work but:

MASTER_LOG_FILE='smarty2-bin.index';
 not work.

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Additional info:

Hi,
As you noted the correct command is
MASTER_LOG_FILE='smarty2-bin.001';
It's all explained in the replication section of our manual.

Regards,
Guilhem

You also get this error message:

Could not find first log file name in binary log index file (server_errno=1236)

if you specify the full path to the binary log file instead of only the log file in the MASTER_LOG_FILE entry of CHANGE MASTER:

Wrong:

MASTER_LOG_FILE='/mysql/binlog.000001'

Correct:

MASTER_LOG_FILE='binlog.000001'

If you see a / or \ in the Master_Log_File entry of SHOW SLAVE STATUS this is probably the mistake.