server_errno=1236

server_errno=1236

设置主/从时，Log中出现如下的错误信息

081023 16:56:47  mysqld ended

 

081023 16:58:08  mysqld started

081023 16:58:08 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295

081023 16:58:08 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295

081023 16:58:08  InnoDB: Started; log sequence number 0 43675

081023 16:58:08 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=jp_club2-relay-bin' to avoid this problem.

081023 16:58:08 [Note] /usr/alibaba/install/mysql-5.0.67/libexec/mysqld: ready for connections.

Version: '5.0.67-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

081023 16:58:08 [Note] Slave SQL thread initialized, starting replication in log ' mysql-bin.000016' at position 498375022, relay log './jp_club2-relay-bin.000002' position: 98

081023 16:58:08 [Note] Slave I/O thread: connected to master 'repclub2@jp_club1:3306',  replication started in log ' mysql-bin.000016' at position 498375022

081023 16:58:08 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236)

081023 16:58:08 [ERROR] Got fatal error 1236: 'Could not find first log file name in binary log index file' from master when reading data from binary log

081023 16:58:08 [Note] Slave I/O thread exiting, read up to log ' mysql-bin.000016', position 498375022

 

查看slave的状态L：

mysql> show slave status\G

           Slave_IO_Running: No

          Slave_SQL_Running: Yes

 

 

原因：

 

是由于dump数据时没有锁定表，执行命令

mysql> FLUSH TABLES WITH READ LOCK;

后退出了这个session，导致表没被锁

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/30821/viewspace-481727/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/30821/viewspace-481727/