Details

    Description

      Aug 19 20:05:43 g2 mysqld[5046]: 160819 20:05:43 [ERROR] mysqld got signal 11 ;
      Aug 19 20:05:43 g2 mysqld[5046]: This could be because you hit a bug. It is also possible that this binary
      Aug 19 20:05:43 g2 mysqld[5046]: or one of the libraries it was linked against is corrupt, improperly built,
      Aug 19 20:05:43 g2 mysqld[5046]: or misconfigured. This error can also be caused by malfunctioning hardware.
      Aug 19 20:05:43 g2 mysqld[5046]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
      Aug 19 20:05:43 g2 mysqld[5046]: We will try our best to scrape up some info that will hopefully help
      Aug 19 20:05:43 g2 mysqld[5046]: diagnose the problem, but since we have already crashed,
      Aug 19 20:05:43 g2 mysqld[5046]: something is definitely wrong and this may fail.
      Aug 19 20:05:43 g2 mysqld[5046]: Server version: 10.1.16-MariaDB-1~xenial
      Aug 19 20:05:43 g2 mysqld[5046]: key_buffer_size=134217728
      Aug 19 20:05:43 g2 mysqld[5046]: read_buffer_size=2097152
      Aug 19 20:05:43 g2 mysqld[5046]: max_used_connections=18
      Aug 19 20:05:43 g2 mysqld[5046]: max_threads=102
      Aug 19 20:05:43 g2 mysqld[5046]: thread_count=9
      Aug 19 20:05:43 g2 mysqld[5046]: It is possible that mysqld could use up to
      Aug 19 20:05:43 g2 mysqld[5046]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759828 K  bytes of memory
      Aug 19 20:05:43 g2 mysqld[5046]: Hope that's ok; if not, decrease some variables in the equation.
      Aug 19 20:05:43 g2 mysqld[5046]: Thread pointer: 0x0x7f0927412008
      Aug 19 20:05:43 g2 mysqld[5046]: Attempting backtrace. You can use the following information to find out
      Aug 19 20:05:43 g2 mysqld[5046]: where mysqld died. If you see no messages after this, something went
      Aug 19 20:05:43 g2 mysqld[5046]: terribly wrong...
      Aug 19 20:05:43 g2 mysqld[5046]: stack_bottom = 0x7f0a7f34f0a8 thread_stack 0x48400
      Aug 19 20:05:43 g2 mysqld[5046]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x560fb73d15ee]
      Aug 19 20:05:43 g2 mysqld[5046]: /usr/sbin/mysqld(handle_fatal_signal+0x2d5)[0x560fb6f20c25]
      Aug 19 20:05:43 g2 mysqld[5046]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0)[0x7f0a7daa23d0]
      Aug 19 20:05:43 g2 mysqld[5046]: /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0x7b)[0x560fb6fd563b]
      Aug 19 20:05:43 g2 mysqld[5046]: /usr/sbin/mysqld(binlog_background_thread+0x2f3)[0x560fb6fd5b33]
      Aug 19 20:05:43 g2 mysqld[5046]: /usr/sbin/mysqld(+0x703e41)[0x560fb7090e41]
      Aug 19 20:05:43 g2 mysqld[5046]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7f0a7da986fa]
      Aug 19 20:05:43 g2 mysqld[5046]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0a7d143b5d]
      Aug 19 20:05:43 g2 mysqld[5046]: Trying to get some variables.
      Aug 19 20:05:43 g2 mysqld[5046]: Some pointers may be invalid and cause the dump to abort.
      Aug 19 20:05:43 g2 mysqld[5046]: Query (0x0):
      Aug 19 20:05:43 g2 mysqld[5046]: Connection ID (thread ID): 3
      Aug 19 20:05:43 g2 mysqld[5046]: Status: NOT_KILLED
      Aug 19 20:05:43 g2 mysqld[5046]: 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=
      

      Attachments

        Issue Links

          Activity

            leelists,

            are you running a Galera cluster or standalone server?

            elenst Elena Stepanova added a comment - leelists , are you running a Galera cluster or standalone server?
            leelists Lee Lists added a comment -

            Hi Elena,

            Yes i'm running a Galera Cluster,

            Thanks for your support

            This crash appears daily ...

            Here's the last one ...

            Aug 20 03:02:42 g2 mysqld[31414]: Server version: 10.1.16-MariaDB-1~xenial
            Aug 20 03:02:42 g2 mysqld[31414]: key_buffer_size=134217728
            Aug 20 03:02:42 g2 mysqld[31414]: read_buffer_size=2097152
            Aug 20 03:02:42 g2 mysqld[31414]: max_used_connections=14
            Aug 20 03:02:42 g2 mysqld[31414]: max_threads=102
            Aug 20 03:02:42 g2 mysqld[31414]: thread_count=9
            Aug 20 03:02:42 g2 mysqld[31414]: It is possible that mysqld could use up to
            Aug 20 03:02:42 g2 mysqld[31414]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759828 K bytes of memory
            Aug 20 03:02:42 g2 mysqld[31414]: Hope that's ok; if not, decrease some variables in the equation.
            Aug 20 03:02:42 g2 mysqld[31414]: Thread pointer: 0x0x7fc1ad012008
            Aug 20 03:02:42 g2 mysqld[31414]: Attempting backtrace. You can use the following information to find out
            Aug 20 03:02:42 g2 mysqld[31414]: where mysqld died. If you see no messages after this, something went
            Aug 20 03:02:42 g2 mysqld[31414]: terribly wrong...
            Aug 20 03:02:42 g2 mysqld[31414]: stack_bottom = 0x7fc30521e0a8 thread_stack 0x48400
            Aug 20 03:02:42 g2 mysqld[31414]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55ba986055ee]
            Aug 20 03:02:42 g2 mysqld[31414]: /usr/sbin/mysqld(handle_fatal_signal+0x2d5)[0x55ba98154c25]
            Aug 20 03:02:42 g2 mysqld[31414]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0)[0x7fc3039713d0]
            Aug 20 03:02:42 g2 mysqld[31414]: /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0x7b)[0x55ba9820963b]
            Aug 20 03:02:42 g2 mysqld[31414]: /usr/sbin/mysqld(binlog_background_thread+0x2f3)[0x55ba98209b33]
            Aug 20 03:02:42 g2 mysqld[31414]: /usr/sbin/mysqld(+0x703e41)[0x55ba982c4e41]
            Aug 20 03:02:42 g2 mysqld[31414]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7fc3039676fa]
            Aug 20 03:02:42 g2 mysqld[31414]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc303012b5d]
            Aug 20 03:02:42 g2 mysqld[31414]: Trying to get some variables.
            Aug 20 03:02:42 g2 mysqld[31414]: Some pointers may be invalid and cause the dump to abort.
            Aug 20 03:02:42 g2 mysqld[31414]: Query (0x0):
            Aug 20 03:02:42 g2 mysqld[31414]: Connection ID (thread ID): 3
            Aug 20 03:02:42 g2 mysqld[31414]: Status: NOT_KILLED
            Aug 20 03:02:42 g2 mysqld[31414]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index

            leelists Lee Lists added a comment - Hi Elena, Yes i'm running a Galera Cluster, Thanks for your support This crash appears daily ... Here's the last one ... Aug 20 03:02:42 g2 mysqld [31414] : Server version: 10.1.16-MariaDB-1~xenial Aug 20 03:02:42 g2 mysqld [31414] : key_buffer_size=134217728 Aug 20 03:02:42 g2 mysqld [31414] : read_buffer_size=2097152 Aug 20 03:02:42 g2 mysqld [31414] : max_used_connections=14 Aug 20 03:02:42 g2 mysqld [31414] : max_threads=102 Aug 20 03:02:42 g2 mysqld [31414] : thread_count=9 Aug 20 03:02:42 g2 mysqld [31414] : It is possible that mysqld could use up to Aug 20 03:02:42 g2 mysqld [31414] : key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759828 K bytes of memory Aug 20 03:02:42 g2 mysqld [31414] : Hope that's ok; if not, decrease some variables in the equation. Aug 20 03:02:42 g2 mysqld [31414] : Thread pointer: 0x0x7fc1ad012008 Aug 20 03:02:42 g2 mysqld [31414] : Attempting backtrace. You can use the following information to find out Aug 20 03:02:42 g2 mysqld [31414] : where mysqld died. If you see no messages after this, something went Aug 20 03:02:42 g2 mysqld [31414] : terribly wrong... Aug 20 03:02:42 g2 mysqld [31414] : stack_bottom = 0x7fc30521e0a8 thread_stack 0x48400 Aug 20 03:02:42 g2 mysqld [31414] : /usr/sbin/mysqld(my_print_stacktrace+0x2e) [0x55ba986055ee] Aug 20 03:02:42 g2 mysqld [31414] : /usr/sbin/mysqld(handle_fatal_signal+0x2d5) [0x55ba98154c25] Aug 20 03:02:42 g2 mysqld [31414] : /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0) [0x7fc3039713d0] Aug 20 03:02:42 g2 mysqld [31414] : /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0x7b) [0x55ba9820963b] Aug 20 03:02:42 g2 mysqld [31414] : /usr/sbin/mysqld(binlog_background_thread+0x2f3) [0x55ba98209b33] Aug 20 03:02:42 g2 mysqld [31414] : /usr/sbin/mysqld(+0x703e41) [0x55ba982c4e41] Aug 20 03:02:42 g2 mysqld [31414] : /lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa) [0x7fc3039676fa] Aug 20 03:02:42 g2 mysqld [31414] : /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fc303012b5d] Aug 20 03:02:42 g2 mysqld [31414] : Trying to get some variables. Aug 20 03:02:42 g2 mysqld [31414] : Some pointers may be invalid and cause the dump to abort. Aug 20 03:02:42 g2 mysqld [31414] : Query (0x0): Aug 20 03:02:42 g2 mysqld [31414] : Connection ID (thread ID): 3 Aug 20 03:02:42 g2 mysqld [31414] : Status: NOT_KILLED Aug 20 03:02:42 g2 mysqld [31414] : Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index
            leelists Lee Lists added a comment -

            just FYI i disabled log_bin on every 3 nodes and the crashes are gone (for now)

            Regards,
            Lee

            leelists Lee Lists added a comment - just FYI i disabled log_bin on every 3 nodes and the crashes are gone (for now) Regards, Lee

            A patch has been pushed to 10.1.17 which will make the node print additional details in the error log around this issue when --wsrep-debug=ON.

            nirbhay_c Nirbhay Choubey (Inactive) added a comment - A patch has been pushed to 10.1.17 which will make the node print additional details in the error log around this issue when --wsrep-debug=ON.
            Elkin Andrei Elkin added a comment -

            Fixed by MDEV-9510.

            Elkin Andrei Elkin added a comment - Fixed by MDEV-9510 .

            People

              sachin.setiya.007 Sachin Setiya (Inactive)
              leelists Lee Lists
              Votes:
              1 Vote for this issue
              Watchers:
              7 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.