Uploaded image for project: 'Percona XtraDB Cluster'
  1. Percona XtraDB Cluster
  2. PXC-2427

mysqld got signal 11

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Duplicate
    • Affects Version/s: 5.7.24-31.33
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Description

      11:00:04 UTC - 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. Please help us make Percona XtraDB Cluster better by reporting any bugs at https://jira.percona.com/projects/PXC/issueskey_buffer_size=8388608 read_buffer_size=131072 max_used_connections=22 max_threads=152 thread_count=6 connection_count=4 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68410 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x7f19cc685980 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 = 7f1a1c5aea70 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xec7eab] /usr/sbin/mysqld(handle_fatal_signal+0x499)[0x788b59] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f1a3bf7e390] /usr/sbin/mysqld(my_b_safe_tell+0x12)[0xea9f62] /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG19raw_get_current_logEP11st_log_info+0x2a)[0xe4aa0a] /usr/sbin/mysqld[0xe5264d] /usr/sbin/mysqld[0x801baa] /usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPPFcS0_P13st_plugin_intPvEijS3_+0x1e1)[0xc9cbf1] /usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3_+0x2c)[0xc9cd9c] /usr/sbin/mysqld(_Z28ha_start_consistent_snapshotP3THD+0x19a)[0x80934a] /usr/sbin/mysqld(_Z11trans_beginP3THDj+0x290)[0xd2b040] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x28e7)[0xc72af7] /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_stateb+0x49d)[0xc7915d] /usr/sbin/mysqld[0xc792fd] /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x1312)[0xc7aef2] /usr/sbin/mysqld(_Z10do_commandP3THD+0x2ac)[0xc7cdfc] /usr/sbin/mysqld(handle_connection+0x3b8)[0xd4ac88] /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xee2b24] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f1a3bf746ba] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f1a3b40941d]Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f19cc672dd0): is an invalid pointer Connection ID (thread ID): 83422 Status: NOT_KILLED
      

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  sebestenyb Balazs Sebesteny
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: