mysqld on debian-amd64/testing crashing with signal 11
Hi folks,
I've been experiencing a problem with mysql-server-4.1 on two
different amd64 machines, running two different versions of the package.
The errors in the log are similar to http://lists.debian.org/debian-
amd64/2005/03/msg00481.html -- but I don't know if the source of the
segfault is a client QUIT command. I don't think it is.
It's occurred about 10 times in the past 7 days, at seemingly random
intervals. I switched to a second server yesterday afternoon, and
less than 6 hours later mysqld on the new server segfaulted.
The servers get about 300qps on average, about half updates and half
selects.
I turned on query logging after about the third day, despite the
performance hit, and couldn't see any abnormal queries in the logs.
Presumably whatever query that causes the segfault, though, wouldn't
get logged.
Since the mysqld in debian doesn't seem to output a backtrace on
crash, I can't use that for further debugging.
I'm open to any suggestions, and please let me know if there's any
further information I can provide.
Error message:
Jun 22 17:55:18 localhost mysqld[10680]: mysqld got signal 11;
Jun 22 17:55:18 localhost mysqld[10680]: This could be because you
hit a bug. It is also possible that this binary
Jun 22 17:55:18 localhost mysqld[10680]: or one of the libraries it
was linked against is corrupt, improperly built,
Jun 22 17:55:18 localhost mysqld[10680]: or misconfigured. This error
can also be caused by malfunctioning hardware.
Jun 22 17:55:18 localhost mysqld[10680]: We will try our best to
scrape up some info that will hopefully help diagnose
Jun 22 17:55:18 localhost mysqld[10680]: the problem, but since we
have already crashed, something is definitely wrong
Jun 22 17:55:18 localhost mysqld[10680]: and this may fail.
Jun 22 17:55:18 localhost mysqld[10680]:
Jun 22 17:55:18 localhost mysqld[10680]: key_buffer_size=268435456
Jun 22 17:55:18 localhost mysqld[10680]: read_buffer_size=131072
Jun 22 17:55:18 localhost mysqld[10680]: max_used_connections=101
Jun 22 17:55:18 localhost mysqld[10680]: max_connections=100
Jun 22 17:55:18 localhost mysqld[10680]: threads_connected=5
Jun 22 17:55:18 localhost mysqld[10680]: It is possible that mysqld
could use up to
Jun 22 17:55:18 localhost mysqld[10680]: key_buffer_size +
(read_buffer_size + sort_buffer_size)*max_connections = 479743 K
Jun 22 17:55:18 localhost mysqld[10680]: bytes of memory
Jun 22 17:55:18 localhost mysqld[10680]: Hope that's ok; if not,
decrease some variables in the equation.
Jun 22 17:55:18 localhost mysqld[10680]:
Jun 22 17:55:18 localhost mysqld_safe[18891]: Number of processes
running now: 0
Jun 22 17:55:18 localhost mysqld_safe[18893]: restarted
Package versions:
mysql-server-4.1 - 4.1.11-3 and 4.1.11a-4
kernel: 2.6.8-11-amd64-k8-smp
memory: 4GB in one, 2GB in the other
cpus: dual opterons at 1.6ghz
Reply to: