Hi,

I have the exact same problem with 5.0.18, on INSERT DELAYED server crashes
and restarts, without it it seems to be working fine.

[EMAIL PROTECTED]:~$ uname -a
Linux elak 2.6.14.3-grsec #1 PREEMPT Fri Dec 2 14:59:02 CET 2005 i686 GNU/Linux

[EMAIL PROTECTED]:~$ dpkg -l mysql-server-5*
ii  mysql-server-5 5.0.18-1       mysql database server binaries

Jan  5 03:56:04 elak mysqld[20351]: mysqld got signal 11;
Jan  5 03:56:04 elak mysqld[20351]: This could be because you hit a bug. It is 
also possible that this binary
Jan  5 03:56:04 elak mysqld[20351]: or one of the libraries it was linked 
against is corrupt, improperly built,
Jan  5 03:56:04 elak mysqld[20351]: or misconfigured. This error can also be 
caused by malfunctioning hardware.
Jan  5 03:56:04 elak mysqld[20351]: We will try our best to scrape up some info 
that will hopefully help diagnose
Jan  5 03:56:04 elak mysqld[20351]: the problem, but since we have already 
crashed, something is definitely wrong
Jan  5 03:56:04 elak mysqld[20351]: and this may fail.
Jan  5 03:56:04 elak mysqld[20351]: 
Jan  5 03:56:04 elak mysqld[20351]: key_buffer_size=16777216
Jan  5 03:56:04 elak mysqld[20351]: read_buffer_size=131072
Jan  5 03:56:04 elak mysqld[20351]: max_used_connections=9
Jan  5 03:56:04 elak mysqld[20351]: max_connections=100
Jan  5 03:56:04 elak mysqld[20351]: threads_connected=2
Jan  5 03:56:04 elak mysqld[20351]: It is possible that mysqld could use up to 
Jan  5 03:56:04 elak mysqld[20351]: key_buffer_size + (read_buffer_size + 
sort_buffer_size)*max_connections = 233983 K
Jan  5 03:56:04 elak mysqld[20351]: bytes of memory
Jan  5 03:56:04 elak mysqld[20351]: Hope that's ok; if not, decrease some 
variables in the equation.
Jan  5 03:56:04 elak mysqld[20351]: 
Jan  5 03:56:04 elak mysqld[20351]: thd=0x8ae14d8
Jan  5 03:56:04 elak mysqld[20351]: Attempting backtrace. You can use the 
following information to find out
Jan  5 03:56:04 elak mysqld[20351]: where mysqld died. If you see no messages 
after this, something went
Jan  5 03:56:04 elak mysqld[20351]: terribly wrong...
Jan  5 03:56:04 elak mysqld[20351]: Cannot determine thread, fp=0x9cae5f98, 
backtrace may not be correct.
Jan  5 03:56:04 elak mysqld[20351]: Stack range sanity check OK, backtrace 
follows:
Jan  5 03:56:04 elak mysqld[20351]: 0x818c8fb
Jan  5 03:56:04 elak mysqld[20351]: 0xa0b23668
Jan  5 03:56:04 elak mysqld[20351]: (nil)
Jan  5 03:56:04 elak mysqld[20351]: 0x81ecbef
Jan  5 03:56:04 elak mysqld[20351]: 0x81a1f7c
Jan  5 03:56:04 elak mysqld[20351]: 0x81a4d58
Jan  5 03:56:04 elak mysqld[20351]: 0x81a5319
Jan  5 03:56:04 elak mysqld[20351]: 0x81a62fd
Jan  5 03:56:04 elak mysqld[20351]: 0x81a6ba5
Jan  5 03:56:04 elak mysqld[20351]: 0xa0b1dcfd
Jan  5 03:56:04 elak mysqld[20351]: 0xa096019e
Jan  5 03:56:04 elak mysqld[20351]: New value of fp=(nil) failed sanity check, 
terminating stack trace!
Jan  5 03:56:04 elak mysqld[20351]: Please read 
http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow 
instructions on how to resolve the stack trace. Resolved
Jan  5 03:56:04 elak mysqld[20351]: stack trace is much more helpful in 
diagnosing the problem, so please do 
Jan  5 03:56:04 elak mysqld[20351]: resolve it
Jan  5 03:56:04 elak mysqld[20351]: Trying to get some variables.
Jan  5 03:56:04 elak mysqld[20351]: Some pointers may be invalid and cause the 
dump to abort...
Jan  5 03:56:04 elak mysqld[20351]: thd->query at 0x8b05c68 = INSERT DELAYED 
INTO syslog (facility, priority,  date, time, host, message) 
VALUES('daemon','err', '2006-01-05', '03:50:11', 'elak', 'om_mysql_write: 46 
messages were lost due to lack of connection')
Jan  5 03:56:04 elak mysqld[20351]: thd->thread_id=24

/f

Attachment: pgpK8BgtKPQEu.pgp
Description: PGP signature

  • Bug#341705: Fredrik Soderblom

Reply via email to