Bug #55324 crash on startup: mysqld got signal 11
Submitted: 16 Jul 2010 19:30 Modified: 18 Jul 2010 11:17
Reporter: Jason Pollentier Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.1.41-3ubuntu12.3 OS:Linux (Ubuntu 10.04 x64 (desktop))
Assigned to: CPU Architecture:Any
Tags: crash

[16 Jul 2010 19:30] Jason Pollentier
Description:
Yesterday, mysql abruptly quit working, but repaired itself. I'll attach logs for this (mysql-100715.log).

It worked normally for several hours after this. This morning, it was crashing on certain queries consistently, but others would work OK. See 'Console Queries' in the Private Notes, and the attached log (mysql-100716-console.log). 

Now, it crashes immediately every time I try to connect. The snippets in the attached log file (mysql-100716.log) each occur hundreds of times in my logs.

Maybe my data files are just corrupt, but I don't see errors pointing to that.

How to repeat:
It just started... Here's my my.cnf. The only thing that might've changed are the buffer and cache sizes. I have 6GB RAM in this machine...

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port		= 3306
socket		= /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket		= /var/run/mysqld/mysqld.sock
nice		= 0

[mysqld]
#
# * Basic Settings
#

#
# * IMPORTANT
#   If you make changes to these settings and your system uses apparmor, you may
#   also need to also adjust /etc/apparmor.d/usr.sbin.mysqld.
#

user		= mysql
socket		= /var/run/mysqld/mysqld.sock
port		= 3306
basedir		= /usr
datadir		= /var/lib/mysql
tmpdir		= /tmp
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address		= 127.0.0.1
#
# * Fine Tuning
#
key_buffer		= 64M
max_allowed_packet	= 64M
thread_stack		= 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit	= 16M
query_cache_size        = 256M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1

log_error                = /var/log/mysql/error.log

# Here you can see queries with especially long duration
#log_slow_queries	= /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id		= 1
#log_bin			= /var/log/mysql/mysql-bin.log
expire_logs_days	= 10
max_binlog_size         = 100M
#binlog_do_db		= include_database_name
#binlog_ignore_db	= include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

[mysqldump]
quick
quote-names
max_allowed_packet	= 16M

[mysql]
#no-auto-rehash	# faster start of mysql but no tab completition

[isamchk]
key_buffer		= 16M

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
[16 Jul 2010 19:31] Jason Pollentier
Logs from 7-15. Server seemed to recover after these.

Attachment: mysql-100715.log (text/x-log), 21.27 KiB.

[16 Jul 2010 19:32] Jason Pollentier
Logs from 7-16. Mysql doesn't stay alive long enough to accept connections.

Attachment: mysql-100716.log (text/x-log), 5.21 KiB.

[16 Jul 2010 19:33] Jason Pollentier
For awhile, some queries worked, others crashed the connection: Log for the crash.

Attachment: mysql-100716-console.log (text/x-log), 2.80 KiB.

[17 Jul 2010 7:33] Valeriy Kravchuk
I see different crashes in the log, but let's start with those related to the League table. Please, send SHOW CREATE TABLE results for it and code of that SignupsOpen() function.

Can you try to upgrade to 5.1.48 and check if that prevents crashes?
[17 Jul 2010 20:47] Jason Pollentier
I removed, cleaned, and re-installed mysql from ubuntu repositories, then rebuilt my database. It works fine now, which makes me think it was data file corruption. Do you still want my schema and function definitions?
[18 Jul 2010 11:17] Valeriy Kravchuk
OK, then let's assume this problem was not a result of any bug in MySQL code.