MySQL Bugs: #4018: log-bin crashes

Bug #4018	log-bin crashes
Submitted:	4 Jun 2004 22:43	Modified:	27 Aug 2004 14:02
Reporter:	Carlos C	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.1	OS:	Linux (Linux Red Hat 9.0)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I am trying to set up the binary log by adding the command 'log-bin' in the my.cnf file.  

How to repeat:
1. I shutdown the server successfully
2. edit the my.cnf file
3. restart the server successfully.
4. The binary log begins to work but after 10-15 secs mysqld crashes.  I have tested this on MySQL Server 4.0.18 and 4.1.1.

Hi, I really need more to be able to repeat this.  We have many users using the binlogs w/o problems in 
all the various versions.

Are you using our binaries.  Are you running out of disk space?  Have you ruled out hardware 
problems?

Hardware Specs: (this is a simple dev machine)
AMD K6-2 533
RAM 256

This is from my.cnf file.
[client]
port=3306
socket=/var/lib/mysql/mysql.sock

[mysqld]
#SETTING VARIABLES FOR QUERY CACHE
query_cache_size=5M
key_buffer_size=8M
table_cache=200
sort_buffer_size=4M

#SETTING VARIABLES FOR INNODB TABLES
innodb_buffer_pool_size=16M
innodb_log_buffer_size=2M

#SETTING VARIABLES FOR LOG FILES
log-slow-queries=dev2_slow_query_log.log 
log=dev2_general_log.log
log-error=dev2_error_log.err

This is from the error log.

040604 14:07:53  InnoDB: Started; log sequence number 0 119475779
mysqld: ready for connections.
Version: '4.1.1-alpha-standard-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306
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=33554432
read_buffer_size=131072
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 864767 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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=0xbfe9f3f8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8089167
0x82da818
0x80d4bd0
0x80d2ab7
0x809c5f4
0x808976d
0x82d7fcc
0x830b8fa
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/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
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.

Sean, 

Could you try with our official x86 linux binaries to rule out any build problems and let me know what 
happens?

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.