[Bug 1378359] [NEW] mysql-server crash when syncing neutron database schema

James Page james.page at ubuntu.com
Tue Oct 7 13:27:02 UTC 2014


Public bug reported:

Version: '5.5.39-0ubuntu4-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
141007 13:18:36  InnoDB: Assertion failure in thread 139656749573888 in file dict0dict.c line 2563
InnoDB: Failing assertion: UT_LIST_GET_LEN(table->referenced_list) == rbt_size(table->referenced_rbt)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:18:36 UTC - mysqld got signal 6 ;
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=8388608
read_buffer_size=131072
max_used_connections=13
max_threads=151
thread_count=13
connection_count=13
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 338508 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f04b1845050
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...
stack_bottom = 7f045ef2de98 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7f04ad8092f0]
/usr/sbin/mysqld(handle_fatal_signal+0x3d4)[0x7f04ad6fad94]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfc90)[0x7f04ac49bc90]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f04abae8d27]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f04abaea418]
/usr/sbin/mysqld(+0x58a76d)[0x7f04ad8bb76d]
/usr/sbin/mysqld(+0x59333d)[0x7f04ad8c433d]
/usr/sbin/mysqld(+0x596507)[0x7f04ad8c7507]
/usr/sbin/mysqld(+0x51ae5d)[0x7f04ad84be5d]
/usr/sbin/mysqld(+0x500e1c)[0x7f04ad831e1c]
/usr/sbin/mysqld(_Z18mysql_rename_tableP10handlertonPKcS2_S2_S2_j+0x123)[0x7f04ad674673]
/usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderb+0x1eb6)[0x7f04ad6782a6]
/usr/sbin/mysqld(_ZN21Alter_table_statement7executeEP3THD+0x48a)[0x7f04ad7edc3a]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x163f)[0x7f04ad61818f]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x160)[0x7f04ad61da60]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1bcd)[0x7f04ad61fd6d]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x176)[0x7f04ad6ac386]
/usr/sbin/mysqld(handle_one_connection+0x41)[0x7f04ad6ac3e1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x80a5)[0x7f04ac4940a5]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f04abbac84d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f0444279920): is an invalid pointer
Connection ID (thread ID): 76
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
141007 13:18:36 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: mysql-server-5.5 5.5.39-0ubuntu4
ProcVersionSignature: User Name 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
Date: Tue Oct  7 13:24:12 2014
Ec2AMI: ami-000000aa
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-00000002
Ec2Ramdisk: ari-00000002
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d..keepme: 
MySQLConf.etc.mysql.conf.d.binlog.cnf: Error: [Errno 13] Permission denied: '/etc/mysql/conf.d/binlog.cnf'
MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLConf.etc.mysql.my.cnf: Error: [Errno 13] Permission denied: '/etc/mysql/my.cnf'
MySQLVarLibDirListing: False
SourcePackage: mysql-5.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ec2-images openstack osci utopic

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.5 in Ubuntu.
https://bugs.launchpad.net/bugs/1378359

Title:
  mysql-server crash when syncing neutron database schema

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1378359/+subscriptions



More information about the Ubuntu-server-bugs mailing list