On Thursday 07 March 2002 10:48 pm, Jeremy Zawodny wrote: > The 4.0.x slave I had just rebuilt the other day died about 40 minutes > ago and produced a core file each time. ?It got caught in the cycle of > "core dump, restart, core dump, restart..."
Jeremy: I think I now understand what happened, or at least I have a pausilble theory that explains what I see in the logs. When I had you kill the broken mysqld last time it went down in the middle of updating db3-relay-bin.005 - that is the only explanation I can think of for it being truncated in the middle of event and especially at such a strange position that is not anywhere near your max_binlog_size value. To prove this, check modification time on db3-relay-bin.005 - should be around the time mysqld was killed and should be almost identical to the creation time on the first core, if you still have it around. Nevertheless, it was a blessing in disguise to have the stale broken log laying around - it helped me find a different bug. However, we need to fix the stale log problem before we can go on. One way to do is to re-start the whole replication from scratch. A more creative way would be to use dd to trim db3-relay-bin.005 down to 214929332 bytes and re-start the server. -- MySQL Development Team For technical support contracts, visit https://order.mysql.com/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA <___/ --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
