Bug #67079 Server crash after upgrade from 5.1.41
Submitted: 4 Oct 2012 12:42 Modified: 6 Nov 2012 1:51
Reporter: Reinis Rozitis Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.6.7 OS:Linux (OpenSuse 11.1)
Assigned to: CPU Architecture:Any

[4 Oct 2012 12:42] Reinis Rozitis
Description:
After upgrading from 5.1.41 to 5.6.7-rc the server segfaults at startup (mysql_safe keeps it restarting in a loop).

121004 14:50:46 mysqld_safe Starting mysqld daemon with databases from /data/mysql
121004 14:50:47 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
121004 14:50:47 [Note] Plugin 'FEDERATED' is disabled.
121004 14:50:47 [Warning] option 'innodb-status-file': boolean value 'innodb_status.file' wasn't recognized. Set to OFF.
121004 14:50:47 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
121004 14:50:47 InnoDB: The InnoDB memory heap is disabled
121004 14:50:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121004 14:50:47 InnoDB: Compressed tables use zlib 1.2.3
121004 14:50:47 InnoDB: Using Linux native AIO
121004 14:50:47 InnoDB: CPU supports crc32 instructions
121004 14:50:47 InnoDB: Initializing buffer pool, size = 10.0G
121004 14:50:48 InnoDB: Completed initialization of buffer pool
121004 14:50:48 InnoDB: highest supported file format is Barracuda.
121004 14:50:48 [Warning] InnoDB: Allocated tablespace 340038, old maximum was 0
121004 14:50:48 InnoDB: 128 rollback segment(s) are active.
121004 14:50:48 InnoDB: Waiting for the background threads to start
121004 14:50:48 InnoDB: 1.2.7 started; log sequence number 7162585765877
121004 14:50:48 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: bd3ad534-0e19-11e2-9979-d8d385a51c76.
121004 14:50:48 [Note] Server hostname (bind-address): '*'; port: 3306
121004 14:50:48 [Note] IPv6 is not available.
121004 14:50:48 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121004 14:50:48 [Note] Server socket created on IP: '0.0.0.0'.
11:50:48 UTC - 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.

key_buffer_size=209715200
read_buffer_size=4194304
max_used_connections=0
max_threads=10000
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 82258003 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x122640a0
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 = 7fff59086f48 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8b47d5]
/usr/sbin/mysqld(handle_fatal_signal+0x401)[0x64b181]
/lib64/libpthread.so.0[0x7f7250c5ca90]
/usr/sbin/mysqld(_Z9get_fieldP11st_mem_rootP5Field+0x4c)[0x74bf0c]
/usr/sbin/mysqld(_Z10acl_reloadP3THD+0x10d1)[0x66e3a1]
/usr/sbin/mysqld(_Z8acl_initb+0x111)[0x671d51]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x795)[0x584225]
/lib64/libc.so.6(__libc_start_main+0xe6)[0x7f724f94d586]
/usr/sbin/mysqld(__gxx_personality_v0+0xe2)[0x57745a]

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

Downgrading back to 5.1.41 works fine.

How to repeat:
Upgrade to 5.6.7-rc.
[6 Oct 2012 1:51] MySQL Verification Team
Thank you for the bug report. Are you read and followed the Manual's instructions?

http://dev.mysql.com/doc/refman/5.6/en/upgrading.html

Thanks.
[7 Nov 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".