Comment 21 for bug 585688

Revision history for this message
John Rosauer (john-rosauer) wrote : Re: [Bug 585688] Re: maridb crashes in federatedx code

Hi,

I just upgraded one of the slaves to MariaDB1.47, the latest, and got it to
crash. It only crashes when using the MySQL Administrator GUI to query the
tables.

The debug with this new version provides better information, I think. See
below.

All the Federated tables point to the same database. Here is an example:

CREATE TABLE `IAUTASS` (
  `O8IMNB` decimal(9,0) NOT NULL,
  `O8INNB` decimal(3,0) NOT NULL,
  `O8AFNB` decimal(9,0) NOT NULL,
  `O8EAST` char(1) COLLATE latin1_general_cs NOT NULL,
  `O8EBST` char(1) COLLATE latin1_general_cs NOT NULL,
  `O8ECST` char(1) COLLATE latin1_general_cs NOT NULL,
  `O8EDST` char(1) COLLATE latin1_general_cs NOT NULL,
  `O8BANR` decimal(9,0) NOT NULL,
  `O8A3NR` decimal(9,0) NOT NULL,
  `O8C7NR` decimal(9,2) NOT NULL,
  `O8DCNR` decimal(3,0) NOT NULL,
  `O8C8NR` decimal(9,0) NOT NULL,
  `O8CJNR` decimal(3,0) NOT NULL,
  `O8IINB` decimal(9,0) NOT NULL,
  `O8BBTM` char(10) COLLATE latin1_general_cs NOT NULL,
  `O8BGD8` decimal(7,0) NOT NULL,
  `O8DYD8` decimal(6,0) NOT NULL
) ENGINE=FEDERATED DEFAULT CHARSET=latin1 COLLATE=latin1_general_cs
CONNECTION='mysql://DSLMIINT:mylmiint@au-db-syd030:3306/comdata/IAUTASS';

regards,
John

100617 12:56:38 [ERROR] 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=402653184
read_buffer_size=2097152
max_used_connections=3
max_threads=153
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
1021497 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x5ef53c0
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 = 0x40d2a100 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2e) [0x960afe]
/usr/sbin/mysqld(handle_segfault+0x353) [0x5e0ba3]
/lib64/libpthread.so.0 [0x3e35c0eb10]
/usr/sbin/mysqld(federatedx_txn::acquire(st_federatedx_share*, bool,
federatedx_io**)+0x79) [0x7975e9]
/usr/sbin/mysqld(ha_federatedx::info(unsigned int)+0x1ce) [0x79266e]
/usr/sbin/mysqld [0x6eab3c]
/usr/sbin/mysqld(get_all_tables(THD*, TABLE_LIST*, Item*)+0x8a1) [0x6ee2c1]
/usr/sbin/mysqld(get_schema_tables_result(JOIN*,
enum_schema_table_state)+0x1d1) [0x6e6b51]
/usr/sbin/mysqld(JOIN::exec()+0x3ff) [0x65db9f]
/usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int,
List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*,
unsigned long long, select_result*, st_select_lex_unit*,
st_select_lex*)+0x14e) [0x65fbfe]
/usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned
long)+0x167) [0x6604f7]
/usr/sbin/mysqld [0x5ed110]
/usr/sbin/mysqld(mysql_execute_command(THD*)+0x739) [0x5f04e9]
/usr/sbin/mysqld(mysql_parse(THD*, char const*, unsigned int, char
const**)+0x1e5) [0x5f5ae5]
/usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned
int)+0x9e6) [0x5f64e6]
/usr/sbin/mysqld(do_command(THD*)+0xe6) [0x5f7136]
/usr/sbin/mysqld(handle_one_connection+0x9e) [0x5e970e]
/lib64/libpthread.so.0 [0x3e35c0673d]
/lib64/libc.so.6(clone+0x6d) [0x3e350d3d1d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x66d15a8 = SHOW TABLE STATUS
thd->thread_id=668
thd->killed=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.