Activity log for bug #896439

Date Who What changed Old value New value Message
2011-11-25 22:23:06 Łukasz Muchlado bug added bug
2012-04-13 13:39:08 Elena Stepanova summary Crash and restart of MariaDB 5.2.9 after running automysqlbackup on ubuntu 10.04 Server started with skip-innodb crashes in mutex_test_and_set on SELECT * FROM INNODB_TABLE_STATS or INNODB_INDEX_STATS
2012-04-13 13:39:25 Elena Stepanova maria: milestone 5.1
2012-04-13 13:39:46 Elena Stepanova bug task added percona-server
2012-04-13 13:44:16 Elena Stepanova summary Server started with skip-innodb crashes in mutex_test_and_set on SELECT * FROM INNODB_TABLE_STATS or INNODB_INDEX_STATS Server started with skip-innodb crashes on SELECT * FROM INNODB_TABLE_STATS or INNODB_INDEX_STATS
2012-04-13 13:48:03 Elena Stepanova tags crash crash xtradb
2012-06-15 05:56:51 Stewart Smith nominated for series percona-server/5.1
2012-06-15 05:56:51 Stewart Smith bug task added percona-server/5.1
2012-06-15 05:56:51 Stewart Smith nominated for series percona-server/5.5
2012-06-15 05:56:51 Stewart Smith bug task added percona-server/5.5
2012-06-15 05:57:00 Stewart Smith percona-server/5.1: status New Fix Committed
2012-06-15 05:57:02 Stewart Smith percona-server/5.5: status New Fix Committed
2012-06-15 05:57:04 Stewart Smith percona-server/5.1: importance Undecided Low
2012-06-15 05:57:07 Stewart Smith percona-server/5.5: importance Undecided Low
2012-06-15 05:57:10 Stewart Smith percona-server/5.1: assignee Stewart Smith (stewart)
2012-06-15 05:57:11 Stewart Smith percona-server/5.5: assignee Stewart Smith (stewart)
2012-06-15 05:59:24 Stewart Smith percona-server/5.1: milestone 5.1.64-13.5
2012-06-15 06:01:19 Launchpad Janitor branch linked lp:~stewart/percona-server/bug896439
2012-06-15 06:02:17 Launchpad Janitor branch linked lp:~stewart/percona-server/5.5-bug896439
2012-06-15 06:48:22 Łukasz Muchlado description System: Ubuntu 10.04 server with all updates running on Linode VPS MariaDB Version: '5.2.9-MariaDB-mariadb105~lucid-log' innodb is disabled default_storage_engine is Maria After installing automysqlbackup from repo and running it manualy information_schema is backed without problems but next database (wordpress) causes problems. MariaDB crashes and is restarted. Problem is repeatable. On other VPS with symilar system but other MariaDB version (5.3.2) and some configuration differences everything is running without problem. Syslog fragment: Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [ERROR] mysqld got signal 11 ; Nov 25 22:52:26 s3 mysqld: This could be because you hit a bug. It is also possible that this binary Nov 25 22:52:26 s3 mysqld: or one of the libraries it was linked against is corrupt, improperly built, Nov 25 22:52:26 s3 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Nov 25 22:52:26 s3 mysqld: We will try our best to scrape up some info that will hopefully help diagnose Nov 25 22:52:26 s3 mysqld: the problem, but since we have already crashed, something is definitely wrong Nov 25 22:52:26 s3 mysqld: and this may fail. Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: key_buffer_size=0 Nov 25 22:52:26 s3 mysqld: read_buffer_size=2097152 Nov 25 22:52:26 s3 mysqld: max_used_connections=1 Nov 25 22:52:26 s3 mysqld: max_threads=102 Nov 25 22:52:26 s3 mysqld: threads_connected=1 Nov 25 22:52:26 s3 mysqld: It is possible that mysqld could use up to Nov 25 22:52:26 s3 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 627451 K Nov 25 22:52:26 s3 mysqld: bytes of memory Nov 25 22:52:26 s3 mysqld: Hope that's ok; if not, decrease some variables in the equation. Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: Thread pointer: 0xb86b8128 Nov 25 22:52:26 s3 mysqld: Attempting backtrace. You can use the following information to find out Nov 25 22:52:26 s3 mysqld: where mysqld died. If you see no messages after this, something went Nov 25 22:52:26 s3 mysqld: terribly wrong... Nov 25 22:52:26 s3 mysqld: stack_bottom = 0xa8d6436c thread_stack 0x30000 Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2d) [0xb75c131d] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(handle_segfault+0x4d4) [0xb71a9bd4] Nov 25 22:52:26 s3 mysqld: [0xf57fe400] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x1e3) [0xb72d68d3] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x5d3) [0xb722fae3] Nov 25 22:52:26 s3 mysqld: /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*)+0x102) [0xb7231b12] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x164) [0xb7232544] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(+0x25618c) [0xb71b618c] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0xfe7) [0xb71b98c7] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2bf) [0xb71c0e9f] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x101d) [0xb71c239d] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(do_command(THD*)+0x10b) [0xb71c2f7b] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(handle_one_connection+0x168) [0xb71b1758] Nov 25 22:52:26 s3 mysqld: /lib/tls/i686/cmov/libpthread.so.0(+0x596e) [0xb6d0996e] Nov 25 22:52:26 s3 mysqld: /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb6b52a4e] Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: Trying to get some variables. Nov 25 22:52:26 s3 mysqld: Some pointers may be invalid and cause the dump to abort. Nov 25 22:52:26 s3 mysqld: Query (0xb880eba0): SELECT /*!40001 SQL_NO_CACHE */ * FROM `INNODB_TABLE_STATS` Nov 25 22:52:26 s3 mysqld: Connection ID (thread ID): 2 Nov 25 22:52:26 s3 mysqld: Status: NOT_KILLED Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Nov 25 22:52:26 s3 mysqld: information that should help you find out what is causing the crash. Nov 25 22:52:26 s3 mysqld_safe: Number of processes running now: 0 Nov 25 22:52:26 s3 mysqld_safe: mysqld restarted Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] PrimeBase XT (PBXT) Engine 1.0.11-7 Pre-GA loaded... Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] The server was not shutdown correctly, recovery required Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Plugin 'InnoDB' is disabled. Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Recovering after a crash using /var/log/mysql/mariadb-bin Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Starting crash recovery... Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Crash recovery finished. Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Event Scheduler: Loaded 0 events Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] /usr/sbin/mysqld: ready for connections. Nov 25 22:52:26 s3 mysqld: Version: '5.2.9-MariaDB-mariadb105~lucid-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (MariaDB - http://mariadb.com/) System: Ubuntu 10.04 server with all updates running on Linode VPS MariaDB Version: '5.2.9-MariaDB-mariadb105~lucid-log' innodb is disabled (skip-innodb in config) default_storage_engine is Maria After installing automysqlbackup from repo and running it manualy, MariaDB crashes and is restarted while backing up information_schema. Problem is repeatable. Syslog fragment: Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [ERROR] mysqld got signal 11 ; Nov 25 22:52:26 s3 mysqld: This could be because you hit a bug. It is also possible that this binary Nov 25 22:52:26 s3 mysqld: or one of the libraries it was linked against is corrupt, improperly built, Nov 25 22:52:26 s3 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Nov 25 22:52:26 s3 mysqld: We will try our best to scrape up some info that will hopefully help diagnose Nov 25 22:52:26 s3 mysqld: the problem, but since we have already crashed, something is definitely wrong Nov 25 22:52:26 s3 mysqld: and this may fail. Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: key_buffer_size=0 Nov 25 22:52:26 s3 mysqld: read_buffer_size=2097152 Nov 25 22:52:26 s3 mysqld: max_used_connections=1 Nov 25 22:52:26 s3 mysqld: max_threads=102 Nov 25 22:52:26 s3 mysqld: threads_connected=1 Nov 25 22:52:26 s3 mysqld: It is possible that mysqld could use up to Nov 25 22:52:26 s3 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 627451 K Nov 25 22:52:26 s3 mysqld: bytes of memory Nov 25 22:52:26 s3 mysqld: Hope that's ok; if not, decrease some variables in the equation. Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: Thread pointer: 0xb86b8128 Nov 25 22:52:26 s3 mysqld: Attempting backtrace. You can use the following information to find out Nov 25 22:52:26 s3 mysqld: where mysqld died. If you see no messages after this, something went Nov 25 22:52:26 s3 mysqld: terribly wrong... Nov 25 22:52:26 s3 mysqld: stack_bottom = 0xa8d6436c thread_stack 0x30000 Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2d) [0xb75c131d] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(handle_segfault+0x4d4) [0xb71a9bd4] Nov 25 22:52:26 s3 mysqld: [0xf57fe400] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x1e3) [0xb72d68d3] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x5d3) [0xb722fae3] Nov 25 22:52:26 s3 mysqld: /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*)+0x102) [0xb7231b12] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x164) [0xb7232544] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(+0x25618c) [0xb71b618c] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0xfe7) [0xb71b98c7] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2bf) [0xb71c0e9f] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x101d) [0xb71c239d] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(do_command(THD*)+0x10b) [0xb71c2f7b] Nov 25 22:52:26 s3 mysqld: /usr/sbin/mysqld(handle_one_connection+0x168) [0xb71b1758] Nov 25 22:52:26 s3 mysqld: /lib/tls/i686/cmov/libpthread.so.0(+0x596e) [0xb6d0996e] Nov 25 22:52:26 s3 mysqld: /lib/tls/i686/cmov/libc.so.6(clone+0x5e) [0xb6b52a4e] Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: Trying to get some variables. Nov 25 22:52:26 s3 mysqld: Some pointers may be invalid and cause the dump to abort. Nov 25 22:52:26 s3 mysqld: Query (0xb880eba0): SELECT /*!40001 SQL_NO_CACHE */ * FROM `INNODB_TABLE_STATS` Nov 25 22:52:26 s3 mysqld: Connection ID (thread ID): 2 Nov 25 22:52:26 s3 mysqld: Status: NOT_KILLED Nov 25 22:52:26 s3 mysqld: Nov 25 22:52:26 s3 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Nov 25 22:52:26 s3 mysqld: information that should help you find out what is causing the crash. Nov 25 22:52:26 s3 mysqld_safe: Number of processes running now: 0 Nov 25 22:52:26 s3 mysqld_safe: mysqld restarted Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] PrimeBase XT (PBXT) Engine 1.0.11-7 Pre-GA loaded... Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] The server was not shutdown correctly, recovery required Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Plugin 'InnoDB' is disabled. Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Recovering after a crash using /var/log/mysql/mariadb-bin Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Starting crash recovery... Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Crash recovery finished. Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] Event Scheduler: Loaded 0 events Nov 25 22:52:26 s3 mysqld: 111125 22:52:26 [Note] /usr/sbin/mysqld: ready for connections. Nov 25 22:52:26 s3 mysqld: Version: '5.2.9-MariaDB-mariadb105~lucid-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (MariaDB - http://mariadb.com/)
2012-06-18 01:45:09 Stewart Smith percona-server/5.5: milestone 5.5.25-27.0
2012-06-18 07:21:36 Stewart Smith percona-server/5.5: status Fix Committed Fix Released
2012-07-02 02:54:34 Stewart Smith percona-server/5.1: status Fix Committed In Progress
2012-07-02 02:54:37 Stewart Smith percona-server/5.1: status In Progress Fix Released
2012-08-25 23:22:41 Elena Stepanova nominated for series maria/5.1
2012-08-25 23:22:41 Elena Stepanova bug task added maria/5.1
2012-08-25 23:22:41 Elena Stepanova nominated for series maria/5.2
2012-08-25 23:22:41 Elena Stepanova bug task added maria/5.2
2012-08-25 23:22:41 Elena Stepanova nominated for series maria/5.5
2012-08-25 23:22:41 Elena Stepanova bug task added maria/5.5
2012-08-25 23:22:41 Elena Stepanova nominated for series maria/5.3
2012-08-25 23:22:41 Elena Stepanova bug task added maria/5.3
2012-08-25 23:23:20 Elena Stepanova maria/5.5: status New Fix Committed
2012-08-25 23:23:28 Elena Stepanova maria/5.5: milestone 5.5
2012-08-25 23:23:32 Elena Stepanova maria/5.3: milestone 5.3
2012-08-25 23:23:36 Elena Stepanova maria/5.2: milestone 5.2
2012-08-25 23:23:40 Elena Stepanova maria/5.1: milestone 5.1
2012-08-25 23:23:52 Elena Stepanova maria: milestone 5.1