[Bug 493325] [NEW] mysqld crashes with large key_buffer (25G)

Brian Gehrich brian-launchpad.net at rustproof.org
Sun Dec 6 21:56:07 GMT 2009

Public bug reported:

I am running mysql on hardy (x86_64) with mysql-server-5.0 version
5.0.51a-3 ubuntu5.4.  We have running this on aserver with 128GB of ram.
When we try to set key_buffer to 25GB, mysqld crashes with the error:

091206 16:41:45 - 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.

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

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...
frame pointer is NULL, did you compile with
-fomit-frame-pointer? Aborting backtrace!
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.

** Affects: mysql-dfsg-5.0 (Ubuntu)
     Importance: Undecided
         Status: New

mysqld crashes with large key_buffer (25G)
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.

More information about the Ubuntu-server-bugs mailing list