Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-37091

Signal 11 when running mariadb-dump

    XMLWordPrintable

Details

    • Not for Release Notes

    Description

      Running mariadb-dump crashes on mariadb server I set up today consistently.

      It works fine when I run the backup as a root user, however when I use a user I created called "backup-service" it crashes as follows:

      250626 20:58:22 [ERROR] mariadbd got signal 11 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to report
      a bug on https://jira.mariadb.org/.
       
      Please include the information from the server start above, to the end of the
      information below.
       
      Server version: 11.8.2-MariaDB-ubu2404-log source revision: 8d36cafe4fc700e6e577d5a36650c58707e76b92
       
      The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
      contains instructions to obtain a better version of the backtrace below.
      Following these instructions will help MariaDB developers provide a fix quicker.
       
      Attempting backtrace. Include this in the bug report.
      (note: Retrieving this information may fail)
       
      Thread pointer: 0x7f27ac000c68
      stack_bottom = 0x7f283c429000 thread_stack 0x49000
      Printing to addr2line failed
      mariadbd(my_print_stacktrace+0x30)[0x55c8587170a0]
      mariadbd(handle_fatal_signal+0x1f3)[0x55c858290893]
      /lib/x86_64-linux-gnu/libc.so.6(+0x45330)[0x7f2855fe6330]
      mariadbd(_ZN4Item19print_parenthesisedEP6String15enum_query_type10precedence+0x21)[0x55c8582af6a1]
      mariadbd(+0x11340db)[0x55c8588890db]
      mariadbd(+0x8d60fc)[0x55c85802b0fc]
      mariadbd(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x176a)[0x55c8580316aa]
      mariadbd(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x2aa)[0x55c85803a7aa]
      mariadbd(_ZN4JOIN10exec_innerEv+0x9dd)[0x55c857fd2f4d]
      mariadbd(_ZN4JOIN4execEv+0x37)[0x55c857fd3927]
      mariadbd(_Z12mysql_selectP3THDP10TABLE_LISTR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x128)[0x55c857fd3f38]
      mariadbd(_Z13handle_selectP3THDP3LEXP13select_resulty+0x17a)[0x55c857fc2b9a]
      mariadbd(+0x82da81)[0x55c857f82a81]
      mariadbd(_Z21mysql_execute_commandP3THDb+0x3868)[0x55c857f8d438]
      mariadbd(_Z11mysql_parseP3THDPcjP12Parser_state+0x19a)[0x55c857f8e6ca]
      mariadbd(_Z16dispatch_command19enum_server_commandP3THDPcjb+0x1041)[0x55c857f7a531]
      mariadbd(_Z10do_commandP3THDb+0x199)[0x55c857f7bc39]
      mariadbd(_Z24do_handle_one_connectionP7CONNECTb+0x65b)[0x55c85811183b]
      mariadbd(handle_one_connection+0x71)[0x55c858111c81]
      mariadbd(+0xd6e27e)[0x55c8584c327e]
      /lib/x86_64-linux-gnu/libc.so.6(+0x9caa4)[0x7f285603daa4]
      /lib/x86_64-linux-gnu/libc.so.6(+0x129c3c)[0x7f28560cac3c]
       
      Connection ID (thread ID): 766
      Status: NOT_KILLED
      Query (0x7f27ac013070): select column_name, extra, generation_expression, data_type from information_schema.columns where table_schema=database() and table_name='contact' order by ordinal_position
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=on,sargable_casefold=on
       
      Writing a core file...
      Working directory at /var/lib/mysql
      Resource Limits (excludes unlimited resources):
      Limit                     Soft Limit           Hard Limit           Units     
      Max stack size            8388608              unlimited            bytes     
      Max processes             1048576              1048576              processes 
      Max open files            1048576              1048576              files     
      Max locked memory         8388608              8388608              bytes     
      Max pending signals       103003               103003               signals   
      Max msgqueue size         819200               819200               bytes     
      Max nice priority         0                    0                    
      Max realtime priority     0                    0                    
      Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
       
      Kernel version: Linux version 5.14.0-553.el9.x86_64 (mockbuild@x86-05.stream.rdu2.redhat.com) (gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2), GNU ld version 2.35.2-59.el9) #1 SMP PREEMPT_DYNAMIC Wed Jan 15 16:52:20 UTC 2025
      

      This is how the user was created when restoring an earlier dump

      CREATE USER `backup-service`@`%` IDENTIFIED BY PASSWORD '.....';
      GRANT SELECT, SHOW DATABASES, LOCK TABLES, EXECUTE, REPLICATION SLAVE, SHOW VIEW, TRIGGER ON *.* TO `backup-service`@`%` IDENTIFIED BY PASSWORD '....';
      /*M!100005 SET DEFAULT ROLE NONE FOR 'backup-service'@'%' */;
      /*!80001 ALTER USER 'backup-service'@'%' DEFAULT ROLE NONE */;
      

      For the dump I used the following switches

      --single-transaction --skip-add-locks --routines --triggers
      

      Attachments

        Issue Links

          Activity

            People

              serg Sergei Golubchik
              naranha Frederick Kämpfer
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.