Uploaded image for project: 'Percona Server for MySQL'
  1. Percona Server for MySQL
  2. PS-385

LP #1390695: percona 5.6.21-70.0 crash on data import

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      **Reported in Launchpad by Damian Luszczymak last update 14-11-2014 13:14:56

      141108 11:00:53 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
      141108 11:00:53 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
      2014-11-08 11:00:54 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
      2014-11-08 11:00:54 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
      2014-11-08 11:00:54 6628 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
      2014-11-08 11:00:54 6628 [Note] Plugin 'FEDERATED' is disabled.
      2014-11-08 11:00:54 6628 [Note] InnoDB: Using atomics to ref count buffer pool pages
      2014-11-08 11:00:54 6628 [Note] InnoDB: The InnoDB memory heap is disabled
      2014-11-08 11:00:54 6628 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2014-11-08 11:00:54 6628 [Note] InnoDB: Memory barrier is not used
      2014-11-08 11:00:54 6628 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2014-11-08 11:00:54 6628 [Note] InnoDB: Using Linux native AIO
      2014-11-08 11:00:54 6628 [Note] InnoDB: Using CPU crc32 instructions
      2014-11-08 11:00:54 6628 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      2014-11-08 11:00:54 6628 [Note] InnoDB: Completed initialization of buffer pool
      2014-11-08 11:00:54 6628 [Note] InnoDB: Highest supported file format is Barracuda.
      2014-11-08 11:00:54 6628 [Note] InnoDB: 128 rollback segment(s) are active.
      2014-11-08 11:00:54 6628 [Note] InnoDB: Waiting for purge to start
      2014-11-08 11:00:54 6628 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1787080
      2014-11-08 11:00:54 6628 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
      2014-11-08 11:00:54 6628 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
      2014-11-08 11:00:54 6628 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
      2014-11-08 11:00:54 6628 [Note] - '127.0.0.1' resolves to '127.0.0.1';
      2014-11-08 11:00:54 6628 [Note] Server socket created on IP: '127.0.0.1'.
      2014-11-08 11:00:54 6628 [Note] Event Scheduler: Loaded 0 events
      2014-11-08 11:00:54 6628 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '5.6.21-70.0' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona Server (GPL), Release 70.0, Revision 688
      10:01:01 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.
      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.
      Please help us make Percona Server better by reporting any
      bugs at http://bugs.percona.com/

      key_buffer_size=16777216
      read_buffer_size=131072
      max_used_connections=1
      max_threads=153
      thread_count=1
      connection_count=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 77372 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f9c45e6c000
      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 = 7f9c764d8e20 thread_stack 0x30000
      /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x8fff2b]
      /usr/sbin/mysqld(handle_fatal_signal+0x369)[0x651369]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xfc90)[0x7f9c74c41c90]
      /usr/sbin/mysqld[0xabd1bd]
      /usr/sbin/mysqld[0xab06a7]
      /usr/sbin/mysqld[0xab1475]
      /usr/sbin/mysqld[0xab3b9e]
      /usr/sbin/mysqld[0xabe2e6]
      /usr/sbin/mysqld[0xa421d0]
      /usr/sbin/mysqld[0xa42f07]
      /usr/sbin/mysqld[0xa43544]
      /usr/sbin/mysqld[0xa4e4bb]
      /usr/sbin/mysqld[0x9b89a1]
      /usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0xbf)[0x58ffaf]
      /usr/sbin/mysqld(Z12write_recordP3THDP5TABLEP9COPY_INFOS4+0x86)[0x6c1fb6]
      /usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xf0d)[0x6c530d]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2334)[0x6dd4e4]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x640)[0x6e2680]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x21e5)[0x6e4ea5]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x245)[0x6aa855]
      /usr/sbin/mysqld(handle_one_connection+0x39)[0x6aa8a9]
      /usr/sbin/mysqld(pfs_spawn_thread+0x140)[0x944e80]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x80a5)[0x7f9c74c3a0a5]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f9c7435284d]

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

      You may download the Percona Server operations manual by visiting
      http://www.percona.com/software/percona-server/. You may find information
      in the manual which will help you identify the cause of the crash.
      141108 11:01:01 mysqld_safe Number of processes running now: 0
      141108 11:01:01 mysqld_safe mysqld restarted
      2014-11-08 11:01:01 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
      2014-11-08 11:01:01 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
      2014-11-08 11:01:01 6749 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
      2014-11-08 11:01:01 6749 [Note] Plugin 'FEDERATED' is disabled.
      2014-11-08 11:01:01 6749 [Note] InnoDB: Using atomics to ref count buffer pool pages
      2014-11-08 11:01:01 6749 [Note] InnoDB: The InnoDB memory heap is disabled
      2014-11-08 11:01:01 6749 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2014-11-08 11:01:01 6749 [Note] InnoDB: Memory barrier is not used
      2014-11-08 11:01:01 6749 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2014-11-08 11:01:01 6749 [Note] InnoDB: Using Linux native AIO
      2014-11-08 11:01:01 6749 [Note] InnoDB: Using CPU crc32 instructions
      2014-11-08 11:01:01 6749 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      2014-11-08 11:01:01 6749 [Note] InnoDB: Completed initialization of buffer pool
      2014-11-08 11:01:01 6749 [Note] InnoDB: Highest supported file format is Barracuda.
      2014-11-08 11:01:01 6749 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1787090
      2014-11-08 11:01:01 6749 [Note] InnoDB: Database was not shutdown normally!
      2014-11-08 11:01:01 6749 [Note] InnoDB: Starting crash recovery.
      2014-11-08 11:01:01 6749 [Note] InnoDB: Reading tablespace information from the .ibd files...
      2014-11-08 11:01:01 6749 [Note] InnoDB: Restoring possible half-written data pages
      2014-11-08 11:01:01 6749 [Note] InnoDB: from the doublewrite buffer...
      InnoDB: Doing recovery: scanned up to log sequence number 1835831
      2014-11-08 11:01:01 6749 [Note] InnoDB: Starting an apply batch of log records to the database...
      InnoDB: Progress in percent: 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
      InnoDB: Apply batch completed
      2014-11-08 11:01:02 6749 [Note] InnoDB: 128 rollback segment(s) are active.
      2014-11-08 11:01:02 6749 [Note] InnoDB: Waiting for purge to start
      2014-11-08 11:01:02 6749 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 1835831
      2014-11-08 11:01:02 6749 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
      2014-11-08 11:01:02 6749 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
      2014-11-08 11:01:02 6749 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
      2014-11-08 11:01:02 6749 [Note] - '127.0.0.1' resolves to '127.0.0.1';
      2014-11-08 11:01:02 6749 [Note] Server socket created on IP: '127.0.0.1'.
      2014-11-08 11:01:02 6749 [Note] Event Scheduler: Loaded 0 events
      2014-11-08 11:01:02 6749 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '5.6.21-70.0' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona Server (GPL), Release 70.0, Revision 688

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            lpjirasync lpjirasync (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Smart Checklist