Bug #21185 SQL Syntax error in a slave
Submitted: 20 Jul 2006 15:41 Modified: 16 Jul 2007 11:29
Reporter: Diego Woitasen Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.0.22 OS:Other (OpenBSD)
Assigned to: CPU Architecture:Any

[20 Jul 2006 15:41] Diego Woitasen
Description:
I have a mysql replication setup with one master and two servers (one of this is in another city with a 1 MB link). The remote slave stop replication with and 'SQL Syntax error' and the other slave no have any problem.

The three servers use the same Mysql and OpenBSD version (3.9). Inclusive, the same hardware.

LOG:
060720 12:14:45 [ERROR] Error reading packet from server:  ( server_errno=1156)
060720 12:14:45 [Note] Slave I/O thread: Failed reading log event, reconnecting
to retry, log 'mysql-bin.000006' position 333438427
060720 12:14:45 [ERROR] Slave: Error '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 ''\uffff\uffff\uffff\uffff\0JFIF\0\0\0\0\0\0\uffff\uffff\0>CREATOR: gd-jpeg v1.0 (using IJG JPEG v62), def' at line 4' on query. Default database: 'acreditaciones'. Query: 'INSERT INTO Archivos (idArchivos,nombre,
                                                        archivo,tipo,idUser_carga,instante_carga)
                                                        VALUES ('','matteo 4x4.jpg',
                                                                '\uffff\uffff\uffff\uffff\0JFIF\0\0\0\0\0\0\uffff\uffff\0>CREATOR: gd-jpeg v1.0 (using IJG JPEG v62), default quality
\uffff\uffff\0C
2!!22222222222222222222222222222222222222222222222222\uffff\uffff\\0\uffff\0\uffff\"\0\uffff\uffff\0\0\0\0\0\0\0\0\0\0\
\uffff\uffff\0\uffff\0\0\0}\0!1AQa\"q2#B\uffff\uffffR\uffff\uffff$3br
%&\'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz
\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\0\0\0\0\0\0\0\ 
\uffff\uffff\0\uffff\0\0w\0!1AQaq\"B
060720 12:14:45 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000006' position 333430176
060720 12:14:53 [Note] Slave: connected to master 'repl@cumbrecba3:3306',replication resumed in log 'mysql-bin.000006' at position 333438427

How to repeat:
I don't know how to repeat the problem, but i happens two times in my servers.
[20 Jul 2006 15:43] Valeriy Kravchuk
Thank you for a problem report. Please, send my.cnf content from your master and "problematic" slave.
[20 Jul 2006 15:58] Diego Woitasen
Master my.cnf

Attachment: my-master.cnf (application/octet-stream, text), 4.81 KiB.

[20 Jul 2006 15:58] Diego Woitasen
Slave my.cnf

Attachment: my-slave.cnf (application/octet-stream, text), 4.79 KiB.

[20 Aug 2006 23:00] Bugs System
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".
[22 Apr 2007 16:35] Valeriy Kravchuk
Sorry for a delay with this bug report (attaching files does not re-open report). Please, check newer version, 5.0.37, and inform about the results.
[22 May 2007 23:00] Bugs System
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".
[16 Jun 2007 11:29] Valeriy Kravchuk
Feedback on any similar bugs with newer (5.0.37-5.0.41) MySQL versions is still needed.
[16 Jul 2007 23:00] Bugs System
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".