Check on both master ans slave:
mysql> show global variables like 'max_allowed_packet';
to se what you have. If i don't remember wrong this can be changed in
run-time (you don't have to stop the server).
mysql> set global max_allowed_packet=<soemthing>
change <something> with at least one megabyte or even more.
On Fri, 2009-01-30 at 16:49 +0100, Thomas Ackermann wrote:
> Rick James schrieb:
> > Use one or the other, not both, of -do- and -ignore-.
> Hello and thanx!
> That helped alot ....
> Still, it seems that my slaves have problems to keep up with the master
> - all of them using INNODB.
> I get such messages:
> 090130 16:43:54 [Note] Slave I/O thread: connected to master
> 'slave@mysql:3307', replication started in log 'mysql-bin.000002' at
> position 305965
> 090130 16:43:54 [ERROR] Error reading packet from server: log event
> entry exceeded max_allowed_packet; Increase max_allowed_packet on master
> 090130 16:43:54 [ERROR] Got fatal error 1236: 'log event entry exceeded
> max_allowed_packet; Increase max_allowed_packet on master' from master
> when reading data from binary log
> 090130 16:43:54 [ERROR] Slave I/O thread exiting, read up to log
> 'mysql-bin.000002', position 305965
> The database is definitely not high volume - it is a small forum and a
> small users database.
> So, that error message confused me ...