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

During delete: InnoDB: Assertion failure in thread 139757855127296 in file buf0buf.cc line 4803

    XMLWordPrintable

Details

    Description

      I have a script running through and deleting rows a fairly large table ( ~150 GB ) on a day - by - day.. there's around 90-150k+ rows per day (to be clear, its a delete .. between StartDay and EndDay kind of query)

      My particular problem is that I'm also trying to restore a different table in the same DB, and the restore keeps failing. Could be related.

      I noticed the infamous:

      ERROR 2013 (HY000) at line 18594: Lost connection to MySQL server during query
      

      In both cases.

      In that script, occasionally, and now I'm doing a load of a large table (same DB, different table) I dumped (using mysqldump, default options), truncated, and would now like to restore, and I get the same error. max_allowed_packet is set to 128 MB, and also, I just dumped this table, and settings have not changed since the data was inserted - so weird that mysqldump could generate things that you cannot re-insert. So, I went to the logs:

      Looking through the logs I noticed this stack trace appearing periodically (note in this, and other logs, I replaced some stuff with <> because I didn't want it public):

      2017-01-28  0:40:20 139757855127296 [ERROR] InnoDB: Block in space_id 0 in file /var/lib/mysql/ibdata1 encrypted.
      2017-01-28  0:40:20 139757855127296 [ERROR] InnoDB: However key management plugin or used key_id 359 is not found or used encryption algorithm or method does not match.
      2017-01-28  0:40:20 139757855127296 [ERROR] InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file.
      2017-01-28  0:40:20 139757855127296 [ERROR] InnoDB: Block in space_id 0 in file /var/lib/mysql/ibdata1 encrypted.
      2017-01-28  0:40:20 139757855127296 [ERROR] InnoDB: However key management plugin or used key_id 359 is not found or used encryption algorithm or method does not match.
      2017-01-28  0:40:20 139757855127296 [ERROR] InnoDB: Marking tablespace as missing. You may drop this table or install correct key management plugin and key file.
      2017-01-28 00:40:20 7f1be94f3700  InnoDB: Assertion failure in thread 139757855127296 in file buf0buf.cc line 4803
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      170128  0:40:20 [ERROR] mysqld got signal 6 ;
      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.13-MariaDB
      key_buffer_size=1048576
      read_buffer_size=1048576
      max_used_connections=159
      max_threads=1002
      thread_count=137
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3099672 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f1bdd23f008
      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 = 0x7f1be94f2d40 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f208977ee0b]
      /usr/sbin/mysqld(handle_fatal_signal+0x475)[0x7f20892df055]
      /lib64/libpthread.so.0(+0x39f3c0f710)[0x7f20888e5710]
      /lib64/libc.so.6(gsignal+0x35)[0x7f2086d0d625]
      /lib64/libc.so.6(abort+0x175)[0x7f2086d0ee05]
      /usr/sbin/mysqld(+0x87d188)[0x7f2089592188]
      /usr/sbin/mysqld(+0x894c68)[0x7f20895a9c68]
      /usr/sbin/mysqld(+0x89577f)[0x7f20895aa77f]
      /usr/sbin/mysqld(+0x874a6f)[0x7f2089589a6f]
      /usr/sbin/mysqld(+0x8f5e50)[0x7f208960ae50]
      /usr/sbin/mysqld(+0x841953)[0x7f2089556953]
      /usr/sbin/mysqld(+0x845c99)[0x7f208955ac99]
      /usr/sbin/mysqld(+0x854075)[0x7f2089569075]
      /usr/sbin/mysqld(+0x74fbf7)[0x7f2089464bf7]
      /usr/sbin/mysqld(+0x753545)[0x7f2089468545]
      /usr/sbin/mysqld(+0x850bd8)[0x7f2089565bd8]
      /usr/sbin/mysqld(+0x7ecacd)[0x7f2089501acd]
      /usr/sbin/mysqld(+0x7f6438)[0x7f208950b438]
      /usr/sbin/mysqld(+0x7faa02)[0x7f208950fa02]
      /usr/sbin/mysqld(+0x7da48c)[0x7f20894ef48c]
      /usr/sbin/mysqld(+0x7c654c)[0x7f20894db54c]
      /usr/sbin/mysqld(+0x7c8ae0)[0x7f20894ddae0]
      /usr/sbin/mysqld(+0x7f5979)[0x7f208950a979]
      /usr/sbin/mysqld(+0x7fa1b1)[0x7f208950f1b1]
      /usr/sbin/mysqld(+0x7fa973)[0x7f208950f973]
      /usr/sbin/mysqld(+0x7d98e3)[0x7f20894ee8e3]
      /usr/sbin/mysqld(+0x728747)[0x7f208943d747]
      /usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f20892e8ecf]
      /usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f20893f2eaf]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f20891735f1]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f208917590d]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f208917856b]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f2089178b1b]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f20892344af]
      /usr/sbin/mysqld(handle_one_connection+0x47)[0x7f2089234607]
      /lib64/libpthread.so.0(+0x39f3c079d1)[0x7f20888dd9d1]
      /lib64/libc.so.6(clone+0x6d)[0x7f2086dc38fd]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f1c06876020): is an invalid pointer
      Connection ID (thread ID): 30164
      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
       
      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.
      170128 00:40:20 mysqld_safe Number of processes running now: 0
      170128 00:40:20 mysqld_safe mysqld restarted
      2017-01-28  0:40:20 139979614677024 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
      2017-01-28  0:40:20 139979614677024 [Warning] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set
      2017-01-28  0:40:20 139979614677024 [Note] /usr/sbin/mysqld (mysqld 10.1.13-MariaDB) starting as process 28049 ...
      2017-01-28  0:40:20 139979614677024 [Note] Using unique option prefix 'myisam_recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead.
      2017-01-28 00:40:20 7f4f8b356820 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-01-28  0:40:20 139979614677024 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2017-01-28  0:40:20 139979614677024 [Note] InnoDB: The InnoDB memory heap is disabled
      2017-01-28  0:40:20 139979614677024 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2017-01-28  0:40:20 139979614677024 [Note] InnoDB: Memory barrier is not used
      2017-01-28  0:40:20 139979614677024 [Note] InnoDB: Compressed tables use zlib 1.2.3
      2017-01-28  0:40:20 139979614677024 [Note] InnoDB: Using Linux native AIO
      2017-01-28  0:40:20 139979614677024 [Note] InnoDB: Using SSE crc32 instructions
      2017-01-28  0:40:20 139979614677024 [Note] InnoDB: Initializing buffer pool, size = 16.0G
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: Completed initialization of buffer pool
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: Highest supported file format is Barracuda.
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2400612224831
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: Database was not shutdown normally!
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: Starting crash recovery.
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: Reading tablespace information from the .ibd files...
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: Restoring possible half-written data pages 
      2017-01-28  0:40:21 139979614677024 [Note] InnoDB: from the doublewrite buffer...
      InnoDB: Doing recovery: scanned up to log sequence number 2400617467392
      InnoDB: Doing recovery: scanned up to log sequence number 2400622710272
      [
       .... removed a long sequence of these from the bug report, for conciseness
      ]
      InnoDB: Doing recovery: scanned up to log sequence number 2400633196032
      InnoDB: Doing recovery: scanned up to log sequence number 2400643681792
      InnoDB: Doing recovery: scanned up to log sequence number 2400654167552
      nnoDB: Doing recovery: scanned up to log sequence number 2402258488832
      InnoDB: Doing recovery: scanned up to log sequence number 2402263731712
      InnoDB: Doing recovery: scanned up to log sequence number 2402264584622
      InnoDB: 6 transaction(s) which must be rolled back or cleaned up
      InnoDB: in total 986008 row operations to undo
      InnoDB: Trx id counter is 933044992
      2017-01-28  0:40:39 139979614677024 [Note] InnoDB: Starting an apply batch of log records to the database...
      InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 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
      InnoDB: Last MySQL binlog file position 0 81485718, file name /var/lib/mysql/mysql-bin.001936
      InnoDB: Starting in background the rollback of uncommitted transactions
      2017-01-28  0:40:59 139979614677024 [Note] InnoDB: 128 rollback segment(s) are active.
      2017-01-28 00:40:59 7f4afebff700  InnoDB: Rolling back trx with id 933044670, 3 rows to undo
      2017-01-28  0:40:59 139979614677024 [Note] InnoDB: Waiting for purge to start
      2017-01-28  0:40:59 139960078300928 [Note] InnoDB: Rollback of trx with id 933044670 completed
      2017-01-28 00:40:59 7f4afebff700  InnoDB: Rolling back trx with id 933044663, 1 rows to undo
      2017-01-28  0:40:59 139960078300928 [Note] InnoDB: Rollback of trx with id 933044663 completed
      2017-01-28 00:40:59 7f4afebff700  InnoDB: Rolling back trx with id 933044662, 1 rows to undo
      2017-01-28  0:40:59 139960078300928 [Note] InnoDB: Rollback of trx with id 933044662 completed
      2017-01-28 00:40:59 7f4afebff700  InnoDB: Rolling back trx with id 933044661, 1 rows to undo
      2017-01-28  0:40:59 139960078300928 [Note] InnoDB: Rollback of trx with id 933044661 completed
      2017-01-28 00:40:59 7f4afebff700  InnoDB: Rolling back trx with id 933044660, 1 rows to undo
      2017-01-28  0:40:59 139960078300928 [Note] InnoDB: Rollback of trx with id 933044660 completed
      2017-01-28 00:40:59 7f4afebff700  InnoDB: Rolling back trx with id 933034392, 986001 rows to undo
       
      InnoDB: Progress in percents: 12017-01-28  0:40:59 139979614677024 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 2402264584622
       2 3 4 5 6 7 8 9 10 112017-01-28  0:42:23 139959778379520 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2017-01-28  0:42:23 139979614677024 [Note] Plugin 'FEEDBACK' is disabled.
      2017-01-28  0:42:23 139979614677024 [Note] Recovering after a crash using /var/lib/mysql/mysql-bin
      2017-01-28  0:42:24 139979614677024 [Note] Starting crash recovery...
      2017-01-28  0:42:24 139979614677024 [Note] Crash recovery finished.
      2017-01-28  0:42:24 139979614677024 [Note] Server socket created on IP: '::'.
      2017-01-28  0:42:24 139979614677024 [Note] Reading of all Master_info entries succeded
      2017-01-28  0:42:24 139979614677024 [Note] Added new Master_info '' to hash table
      2017-01-28  0:42:24 139979614677024 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.1.13-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
       12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 352017-01-28  0:43:20 139959712200448 [Note] Start binlog_dump to slave_server(994593286), pos(mysql-bin.001936, 81485718)
      2017-01-28  0:43:20 139959712466688 [Note] Start binlog_dump to slave_server(511624938), pos(mysql-bin.001936, 81485718)
       36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 832017-01-28  0:44:32 139979614136064 [Warning] Aborted connection 13 to db: '<>' user: '<>' host: '<>org' (Unknown error)
       84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 1002017-01-28  0:44:55 139960078300928 [Note] InnoDB: Rollback of trx with id 933034392 completed
      2017-01-28 00:44:55 7f4afebff700  InnoDB: Rollback of non-prepared transactions completed
      2017-01-28  0:46:23 139959679309568 [Warning] IP address '10.7.50.19' could not be resolved: Name or service not known
      2017-01-28  0:48:21 139959702611712 [Warning] Aborted connection 579 to db: '<removed for bug report>' user: '<removed for bug report>' host: '<removed for bug report>.org' (Unknown error)
      

      To give you an idea of how it's repeating, I grepped:

      $ grep -Hinr "/usr/sbin/mysqld(_Z" mysqld-error.log
      mysqld-error.log:91354:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7fef6b633ecf]
      mysqld-error.log:91355:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7fef6b73deaf]
      mysqld-error.log:91356:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7fef6b4be5f1]
      mysqld-error.log:91357:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7fef6b4c090d]
      mysqld-error.log:91358:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7fef6b4c356b]
      mysqld-error.log:91359:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7fef6b4c3b1b]
      mysqld-error.log:91360:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7fef6b57f4af]
      mysqld-error.log:95885:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7fc2c8a85ecf]
      mysqld-error.log:95886:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7fc2c8b8feaf]
      mysqld-error.log:95887:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7fc2c89105f1]
      mysqld-error.log:95888:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7fc2c891290d]
      mysqld-error.log:95889:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7fc2c891556b]
      mysqld-error.log:95890:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7fc2c8915b1b]
      mysqld-error.log:97544:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f9f422b1ecf]
      mysqld-error.log:97545:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f9f423bbeaf]
      mysqld-error.log:97546:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f9f4213c5f1]
      mysqld-error.log:97547:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f9f4213e90d]
      mysqld-error.log:97548:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f9f4214156b]
      mysqld-error.log:97549:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f9f42141b1b]
      mysqld-error.log:97550:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f9f421fd4af]
      mysqld-error.log:98399:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f1dc3798ecf]
      mysqld-error.log:98400:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f1dc38a2eaf]
      mysqld-error.log:98401:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f1dc36235f1]
      mysqld-error.log:98402:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f1dc362590d]
      mysqld-error.log:98403:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f1dc362856b]
      mysqld-error.log:98404:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f1dc3628b1b]
      mysqld-error.log:98405:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f1dc36e44af]
      mysqld-error.log:99373:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f3ce0493ecf]
      mysqld-error.log:99374:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f3ce059deaf]
      mysqld-error.log:99375:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f3ce031e5f1]
      mysqld-error.log:99376:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f3ce032090d]
      mysqld-error.log:99377:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f3ce032356b]
      mysqld-error.log:99378:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f3ce0323b1b]
      mysqld-error.log:99379:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f3ce03df4af]
      mysqld-error.log:99906:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f34e4ffdecf]
      mysqld-error.log:99907:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f34e5107eaf]
      mysqld-error.log:99908:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f34e4e885f1]
      mysqld-error.log:99909:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f34e4e8a90d]
      mysqld-error.log:99910:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f34e4e8d56b]
      mysqld-error.log:99911:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f34e4e8db1b]
      mysqld-error.log:99912:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f34e4f494af]
      mysqld-error.log:100713:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f0004453ecf]
      mysqld-error.log:100714:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f000455deaf]
      mysqld-error.log:100715:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f00042de5f1]
      mysqld-error.log:100716:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f00042e090d]
      mysqld-error.log:100717:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f00042e356b]
      mysqld-error.log:101089:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f5287e28ecf]
      mysqld-error.log:101090:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f5287f32eaf]
      mysqld-error.log:101091:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f5287cb35f1]
      mysqld-error.log:101092:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f5287cb590d]
      mysqld-error.log:101093:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f5287cb856b]
      mysqld-error.log:101094:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f5287cb8b1b]
      mysqld-error.log:101095:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f5287d744af]
      mysqld-error.log:101560:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f5f3cb0decf]
      mysqld-error.log:101561:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f5f3cc17eaf]
      mysqld-error.log:101562:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f5f3c9985f1]
      mysqld-error.log:101563:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f5f3c99a90d]
      mysqld-error.log:101564:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f5f3c99d56b]
      mysqld-error.log:101565:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f5f3c99db1b]
      mysqld-error.log:101566:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f5f3ca594af]
      mysqld-error.log:101928:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7fc4865a2ecf]
      mysqld-error.log:101929:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7fc4866aceaf]
      mysqld-error.log:101930:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7fc48642d5f1]
      mysqld-error.log:101931:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7fc48642f90d]
      mysqld-error.log:101932:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7fc48643256b]
      mysqld-error.log:101933:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7fc486432b1b]
      mysqld-error.log:101934:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7fc4864ee4af]
      mysqld-error.log:102395:/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x23f)[0x7f20892e8ecf]
      mysqld-error.log:102396:/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyP13select_result+0x110f)[0x7f20893f2eaf]
      mysqld-error.log:102397:/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x7061)[0x7f20891735f1]
      mysqld-error.log:102398:/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f208917590d]
      mysqld-error.log:102399:/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f208917856b]
      mysqld-error.log:102400:/usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f2089178b1b]
      mysqld-error.log:102401:/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f20892344af]
      

      Memory usage seems OK whenever I check it:

      $ free -m
                   total       used       free     shared    buffers     cached
      Mem:         64320      63968        352          0        140      43698
      -/+ buffers/cache:      20129      44191
      Swap:         4095        213       3882
      

      No idea if all of my lost connections are related to the issue - but it does appear at least some of my lost connections are related to it.

      Note that in the script doing the deletes, I have it looping and sleeping and retrying on failure:

      2017-01-28 01:59:07.325604 Issue with query: 2003: Can't connect to MySQL server on '<>' (111) sleeping and trying again
      Deleting 623366 from 2016-10-27 18:52:42.588751 to 2016-10-28 18:52:42.588751
       
      2017-01-28 01:59:12.331931 Issue with query: 2003: Can't connect to MySQL server on '<>' (111) sleeping and trying again
      Deleting 623366 from 2016-10-27 18:52:42.588751 to 2016-10-28 18:52:42.588751
       
      2017-01-28 01:59:17.338245 Issue with query: 2003: Can't connect to MySQL server on '<>' (111) sleeping and trying again
      

      In the try block, I open, get cursor, query, commit, close, so hopefully I'm not burning through connections or anything - it's a fairly straightforward python script. .... and I can make progress in the script, via retries, and just starting the script again.

      However, since the dump keeps failing, I can't restore the data.

      Attachments

        1. enable_encryption.preset
          0.7 kB
        2. custom-mysql.cnf
          4 kB
        3. my.cnf
          0.2 kB
        4. mysql-clients.cnf
          0.2 kB
        5. server.cnf
          1 kB
        6. tokudb.cnf
          0.3 kB
        7. ibdata1_page0.bin
          16 kB
        8. ibdata2_page0.bin
          16 kB
        9. my.cnf
          8 kB

        Issue Links

          Activity

            People

              jplindst Jan Lindström (Inactive)
              StuS Stu S
              Votes:
              1 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.