Description:
"binlog dump" causes the crash of mysql after approximately one minute or at the time of operations modifying the bases on the master during the sending of data towards the slave, mysql restarded automatically.
OS: RHEL4 update 4(x86_64)
Memory : 4Go
2 CPU: intel xeon dual core 1,60
result of resolve_stackd_dump :
0x746f6f72 __stop___libc_freeres_ptrs + 1943527618
0x617571696c706572 __stop___libc_freeres_ptrs + 1809372866
myc.cnf:
[mysqld]
socket=/tmp/mysql.sock
user=mysql
skip-innodb
language=/usr/local/mysql/share/mysql/french
set-variable=key_buffer_size=256M
set-variable=table_cache=1024
set-variable=join_buffer_size=4M
set-variable=read_buffer_size=4M
set-variable=sort_buffer_size=4M
set-variable=thread_stack=262144
set-variable = ft_min_word_len=3
set-variable = tmp_table_size=64M
# replication maitre
log-bin
server-id = 2
[mysqld_safe]
socket=/tmp/mysql.sock
err-log=/var/log/mysql/mysqld.log
pid-file=/var/mysql/mysqld.pid
extract of file mysqld.log:
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=402653184
read_buffer_size=4190208
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1212015 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x9e9540
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=0x2ae021242d28, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x617571696c706572
New value of fp=0x9e9540 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=2
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
070110 04:22:10 mysqld restarted
/usr/local/mysql/libexec/mysqld: Prêt pour des connections Source distribution
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=402653184
read_buffer_size=4190208
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1212015 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x9e9540
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=0x2ac7343d5d28, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x617571696c706572
New value of fp=0x9e9540 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=2
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
070110 04:26:14 mysqld restarted
How to repeat:
"binlog dump" causes the crash of mysql after approximately one minute or at the time of operations modifying the bases on the master during the sending of data towards the slave, mysql restarded automatically.
OS: RHEL4 update 4(x86_64)
Memory : 4Go
2 CPU: intel xeon dual core 1,60
result of resolve_stackd_dump :
0x746f6f72 __stop___libc_freeres_ptrs + 1943527618
0x617571696c706572 __stop___libc_freeres_ptrs + 1809372866
myc.cnf:
[mysqld]
socket=/tmp/mysql.sock
user=mysql
skip-innodb
language=/usr/local/mysql/share/mysql/french
set-variable=key_buffer_size=256M
set-variable=table_cache=1024
set-variable=join_buffer_size=4M
set-variable=read_buffer_size=4M
set-variable=sort_buffer_size=4M
set-variable=thread_stack=262144
set-variable = ft_min_word_len=3
set-variable = tmp_table_size=64M
# replication maitre
log-bin
server-id = 2
[mysqld_safe]
socket=/tmp/mysql.sock
err-log=/var/log/mysql/mysqld.log
pid-file=/var/mysql/mysqld.pid
extract of file mysqld.log:
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=402653184
read_buffer_size=4190208
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1212015 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x9e9540
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=0x2ae021242d28, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x617571696c706572
New value of fp=0x9e9540 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=2
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
070110 04:22:10 mysqld restarted
/usr/local/mysql/libexec/mysqld: Prêt pour des connections Source distribution
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=402653184
read_buffer_size=4190208
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1212015 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x9e9540
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=0x2ac7343d5d28, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x617571696c706572
New value of fp=0x9e9540 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=2
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
070110 04:26:14 mysqld restarted
