MySQL Forums
Forum List  »  Replication

Re: Replication crashes when max_bin_log_size is reached
Posted by: Pär Iwarson
Date: May 16, 2005 04:32PM

I have no let the relay log reach max_bin_log_size limit and let it crash again. This resulted in this error log:

-------------------------------------------------------------------------
-------------------------START ERROR LOG-------------------------------

050516 17:10:05 Could not use ensim-relay-bin for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
050516 17:10:05 next log error: -1 offset: 22 log: ./ensim-relay-bin.025
050516 17:10:05 Error reading relay log event: Error purging processed log
050516 17:10:05 Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0
050516 17:10:05 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'freebsds-bin.020' position 42272395
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=20
max_connections=100
threads_connected=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x40e00440
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbfe5f5d8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8072d44
0x826ca28
0x829571a
0x8294e71
0x825149e
0x82518aa
0x805fbcb
0x807c2fb
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at (nil) is invalid pointer
thd->thread_id=4935
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
050516 17:10:11 mysqld restarted
050516 17:10:11 Warning: Asked for 196608 thread stack, but got 126976
050516 17:10:12 InnoDB: Started
050516 17:10:12 Could not use ensim-relay-bin for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
050516 17:10:12 Failed in open_log() called from init_relay_log_info()
050516 17:10:12 Failed to initialize the master info structure
/usr/sbin/mysqld: ready for connections.
Version: '4.0.23-standard' socket: '/home/virtual/FILESYSTEMTEMPLATE/.mysqlsock/mysql.sock' port: 3306 Official MySQL RPM

---------------------------END ERROR LOG-------------------------------
-------------------------------------------------------------------------

I copied the backtrace into mysqld.stack

I then executed

nm -n /usr/sbin/mysqld > /tmp/mysqld.sym

with the result "No symbols"

also tried

nm -n -D /usr/sbin/mysqld > /tmp/mysqld.sym

with the result "No symbols"

I then executed

resolve_stack_dump -s mysqld.sym -n mysqld.stack

and got the following result:

0x8072d44 + 134688068
0x826ca28 + 136759848
0x829571a + 136927002
0x8294e71 + 136924785
0x825149e + 136647838
0x82518aa + 136648874
0x805fbcb + 134609867
0x807c2fb + 134726395
0x826a1dc + 136749532
0x82a008a + 136970378

I don't know if that is to any help. But no one would be glader than me if this problem is solved.

Regards
Iwarson

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: Replication crashes when max_bin_log_size is reached
3016
May 16, 2005 04:32PM


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.