← Back to team overview

maria-discuss team mailing list archive

Re: how to file a problem / bug ?

 

Hi Markus,

as I wrote before, I wasn't sure if this list was the right place. So I didn't want to go into more details first.

What I did:

 * A relatively simple table, 5 columns, col1...col4 unsingned integers
   (medium and tiny), col5 decimal
 * col1...col4 together form the primary key
 * besides this, col2...col4 have foreign key constraint pointing to 3
   other tables

First I had 4 indexes

 * primary (col1,col2,col3,col4)
 * col2_Idx (col2)
 * col3_Idx (col3)
 * col4_Idx (col4)

and the 3 foreign key constraints.

Some weeks ago I wondered if the 3 indexes for col2...col4 are necessary at all, because this 3 columns are allready part of the primary key. So I thought "just try" and simply DROPed them. The server did not complain and the table still "worked" as before for some weeks now.

Yesterday evenenig I added a 6th column (of type decimal) to the table. Still everything was fine. I inserted some records, everything ok.

Today I connected to the DB again (from a different machine). When I inserted the first record I saw that the 3 foreign key were gone. Now I guessed that there was a problem with the deleted indexes in the server by adding the 6th column. For a test I tried to recreate 1 of those indexes (for col2). There the server crashed. (See the log attached to this mail)

Norbert


Am 14.03.19 12:24 schrieb Markus Mäkelä:
Hi,

If you're looking to report bugs, you can find the MariaDB Jira here: https://jira.mariadb.org

What sort of a problem did you encounter? It's possible that it's not a bug so some more details would be good.

Markus

2019-03-14  0:33:32 140447313766144 [Warning] Aborted connection 82719 to db: 'asterisk' user: 'asterisk' host: 'asterina.intra.zawodsky.at' (Got timeout reading communication packets)
2019-03-14 11:49:37 140447313766144 [ERROR] Cannot find index Cash_UID_Idx in InnoDB index dictionary.
2019-03-14 11:49:37 140447313766144 [ERROR] Build InnoDB index translation table for Table ./Grapecash/J_CashOpEntries failed
2019-03-14 11:49:37 140447313766144 [ERROR] InnoDB could not find key no 1 with name Cash_UID_Idx from dict cache for table Grapecash/J_CashOpEntries
2019-03-14 11:49:37 140447313766144 [ERROR] InnoDB: Table Grapecash/J_CashOpEntries contains 2 indexes inside InnoDB, which is different from the number of indexes 2 defined in the MariaDB  Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html

2019-03-14 11:49:37 140447313766144 [ERROR] InnoDB could not find key no 1 with name Cash_UID_Idx from dict cache for table Grapecash/J_CashOpEntries
190314 11:49:37 [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.

To report this bug, see https://mariadb.com/kb/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: 10.2.15-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=12
max_threads=153
thread_count=16
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 215462 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fbbf0085368
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 = 0x7fbc703f1cf8 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x3c)[0x562b3e61859c]
/usr/sbin/mysqld(handle_fatal_signal+0x57b)[0x562b3e14d89b]
/lib64/libpthread.so.0(+0x122e0)[0x7fbc84a532e0]
/usr/sbin/mysqld(+0x7cd820)[0x562b3e2c0820]
/usr/sbin/mysqld(+0x5333e7)[0x562b3e0263e7]
/usr/sbin/mysqld(+0x52afc7)[0x562b3e01dfc7]
/usr/sbin/mysqld(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x1c3)[0x562b3e02e3e3]
/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x229)[0x562b3e02ff19]
/usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0x70d)[0x562b3e017b7d]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x30)[0x562b3e0180b0]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1fc)[0x562b3e01831c]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x17f)[0x562b3e018b9f]
/usr/sbin/mysqld(+0x4cf138)[0x562b3dfc2138]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x642f)[0x562b3dfcec2f]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x2e9)[0x562b3dfd12c9]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1fd8)[0x562b3dfd3fb8]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x176)[0x562b3dfd4886]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x204)[0x562b3e090084]
/usr/sbin/mysqld(handle_one_connection+0x34)[0x562b3e090264]
/lib64/libpthread.so.0(+0x7559)[0x7fbc84a48559]
/lib64/libc.so.6(clone+0x3f)[0x7fbc83e9281f]

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

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,orderby_uses_equalities=on,condition_pushdown_for_derived=on

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.

We think the query pointer is invalid, but we will try to print it anyway. 
Query: SHOW INDEXES FROM `Grapecash`.`J_CashOpEntries`

2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Uses event mutexes
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Using Linux native AIO
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Number of pools: 1
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Using SSE2 crc32 instructions
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Initializing buffer pool, total size = 512M, instances = 1, chunk size = 128M
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Completed initialization of buffer pool
2019-03-14 11:49:39 139888690431744 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-14 11:49:39 139889736788160 [Note] InnoDB: Starting crash recovery from checkpoint LSN=427206510748
2019-03-14 11:49:40 139889736788160 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
2019-03-14 11:49:41 139889736788160 [Note] InnoDB: Last binlog file './binlog.000001', position 25090610
2019-03-14 11:49:46 139889736788160 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-03-14 11:49:46 139889736788160 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-03-14 11:49:46 139889736788160 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-03-14 11:49:46 139889736788160 [Note] InnoDB: Setting file '/CryptHD/InnoDB/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-03-14 11:49:46 139889736788160 [Note] InnoDB: File '/CryptHD/InnoDB/ibtmp1' size is now 12 MB.
2019-03-14 11:49:46 139889736788160 [Note] InnoDB: Waiting for purge to start
2019-03-14 11:49:46 139889736788160 [Note] InnoDB: 5.7.22 started; log sequence number 427206511732
2019-03-14 11:49:46 139888401827584 [Note] InnoDB: Loading buffer pool(s) from /CryptHD/InnoDB/ib_buffer_pool
2019-03-14 11:49:46 139889736788160 [Note] Plugin 'FEEDBACK' is disabled.
2019-03-14 11:49:46 139889736788160 [Note] Recovering after a crash using tc.log
2019-03-14 11:49:46 139889736788160 [Note] Starting crash recovery...
2019-03-14 11:49:46 139889736788160 [Note] Crash recovery finished.
2019-03-14 11:49:46 139889736788160 [Note] Server socket created on IP: '::'.
2019-03-14 11:49:46 139889736788160 [Note] Reading of all Master_info entries succeded
2019-03-14 11:49:46 139889736788160 [Note] Added new Master_info '' to hash table
2019-03-14 11:49:46 139889736788160 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.2.15-MariaDB'  socket: '/var/run/mysql/mysql.sock'  port: 3306  openSUSE package
2019-03-14 11:49:51 139888401827584 [Note] InnoDB: Buffer pool(s) load completed at 190314 11:49:51

2019-03-14 11:51:20 139889395869440 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
2019-03-14 11:51:20 139889395869440 [Note] Event Scheduler: Purging the queue. 0 events
2019-03-14 11:51:20 139888648468224 [Note] InnoDB: FTS optimize thread exiting.
2019-03-14 11:51:20 139889395869440 [Note] InnoDB: Starting shutdown...
2019-03-14 11:51:20 139888401827584 [Note] InnoDB: Dumping buffer pool(s) to /CryptHD/InnoDB/ib_buffer_pool
2019-03-14 11:51:20 139888401827584 [Note] InnoDB: Buffer pool(s) dump completed at 190314 11:51:20
2019-03-14 11:51:21 139889395869440 [Note] InnoDB: Shutdown completed; log sequence number 427206513233
2019-03-14 11:51:21 139889395869440 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-03-14 11:51:21 139889395869440 [Note] /usr/sbin/mysqld: Shutdown complete

2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Uses event mutexes
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Using Linux native AIO
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Number of pools: 1
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Using SSE2 crc32 instructions
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Initializing buffer pool, total size = 512M, instances = 1, chunk size = 128M
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Completed initialization of buffer pool
2019-03-14 11:51:33 140028276868864 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Highest supported file format is Barracuda.
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: Setting file '/CryptHD/InnoDB/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: File '/CryptHD/InnoDB/ibtmp1' size is now 12 MB.
2019-03-14 11:51:33 140029323266240 [Note] InnoDB: 5.7.22 started; log sequence number 427206513233
2019-03-14 11:51:33 140028122482432 [Note] InnoDB: Loading buffer pool(s) from /CryptHD/InnoDB/ib_buffer_pool
2019-03-14 11:51:33 140029323266240 [Note] Plugin 'FEEDBACK' is disabled.
2019-03-14 11:51:34 140029323266240 [Note] Server socket created on IP: '::'.
2019-03-14 11:51:34 140029323266240 [Note] Reading of all Master_info entries succeded
2019-03-14 11:51:34 140029323266240 [Note] Added new Master_info '' to hash table
2019-03-14 11:51:34 140029323266240 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.2.15-MariaDB'  socket: '/var/run/mysql/mysql.sock'  port: 3306  openSUSE package
2019-03-14 11:51:34 140028122482432 [Note] InnoDB: Buffer pool(s) load completed at 190314 11:51:34

Follow ups

References