List:Replication« Previous MessageNext Message »
From:Lars Thalmann Date:December 27 2004 1:16pm
Subject:Re: why Cant replicate
View as plain text  
Hi Nick,

On Thu, 2004-12-23 at 11:20, NiCK wrote:
> master server is ,port is 3306
> slave server is,port is 4506
> Use mysql-max-4.1.8-pc-linux-i686.tar.gz to install
> os is redhat 7.3
> Cant replicate from to,why?
> My error log as following
> 041223 17:57:28  mysqld started
> 041223 17:57:28  InnoDB: Started; log sequence number 0 43634
> 041223 17:57:28 [Warning] mysql.user table is not updated to new password
> format; Disabling new password usage until mysql_fix_privilege_tables is run
> /usr/local/mysql-max/bin/mysqld: ready for connections.

You probably have data from an earlier version of MySQL.  You 
should update the passform format with the mysql_fix_privilege_tables
command.  (Probably not the cause for the below, but doesn't hurt 
to do.)

> Version: '4.1.8-max'  socket: '/tmp/mysql.sock'  port: 4506  Official
> MySQL-max binary
> 041223 17:57:28 [Note] Slave SQL thread initialized, starting replication in
> log 'yide-bin.001' at position 775094342, relay log
> './backup-relay-bin.000002' position: 112
> 041223 17:57:28 [ERROR] Slave: Query caused different errors on master and
> slave. Error on master: 'Invalid error code' (25956), Error on slave: 'You
> have an error in your SQL syntax; check the manual that corresponds to your
> MySQL server version for the right syntax to use near 'ete from iqqusers
> where mobile_no='13305836396'' at line 1' (1064). Default database: 'lete
> from iqqusers where mobile_no='13305836396''. Query: 'ete from iqqusers
> where mobile_no='13305836396'', Error_code: 0

At some point in time, you ran a query that is illegal and that query 
yielded different error codes on the master and slave.  There can be
many things causing this: corrupted disk where relay log is stored,
different data on master/slave, etc.

> 041223 17:57:28 [ERROR] Error running query, slave SQL thread aborted. Fix
> the problem, and restart the slave SQL thread with "SLAVE START". We stopped
> at log 'yide-bin.001' position 775094342

Use the mysqlbinlog program on file yide-bin.001 at 
position 775094342 to check what the above query was.

> 041223 17:57:28 [Note] Slave I/O thread: connected to master
> 'repl@stripped:3306',  replication started in log 'yide-bin.002' at
> position 0
> 041223 17:57:28 [ERROR] Error reading packet from server: Could not find
> first log file name in binary log index file (server_errno=1236)
> 041223 17:57:28 [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
> 041223 17:57:28 [ERROR] Slave I/O thread exiting, read up to log
> 'yide-bin.002', position 0

Best wishes,

Dr. Lars Thalmann
MySQL Cluster,

why Cant replicateNiCK23 Dec
Re: why Cant replicateLars Thalmann27 Dec