Details

    Description

      I hit this bug, please help. it happened twice today

      171128 14:22:18 [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.1.28-MariaDB
      key_buffer_size=2147483648
      read_buffer_size=8388608
      max_used_connections=7
      max_threads=802
      thread_count=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 15253640 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f232e6be008
      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 = 0x7f276792acb0 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55aaf981e92e]
      /usr/sbin/mysqld(handle_fatal_signal+0x305)[0x55aaf9341ce5]
      /lib64/libpthread.so.0(+0xf5e0)[0x7f276d4e15e0]
      /usr/sbin/mysqld(_ZN17Query_cache_block11headers_lenEv+0x0)[0x55aaf917b810]
      /usr/sbin/mysqld(_ZN17Query_cache_block4dataEv+0x11)[0x55aaf917b831]
      /usr/sbin/mysqld(_ZN11Query_cache6insertEP3THDP15Query_cache_tlsPKcmj+0x5c)[0x55aaf917f21c]
      /usr/sbin/mysqld(net_real_write+0x45)[0x55aaf9128e05]
      /usr/sbin/mysqld(net_flush+0x23)[0x55aaf9129143]
      /usr/sbin/mysqld(net_write_command+0x3fb)[0x55aaf91298ab]
      /usr/sbin/mysqld(cli_advanced_command+0xe2)[0x55aaf9321782]
      /usr/sbin/mysqld(mysql_send_query+0x31)[0x55aaf931ee61]
      /usr/sbin/mysqld(mysql_real_query+0x11)[0x55aaf931ee81]
      mysys/stacktrace.c:268(my_print_stacktrace)[0x7f27679f85fc]
      sql/signal_handler.cc:168(handle_fatal_signal)[0x55aaf9206215]
      sql-common/client.c:701())[0x55aaf920ec2f]
      sql/sql_select.cc:3584(make_join_statistics(JOIN*, List<TABLE_LIST>&, st_dynamic_array*))[0x55aaf921151f]
      sql/sql_select.cc:3435(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*))[0x55aaf921165f]
      sql/sql_select.cc:384(handle_select(THD*, LEX*, select_result*, unsigned long))[0x55aaf92121e5]
      /usr/sbin/mysqld(+0x376297)[0x55aaf90f8297]
      sql/sql_parse.cc:5913(execute_sqlcom_select(THD*, TABLE_LIST*))[0x55aaf91bc9b0]
      sql/sql_parse.cc:7334(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55aaf91bf702]
      sql/sql_parse.cc:1484(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x55aaf91c306a]
      sql/sql_parse.cc:1108(do_command(THD*))[0x55aaf91c39c6]
      sql/sql_connect.cc:1349(do_handle_one_connection(THD*))[0x55aaf928f61a]
      sql/sql_connect.cc:1263(handle_one_connection)[0x55aaf928f7c0]
      /lib64/libpthread.so.0(+0x7e25)[0x7f276d4d9e25]
      /lib64/libc.so.6(clone+0x6d)[0x7f276b87d34d]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f2767546020): /* TUNGSTEN USE qos=RO_RELAXED */ select a.type, a.reason, a.published, a.id_RSSEpisode, b.id_RSSFeed, a.id_NewsItem, c.custom_playlist_name, b.duration from sa1.UserFrontPage a left join sa1.RSSEpisode b on a.id_RSSEpisode = b.id left join sa1.user_preference_vector_federated c on a.id_User = c.id_User and b.id_RSSFeed = c.id_RSSFeed where a.id_User = 1003630460 and a.type in (0, 1, 2, 3, 4, 11, 12, 13, 14, 15) order by a.published desc limit 0, 3
      Connection ID (thread ID): 19705
      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=off

      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.
      Writing a core file
      2017-11-28 14:23:05 7f536d896900 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: The InnoDB memory heap is disabled
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: Compressed tables use zlib 1.2.7
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: Using Linux native AIO
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: Using SSE crc32 instructions
      2017-11-28 14:23:05 139996296734976 [Note] InnoDB: Initializing buffer pool, size = 16.0G
      2017-11-28 14:23:06 139996296734976 [Note] InnoDB: Completed initialization of buffer pool
      2017-11-28 14:23:06 139996296734976 [Note] InnoDB: Highest supported file format is Barracuda.
      2017-11-28 14:23:06 139996296734976 [Note] InnoDB: The log sequence number 3265437035429 in ibdata file do not match the log sequence number 3265441631402 in the ib_logfiles!
      2017-11-28 14:23:06 139996296734976 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
      InnoDB: Last MySQL binlog file position 0 649653, file name /var/lib/mysql/binlog/mysql-bin.000016
      2017-11-28 14:23:07 139996296734976 [Note] InnoDB: 128 rollback segment(s) are active.
      2017-11-28 14:23:07 139996296734976 [Note] InnoDB: Waiting for purge to start
      2017-11-28 14:23:07 139996296734976 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 3265441631402
      2017-11-28 14:23:07 139974846416640 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2017-11-28 14:23:07 139996296734976 [Note] Plugin 'FEEDBACK' is disabled.
      2017-11-28 14:23:07 139996296734976 [Note] Recovering after a crash using /var/lib/mysql/binlog/mysql-bin
      2017-11-28 14:23:07 139996296734976 [Note] Starting crash recovery...
      2017-11-28 14:23:07 139996296734976 [Note] Crash recovery finished.
      2017-11-28 14:23:07 139996296734976 [Warning] Failed to setup SSL
      2017-11-28 14:23:07 139996296734976 [Warning] SSL error: SSL_CTX_set_default_verify_paths failed
      2017-11-28 14:23:07 139996296734976 [Warning] SSL error: error:02001002:system library:fopen:No such file or directory
      2017-11-28 14:23:07 139996296734976 [Warning] SSL error: error:2006D080:BIO routines:BIO_new_file:no such file
      2017-11-28 14:23:07 139996296734976 [Warning] SSL error: error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib
      2017-11-28 14:23:07 139996296734976 [Note] Server socket created on IP: '0.0.0.0'.
      2017-11-28 14:23:07 139996296734976 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.1.28-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server

      Attachments

        Issue Links

          Activity

            alice Alice Sherepa added a comment -

            Please add table structure (and indexes) for all tables, involved in a query.

            alice Alice Sherepa added a comment - Please add table structure (and indexes) for all tables, involved in a query.

            jai, did you happen to change query cache type or query cache size around the time when the problem occurred?

            elenst Elena Stepanova added a comment - jai , did you happen to change query cache type or query cache size around the time when the problem occurred?
            jai Jai added a comment -

            Hi Elena,
            Thanks for getting back.
            We didn't change query cache type or query cache size. But the data was refreshed from a database that has 64GB ram vs this database server has 15GB ram. Do you think thats the issue.

            Thanks,
            Jai

            jai Jai added a comment - Hi Elena, Thanks for getting back. We didn't change query cache type or query cache size. But the data was refreshed from a database that has 64GB ram vs this database server has 15GB ram. Do you think thats the issue. Thanks, Jai

            jai, please define "was refreshed" in terms of exact steps that were performed.
            Please also provide information that alice requested in her earlier comment, along with your config file(s).
            Thanks.

            elenst Elena Stepanova added a comment - jai , please define "was refreshed" in terms of exact steps that were performed. Please also provide information that alice requested in her earlier comment, along with your config file(s). Thanks.
            jai Jai added a comment -

            Hi Elena,
            Refreshed meaning - Took a backup of database and restored in a new database instance.

            I will attach a file with those details

            jai Jai added a comment - Hi Elena, Refreshed meaning - Took a backup of database and restored in a new database instance. I will attach a file with those details
            alice Alice Sherepa added a comment -

            Hi Jai, do you use Federated storage engine? stack trace is very similar to MDEV-14272

            alice Alice Sherepa added a comment - Hi Jai, do you use Federated storage engine? stack trace is very similar to MDEV-14272
            jai Jai added a comment -

            Hi Alice,

            Yes we do use Federated Storage engine. And we have been using it for a while now without any issues.

            Thanks,
            Jai

            jai Jai added a comment - Hi Alice, Yes we do use Federated Storage engine. And we have been using it for a while now without any issues. Thanks, Jai
            elenst Elena Stepanova added a comment - - edited

            MDEV-14272 has been fixed now, the fix will be included in the next 10.1 release. Hopefully it will help.
            Please comment here if you still experience the problem on 10.1.31+, and the bug report will be re-opened.

            elenst Elena Stepanova added a comment - - edited MDEV-14272 has been fixed now, the fix will be included in the next 10.1 release. Hopefully it will help. Please comment here if you still experience the problem on 10.1.31+, and the bug report will be re-opened.

            People

              Unassigned Unassigned
              jai Jai
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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