MySQL Forums
Forum List  »  Replication

Re: Replication crashes when max_bin_log_size is reached
Posted by: Guilhem Bichot
Date: May 06, 2005 01:59AM

Hello, you both who have the problem!

This is not a known problem, never heard about it. Let's try to debug it a bit:
in your mysql log which you posted in the first message, there is something like
mysqld got signal 11;
"This could be because you hit a bug. It is also possible that this binary
<cut>
Stack range sanity check OK, backtrace follows:
0x8072d44
0x826ca28
0x2d32302d
0x8250f2a
0x80ee218
0x80ef697
0x826a1dc
0x82a008a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it "

Please, could you do the above? I cannot do it myself, it must be done using the exact MySQL binary which crashed. If we had the resolved stack trace, we may have an idea of where in code it had a segfault.
Thanks!

Mr. Guilhem Bichot <guilhem@mysql.com>
MySQL AB, Lead Software Engineer
Bordeaux, France
www.mysql.com

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Replication crashes when max_bin_log_size is reached
2904
May 06, 2005 01:59AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.