Try upgrading to the newest 4.0 release of mysql. 4.0 up until about .19
or .20 had odd replication problems.
Scott M. Grim wrote:
I recently installed SUSE 9.1 64bit with MySQL 4.0.18 on a new server and have
been getting the following errors:
050509 10:53:14 Error reading packet from server:
I recently installed SUSE 9.1 64bit with MySQL 4.0.18 on a new server and have
been getting the following errors:
050509 10:53:14 Error reading packet from server: bogus data in log event
(server_errno=1236)
050509 10:53:14 Got fatal error 1236: 'bogus data in log event' from master
when read
> Please don't take this the wrong way, but mission-critical problems
> should be sent thru MySQL's official support channels. Otherwise
> you're at the mercy of a bunch of volunteers...
I don't. :) I use a lot of free/open software. I've found that the
volunteers are often better then paid su
he .err log:
>
> 030807 9:22:35 Error in Log_event::read_log_event():
> 'Event too big', data_len=1869425764,event_type=114
> 030807 9:22:35 Error reading relay log event: slave SQL thread
> aborted because of I/O error
> 030807 9:22:35 Could not parse log
9:22:35 Error in Log_event::read_log_event():
'Event too big', data_len=1869425764,event_type=114
030807 9:22:35 Error reading relay log event: slave SQL thread
aborted because of I/O error
030807 9:22:35 Could not parse log event entry, check the master
Michael Loftis <[EMAIL PROTECTED]> wrote:
> Recently, and pretty consistently our slave's relay logs have been getting
> garbage that is not in the master. The symptom is usually a truncated
> query with a few characters of garbage. The solution for now is to change
> master to to the errored
Recently, and pretty consistently our slave's relay logs have been getting
garbage that is not in the master. The symptom is usually a truncated
query with a few characters of garbage. The solution for now is to change
master to to the errored master bin log and position and have it start
re
