Created attachment 929585 [details]
full backtrace

Description of problem:
When I try to upgrade database, server crashes.

Version-Release number of selected component (if applicable):
mariadb-server-5.5.38-3.fc20.x86_64

How reproducible:
always

Steps to Reproduce:
1.mysql_upgrade
2.
3.

Actual results:
140821 19:29:05 [ERROR] Build InnoDB index translation table for Table ./roundcubemail/users failed
140821 19:29:05 [ERROR] Table roundcubemail/users contains 2 indexes inside InnoDB, which is different from the number of indexes 3 defined in the MySQL 
140821 19:29:05 [ERROR] Innodb could not find key n:o 1 with name username_index from dict cache for table roundcubemail/users
140821 19:29:05 [ERROR] Table roundcubemail/users contains fewer indexes inside InnoDB than are defined in the MySQL .frm file. Have you mixed up .frm files fro
m different installations? See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html

140821 19:29:05  InnoDB: Assertion failure in thread 140236594571008 in file ha_innodb.cc line 5710
InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED
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.
140821 19:29:05 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 5.5.38-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466712 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f8b6bdf3e90
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 = 0x7f8b60675d80 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f8b6815c27d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7f8b67d74285]
/lib64/libpthread.so.0(+0x324dc0f750)[0x7f8b67491750]
/lib64/libc.so.6(gsignal+0x39)[0x7f8b65c43c39]
/lib64/libc.so.6(abort+0x148)[0x7f8b65c45348]
/usr/libexec/mysqld(+0x6faba0)[0x7f8b67fbbba0]
/usr/libexec/mysqld(+0x706d48)[0x7f8b67fc7d48]
/usr/libexec/mysqld(+0x70b28c)[0x7f8b67fcc28c]
/usr/libexec/mysqld(_ZN7handler18index_read_idx_mapEPhjPKhm16ha_rkey_function+0x33)[0x7f8b67d74823]
/usr/libexec/mysqld(+0x3c27be)[0x7f8b67c837be]
/usr/libexec/mysqld(+0x3c2978)[0x7f8b67c83978]
/usr/libexec/mysqld(+0x3c844b)[0x7f8b67c8944b]
/usr/libexec/mysqld(_ZN4JOIN8optimizeEv+0x795)[0x7f8b67c8d305]
/usr/libexec/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xc8)[0x7f8b67c8f818]
/usr/libexec/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x2db)[0x7f8b67c9030b]
/usr/libexec/mysqld(+0x37daa9)[0x7f8b67c3eaa9]
/usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x44d3)[0x7f8b67c48c03]
/usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x125)[0x7f8b67c4bdb5]
/usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1737)[0x7f8b67c4ddf7]
/usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0x1c2)[0x7f8b67cfe512]
/usr/libexec/mysqld(handle_one_connection+0x4a)[0x7f8b67cfe5ba]
/lib64/libpthread.so.0(+0x324dc07f33)[0x7f8b67489f33]
/lib64/libc.so.6(clone+0x6d)[0x7f8b65d02ded]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f8b34004c68): SELECT * FROM users WHERE user_id = '1'
Connection ID (thread ID): 1
Status: NOT_KILLED


Expected results:
upgrade database, or (at least) no crash

Additional info:
I repeated this several times and got several core files. The above trace could be different from backtrace attached.