On Tue, Aug 19, 2003 at 09:12:03AM -0400, Jason McCormick wrote: > Hello all, > > Sorry to post this again, but I go not response and was really hoping > someone can help me as this is a mission-critical problem.
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 have 3 slave MySQL servers (4.0.13) replicating from a master > machine (4.0.13). The master machine is running only MySQL while > the slave machines are an Apache + Tomcat + MySQL web service. All > slave machines are precisely identical. I'm running into a > situation where (seemly at random) after a month or two of > consistently flawless performance, just ONE of the slave machines > will report the following error in the .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 event entry, check the master > for binlog corruption This may also be a network problem, > or just a bug in the master or slave code. > 030807 9:22:35 Error running query, slave SQL thread aborted. Fix > the problem, and restart the slave SQL thread with "SLAVE > START". > We stopped at log 'oakpub-bin.002' position 25239274 Had the machine crashed and restarted recently? Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.13: up 18 days, processed 902,078,317 queries (579/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
