[MDEV-19037] Crashing on adding index / index name could not added again in same tablespace - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Duplicate
Affects Version/s: 10.1.37, 10.0.38
Fix Version/s: N/A
Component/s: Data Definition - Alter Table, Data types
Labels:
None
Environment:
Debian GNU/Linux 8.11 (jessie)
Debian GNU/Linux 9.8 (stretch)

Description

Hello,

we have got a problem with two (Magento 1.x) shop systems on two different hardware servers and two different MariaDB versions. From time to time - we can't reproduce it step by step - we are unable to add an INDEX to a table. We get an error, that it already exists, but it doesnt:

MariaDB [project_mage]> SELECT    constraint_name,   table_name FROM    information_schema.table_constraints  WHERE    constraint_type = 'FOREIGN KEY'    AND table_schema = DATABASE()    AND constraint_name LIKE 'FK_CAT_PRD_FLAT_%' ORDER BY    constraint_name;

+------------------------------------------------+------------------------+

| constraint_name                                | table_name             |

+------------------------------------------------+------------------------+

| FK_CAT_PRD_FLAT_1_ENTT_ID_CAT_PRD_ENTT_ENTT_ID | catalog_product_flat_1 |

| FK_CAT_PRD_FLAT_3_ENTT_ID_CAT_PRD_ENTT_ENTT_ID | catalog_product_flat_3 |

+------------------------------------------------+------------------------+

2 rows in set (0.02 sec)

MariaDB [project_mage]> ALTER TABLE `catalog_product_flat_2` ADD CONSTRAINT `FK_CAT_PRD_FLAT_2_ENTT_ID_CAT_PRD_ENTT_ENTT_ID` FOREIGN KEY (`entity_id`) REFERENCES `catalog_product_entity` (`entity_id`) ON DELETE CASCADE ON UPDATE CASCADE;

ERROR 1005 (HY000): Can't create table `project_mage`.`#sql-5c4b_29c` (errno: 121 "Duplicate key on write or update")

MariaDB [project_mage]> ALTER TABLE `catalog_product_flat_2` ADD CONSTRAINT `FK_CAT_PRD_FLAT_1234567_TEST` FOREIGN KEY (`entity_id`) REFERENCES `catalog_product_entity` (`entity_id`) ON DELETE CASCADE ON UPDATE CASCADE;

Query OK, 1361 rows affected (0.21 sec)

Records: 1361  Duplicates: 0  Warnings: 0

MariaDB [project_mage]> SELECT    constraint_name,   table_name FROM    information_schema.table_constraints  WHERE    constraint_type = 'FOREIGN KEY'    AND table_schema = DATABASE()    AND constraint_name LIKE 'FK_CAT_PRD_FLAT_%' ORDER BY    constraint_name;

+------------------------------------------------+------------------------+

| constraint_name                                | table_name             |

+------------------------------------------------+------------------------+

| FK_CAT_PRD_FLAT_1234567_TEST                   | catalog_product_flat_2 |

| FK_CAT_PRD_FLAT_1_ENTT_ID_CAT_PRD_ENTT_ENTT_ID | catalog_product_flat_1 |

| FK_CAT_PRD_FLAT_3_ENTT_ID_CAT_PRD_ENTT_ENTT_ID | catalog_product_flat_3 |

+------------------------------------------------+------------------------+

3 rows in set (0.02 sec)

MariaDB [project_mage]> SHOW ENGINE INNODB STATUS

    -> ;

.....

------------------------

LATEST FOREIGN KEY ERROR

------------------------

2019-02-26 11:34:00 7f525ad33700 Error in foreign key constraint creation for table `project_mage`.`#sql-5c4b_29c`.

A foreign key constraint of name `project_mage`.`FK_CAT_PRD_FLAT_2_ENTT_ID_CAT_PRD_ENTT_ENTT_ID`

already exists. (Note that internally InnoDB adds 'databasename'

in front of the user-defined constraint name.)

Note that InnoDB's FOREIGN KEY system tables store

constraint names as case-insensitive, with the

MySQL standard latin1_swedish_ci collation. If you

create tables or databases whose names differ only in

the character case, then collisions in constraint

names can occur. Workaround: name your constraints

explicitly with unique names.

Failed query:

ALTER TABLE `catalog_product_flat_2` ADD CONSTRAINT `FK_CAT_PRD_FLAT_2_ENTT_ID_CAT_PRD_ENTT_ENTT_ID` FOREIGN KEY (`entity_id`) REFERENCES `catalog_product_entity` (`entity_id`) ON DELETE CASCADE ON UPDATE CASCADE;

Adding the index with another name works. The only solution to re-add the original INDEX name is to dump the database into a new database name and to use the new one than. The old tablespace has to be removed then.

In one case we were able to get more information from the log where the bug happened (so that the index disappeared and couldn't get added anymore):

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: Warning: Index PRIMARY points to table project_magento/catalog_product_flat_8 and ib_table project_magento/#sql-43c_464b3e statistics is initialized 1 but index table project_magento/catalog_product_flat_8 initialized 1 mysql table is #sql-43c_464b3e. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Error] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_TYPE_ID for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name PRIMARY for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_TYPE_ID for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_ATTRIBUTE_SET_ID for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_HT_POSITION for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_NAME for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_PRICE for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_STATUS for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_10_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_8_HT_GEWICHT for table project_magento/#sql-43c_464b3e

Mär 21 13:21:17 server3 mysqld[1085]: 2019-03-21 13:21:17 7ff0ee8a8700 InnoDB: Assertion failure in thread 140672770934528 in file ha_innodb.cc line 9040

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: Failing assertion: ut_strcmp(index->name, key->name) == 0

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: We intentionally generate a memory trap.

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: If you get repeated assertion failures or crashes, even

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: immediately after the mysqld startup, there may be

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: corruption in the InnoDB tablespace. Please refer to

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

Mär 21 13:21:17 server3 mysqld[1085]: InnoDB: about forcing recovery.

Mär 21 13:21:17 server3 mysqld[1085]: 190321 13:21:17 [ERROR] mysqld got signal 6 ;

Mär 21 13:21:17 server3 mysqld[1085]: This could be because you hit a bug. It is also possible that this binary

Mär 21 13:21:17 server3 mysqld[1085]: or one of the libraries it was linked against is corrupt, improperly built,

Mär 21 13:21:17 server3 mysqld[1085]: or misconfigured. This error can also be caused by malfunctioning hardware.

Mär 21 13:21:17 server3 mysqld[1085]:

Mär 21 13:21:17 server3 mysqld[1085]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

Mär 21 13:21:17 server3 mysqld[1085]:

Mär 21 13:21:17 server3 mysqld[1085]: We will try our best to scrape up some info that will hopefully help

Mär 21 13:21:17 server3 mysqld[1085]: diagnose the problem, but since we have already crashed,

Mär 21 13:21:17 server3 mysqld[1085]: something is definitely wrong and this may fail.

Mär 21 13:21:17 server3 mysqld[1085]:

Mär 21 13:21:17 server3 mysqld[1085]: Server version: 10.0.38-MariaDB-0+deb8u1

Mär 21 13:21:17 server3 mysqld[1085]: key_buffer_size=25165824

Mär 21 13:21:17 server3 mysqld[1085]: read_buffer_size=131072

Mär 21 13:21:17 server3 mysqld[1085]: max_used_connections=53

Mär 21 13:21:17 server3 mysqld[1085]: max_threads=153

Mär 21 13:21:17 server3 mysqld[1085]: thread_count=3

Mär 21 13:21:17 server3 mysqld[1085]: It is possible that mysqld could use up to

Mär 21 13:21:17 server3 mysqld[1085]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 360522 K bytes of memory

Mär 21 13:21:17 server3 mysqld[1085]: Hope that's ok; if not, decrease some variables in the equation.

Mär 21 13:21:17 server3 mysqld[1085]:

Mär 21 13:21:17 server3 mysqld[1085]: Thread pointer: 0x7ff019695008

Mär 21 13:21:17 server3 mysqld[1085]: Attempting backtrace. You can use the following information to find out

Mär 21 13:21:17 server3 mysqld[1085]: where mysqld died. If you see no messages after this, something went

Mär 21 13:21:17 server3 mysqld[1085]: terribly wrong...

Mär 21 13:21:17 server3 mysqld[1085]: stack_bottom = 0x7ff0ee8a7e88 thread_stack 0x30000

Mär 21 13:21:18 server3 mysqld[1085]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0xc0885e]

Mär 21 13:21:18 server3 mysqld[1085]: /usr/sbin/mysqld(handle_fatal_signal+0x3af)[0x738a2f]

Mär 21 13:21:18 server3 mysqld[1085]: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7ff18e47b890]

Mär 21 13:21:18 server3 mysqld[1085]: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7ff18d024067]

Mär 21 13:21:18 server3 mysqld[1085]: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7ff18d025448]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld[0x98de3c]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld[0x994de6]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld[0x995d82]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x33)[0x73cf63]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x8c9)[0x66da29]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_Z19open_table_uncachedP3THDP10handlertonPKcS4_S4_bb+0x1c9)[0x578e39]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderb+0x3b11)[0x653911]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x4db)[0x69cc9b]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x6cb)[0x5c0b2b]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1ca)[0x5c6d2a]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1587)[0x5c8847]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x25b)[0x6992db]

Mär 21 13:21:19 server3 mysqld[1085]: /usr/sbin/mysqld(handle_one_connection+0x39)[0x699329]

Mär 21 13:21:19 server3 mysqld[1085]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7ff18e474064]

Mär 21 13:21:19 server3 mysqld[1085]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff18d0d762d]

Mär 21 13:21:19 server3 mysqld[1085]:

Mär 21 13:21:19 server3 mysqld[1085]: Trying to get some variables.

Mär 21 13:21:19 server3 mysqld[1085]: Some pointers may be invalid and cause the dump to abort.

Mär 21 13:21:19 server3 mysqld[1085]: Query (0x7ff01483a020): is an invalid pointer

Mär 21 13:21:19 server3 mysqld[1085]: Connection ID (thread ID): 4606782

Mär 21 13:21:19 server3 mysqld[1085]: Status: NOT_KILLED

Mär 21 13:21:19 server3 mysqld[1085]:

Mär 21 13:21:19 server3 mysqld[1085]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on

Mär 21 13:21:19 server3 mysqld[1085]:

Mär 21 13:21:19 server3 mysqld[1085]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

Mär 21 13:21:19 server3 mysqld[1085]: information that should help you find out what is causing the crash.

Mär 21 13:21:19 server3 mysqld[1085]:

Mär 21 13:21:19 server3 mysqld[1085]: We think the query pointer is invalid, but we will try to print it anyway.

Mär 21 13:21:19 server3 mysqld[1085]: Query: ALTER TABLE `catalog_product_flat_10` ADD CONSTRAINT `FK_CAT_PRD_FLAT_10_ENTT_ID_CAT_PRD_ENTT_ENTT_ID` FOREIGN KEY (`entity_id`) REFERENCES `catalog_product_entity` (`entity_id`) ON DELETE CASCADE ON UPDATE CASCADE

Mär 21 13:21:19 server3 mysqld[1085]:

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB-0+deb8u1) starting as process 16722 ...

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Using mutexes to ref count buffer pool pages

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: The InnoDB memory heap is disabled

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Compressed tables use zlib 1.2.8

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Using Linux native AIO

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Using CPU crc32 instructions

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Initializing buffer pool, size = 5.0G

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Completed initialization of buffer pool

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Highest supported file format is Barracuda.

Mär 21 13:21:20 server3 mysqld[16723]: 190321 13:21:20 [Note] InnoDB: Starting crash recovery from checkpoint LSN=23210158732705

Mär 21 13:21:24 server3 mysqld[16723]: 190321 13:21:24 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

Mär 21 13:21:25 server3 mysqld[16723]: 190321 13:21:25 [Note] InnoDB: Starting final batch to recover 427 pages from redo log

Mär 21 13:21:26 server3 mysqld[16723]: 190321 13:21:26 [Note] InnoDB: 128 rollback segment(s) are active.

Mär 21 13:21:26 server3 mysqld[16723]: 190321 13:21:26 [Note] InnoDB: Waiting for purge to start

Mär 21 13:21:26 server3 mysqld[16723]: 190321 13:21:26 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 23210183027997

Mär 21 13:21:26 server3 mysqld[16723]: 190321 13:21:26 [Note] Plugin 'FEEDBACK' is disabled.

Mär 21 13:21:27 server3 mysqld[16723]: 190321 13:21:27 [Note] Server socket created on IP: '::'.

Mär 21 13:21:27 server3 mysqld[16723]: 190321 13:21:27 [Note] /usr/sbin/mysqld: ready for connections.

Mär 21 13:21:27 server3 mysqld[16723]: Version: '10.0.38-MariaDB-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: Warning: Index PRIMARY points to table project_mage/catalog_product_flat_3 and ib_table project_mage/#sql-4152_42a5 statistics is initialized 1 but index table project_mage/catalog_product_flat_3 initialized 1 mysql table is #sql-4152_42a5. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Error] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_TYPE_ID for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name PRIMARY for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_TYPE_ID for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_ATTRIBUTE_SET_ID for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_NAME for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_PRICE for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_STATUS for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_HT_POSITION for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: [Note] Index for key no 1 mysql name IDX_CATALOG_PRODUCT_FLAT_7_TYPE_ID , InnoDB name IDX_CATALOG_PRODUCT_FLAT_3_HT_GEWICHT for table project_mage/#sql-4152_42a5

Mär 21 15:42:09 server3 mysqld[16723]: 2019-03-21 15:42:09 7f01905d0700 InnoDB: Assertion failure in thread 139644693710592 in file ha_innodb.cc line 9040

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: Failing assertion: ut_strcmp(index->name, key->name) == 0

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: We intentionally generate a memory trap.

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: If you get repeated assertion failures or crashes, even

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: immediately after the mysqld startup, there may be

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: corruption in the InnoDB tablespace. Please refer to

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

Mär 21 15:42:09 server3 mysqld[16723]: InnoDB: about forcing recovery.

Mär 21 15:42:09 server3 mysqld[16723]: 190321 15:42:09 [ERROR] mysqld got signal 6 ;

Mär 21 15:42:09 server3 mysqld[16723]: This could be because you hit a bug. It is also possible that this binary

Mär 21 15:42:09 server3 mysqld[16723]: or one of the libraries it was linked against is corrupt, improperly built,

Mär 21 15:42:09 server3 mysqld[16723]: or misconfigured. This error can also be caused by malfunctioning hardware.

Mär 21 15:42:09 server3 mysqld[16723]:

Mär 21 15:42:09 server3 mysqld[16723]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

Mär 21 15:42:09 server3 mysqld[16723]:

Mär 21 15:42:09 server3 mysqld[16723]: We will try our best to scrape up some info that will hopefully help

Mär 21 15:42:09 server3 mysqld[16723]: diagnose the problem, but since we have already crashed,

Mär 21 15:42:09 server3 mysqld[16723]: something is definitely wrong and this may fail.

Mär 21 15:42:09 server3 mysqld[16723]:

Mär 21 15:42:09 server3 mysqld[16723]: Server version: 10.0.38-MariaDB-0+deb8u1

Mär 21 15:42:09 server3 mysqld[16723]: key_buffer_size=25165824

Mär 21 15:42:09 server3 mysqld[16723]: read_buffer_size=131072

Mär 21 15:42:09 server3 mysqld[16723]: max_used_connections=18

Mär 21 15:42:09 server3 mysqld[16723]: max_threads=153

Mär 21 15:42:09 server3 mysqld[16723]: thread_count=4

Mär 21 15:42:09 server3 mysqld[16723]: It is possible that mysqld could use up to

Mär 21 15:42:09 server3 mysqld[16723]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 360522 K bytes of memory

Mär 21 15:42:09 server3 mysqld[16723]: Hope that's ok; if not, decrease some variables in the equation.

Mär 21 15:42:09 server3 mysqld[16723]:

Mär 21 15:42:09 server3 mysqld[16723]: Thread pointer: 0x7f001e0c5008

Mär 21 15:42:09 server3 mysqld[16723]: Attempting backtrace. You can use the following information to find out

Mär 21 15:42:09 server3 mysqld[16723]: where mysqld died. If you see no messages after this, something went

Mär 21 15:42:09 server3 mysqld[16723]: terribly wrong...

Mär 21 15:42:09 server3 mysqld[16723]: stack_bottom = 0x7f01905cfe88 thread_stack 0x30000

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0xc0885e]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(handle_fatal_signal+0x3af)[0x738a2f]

Mär 21 15:42:10 server3 mysqld[16723]: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0192dbf890]

Mär 21 15:42:10 server3 mysqld[16723]: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0191968067]

Mär 21 15:42:10 server3 mysqld[16723]: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0191969448]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld[0x98de3c]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld[0x994de6]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld[0x995d82]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcij+0x33)[0x73cf63]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x8c9)[0x66da29]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_Z19open_table_uncachedP3THDP10handlertonPKcS4_S4_bb+0x1c9)[0x578e39]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderb+0x3b11)[0x653911]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x4db)[0x69cc9b]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x6cb)[0x5c0b2b]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1ca)[0x5c6d2a]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1587)[0x5c8847]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x25b)[0x6992db]

Mär 21 15:42:10 server3 mysqld[16723]: /usr/sbin/mysqld(handle_one_connection+0x39)[0x699329]

Mär 21 15:42:11 server3 mysqld[16723]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f0192db8064]

Mär 21 15:42:11 server3 mysqld[16723]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0191a1b62d]

Mär 21 15:42:11 server3 mysqld[16723]:

Mär 21 15:42:11 server3 mysqld[16723]: Trying to get some variables.

Mär 21 15:42:11 server3 mysqld[16723]: Some pointers may be invalid and cause the dump to abort.

Mär 21 15:42:11 server3 mysqld[16723]: Query (0x7f000281f020): is an invalid pointer

Mär 21 15:42:11 server3 mysqld[16723]: Connection ID (thread ID): 17061

Mär 21 15:42:11 server3 mysqld[16723]: Status: NOT_KILLED

Mär 21 15:42:11 server3 mysqld[16723]:

Mär 21 15:42:11 server3 mysqld[16723]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on

Mär 21 15:42:11 server3 mysqld[16723]:

Mär 21 15:42:11 server3 mysqld[16723]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

Mär 21 15:42:11 server3 mysqld[16723]: information that should help you find out what is causing the crash.

Mär 21 15:42:11 server3 mysqld[16723]:

Mär 21 15:42:11 server3 mysqld[16723]: We think the query pointer is invalid, but we will try to print it anyway.

Mär 21 15:42:11 server3 mysqld[16723]: Query: ALTER TABLE `catalog_product_flat_7` ADD CONSTRAINT `FK_CAT_PRD_FLAT_7_ENTT_ID_CAT_PRD_ENTT_ENTT_ID` FOREIGN KEY (`entity_id`) REFERENCES `catalog_product_entity` (`entity_id`) ON DELETE CASCADE ON UPDATE CASCADE

Mär 21 15:42:11 server3 mysqld[16723]:

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB-0+deb8u1) starting as process 20783 ...

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: Using mutexes to ref count buffer pool pages

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: The InnoDB memory heap is disabled

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: Compressed tables use zlib 1.2.8

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: Using Linux native AIO

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: Using CPU crc32 instructions

Mär 21 15:42:11 server3 mysqld[20784]: 190321 15:42:11 [Note] InnoDB: Initializing buffer pool, size = 5.0G

Mär 21 15:42:12 server3 mysqld[20784]: 190321 15:42:12 [Note] InnoDB: Completed initialization of buffer pool

Mär 21 15:42:12 server3 mysqld[20784]: 190321 15:42:12 [Note] InnoDB: Highest supported file format is Barracuda.

Mär 21 15:42:12 server3 mysqld[20784]: 190321 15:42:12 [Note] InnoDB: Starting crash recovery from checkpoint LSN=23222894463444

Mär 21 15:42:12 server3 mysqld[20784]: 190321 15:42:12 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...

Mär 21 15:42:13 server3 mysqld[20784]: InnoDB: 1 transaction(s) which must be rolled back or cleaned up

Mär 21 15:42:13 server3 mysqld[20784]: InnoDB: in total 26696 row operations to undo

Mär 21 15:42:13 server3 mysqld[20784]: InnoDB: Trx id counter is 8991234816

Mär 21 15:42:13 server3 mysqld[20784]: 190321 15:42:13 [Note] InnoDB: Starting final batch to recover 676 pages from redo log

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] InnoDB: 128 rollback segment(s) are active.

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] InnoDB: Starting in background the rollback of recovered transactions

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] InnoDB: Waiting for purge to start

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 23222935794917

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] Plugin 'FEEDBACK' is disabled.

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] Server socket created on IP: '::'.

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] /usr/sbin/mysqld: ready for connections.

Mär 21 15:42:14 server3 mysqld[20784]: Version: '10.0.38-MariaDB-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] InnoDB: Rollback of trx with id 8991234295 completed

Mär 21 15:42:14 server3 mysqld[20784]: 190321 15:42:14 [Note] InnoDB: Rollback of non-prepared transactions completed

Mär 21 15:42:35 server3 mysqld[20784]: 190321 15:42:35 [ERROR] mysqld: Table './project_mage/catalogsearch_fulltext' is marked as crashed and should be repaired

Mär 21 15:42:35 server3 mysqld[20784]: 190321 15:42:35 [Warning] Checking table: './project_mage/catalogsearch_fulltext'

I have added the current SQL structure from the database.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

project_mage_structure.sql.gz
63 kB
2019-03-25 10:29

Issue Links

duplicates

MDEV-16060 InnoDB: Failing assertion: ut_strcmp(index->name, key->name)

Closed

relates to

MDEV-18847 Assertion failure in file ha_innodb.cc line 9690, Failing assertion: ut_strcmp(index->name, key->name) == 0

Closed

Activity

People

Assignee:: Sergey Vojtovich

Reporter:: LEONEX Internet GmbH

Votes:: 1 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2019-03-25 10:30

Updated:: 2019-05-09 07:52

Resolved:: 2019-05-09 07:47

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.