aborted.
Fix the problem, and restart the slave SQL thread with SLAVE START.
We stopped at log 'mysql-bin.002730' position 52953235
110928 23:31:53 [ERROR] Error reading packet from server: log event
entry exceeded max_allowed_packet; Increase max_allowed_packet on
master ( server_errno=1236)
110928 23
Is there any way I can find out how big I should set max_allowed_packet?
I have changed it from the default 1M to 32M, but I still get that error.
Or is it a bug? We use MySQL 4.0.12 on the slave and 4.0.15-max on the master.
How big should I set max_allowed_packet? The servers are dual Pentium
Hello.
In my opinion (it is based on looking through the source code, but I
can be wrong) - the max_allowed_packet should be at least more than
any event in the master's binary log. The tool for researching
binary logs is mysqlbinlog utility. See:
packet too big errors in replication are often a sign of corrupt
binary logs. If it's on a slave reading the relay log
often times flushing it will temporarily solve the problem. The easiest
way to flush the relay logs is to do a slave stop; change master to back
to the current file name and
Today on a slave I got (this actually has occured several times in the past
months):
Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log
'xxx-bin.040' at position 47694
010511 10:37:19 Error reading packet from server: log event entry exceeded
max_allowed_packet
Hello,
I'm trying to set up replication, but I cant get any further than this
message on the slave.
Error reading packet from server: log event entry exceeded
max_allowed_packet
My max allowed packet size is 512M which I've gradually reached while trying
to stop the above error message
Today on a slave I got:
Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log
'xxx-bin.040' at position 47694
010511 10:37:19 Error reading packet from server: log event entry exceeded
max_allowed_packet - increase max_allowed_packet on master (read_errno
0
