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

innodb.innodb-64k failed in buildbot, lost connection to server





      innodb.innodb-64k 'innodb'               w2 [ fail ]
              Test ended at 2017-10-26 03:11:14
      CURRENT_TEST: innodb.innodb-64k
      mysqltest: At line 635: query 'update t2 set col150=@a' failed: 2013: Lost connection to MySQL server during query
      The result from queries just before the failure was:
      < snip >
        `COL181` text DEFAULT NULL,
        `COL182` text DEFAULT NULL,
        `COL183` text DEFAULT NULL,
        `COL184` text DEFAULT NULL,
        `COL185` text DEFAULT NULL,
        `COL186` text DEFAULT NULL,
        `COL187` text DEFAULT NULL,
        `COL188` text DEFAULT NULL,
        `COL189` text DEFAULT NULL,
        `COL190` text DEFAULT NULL,
        `COL191` text DEFAULT NULL,
        `COL192` text DEFAULT NULL,
        `COL193` text DEFAULT NULL,
        `COL194` text DEFAULT NULL,
        `COL195` text DEFAULT NULL,
        `COL196` text DEFAULT NULL,
        `COL197` text DEFAULT NULL
      update t2 set col150=@a;
      More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.2.10/mysql-test/var/2/log/innodb-64

      2017-10-26  3:11:12 2932595520 [Note] InnoDB: Uncompressed page, stored checksum in field1 2609818021, calculated checksums for field1: crc32 1225725904/2230021968, innodb 4240219472,  page type 10 == BLOB.none 3735928559, stored checksum in field2 2609818021, calculated checksums for field2: crc32 1225725904/2230021968, innodb 2875794546, none 3735928559,  page LSN 0 14755692, low 4 bytes of LSN at page end 14755692, page number (if stored to page already) 629, space id (if created with >= MySQL-4.1.1 and stored already) 10
      InnoDB: Page may be a BLOB page
      2017-10-26  3:11:12 2932595520 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
      171026  3:11:12 [ERROR] 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.
      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.2.10-MariaDB-debug-log
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61885 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0xa6305c38
      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 = 0xaecbd2a0 thread_stack 0x49000
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0xa6314380): update t2 set col150=@a
      Connection ID (thread ID): 8
      Status: NOT_KILLED


        Issue Links



              wlad Vladislav Vaintroub
              alice Alice Sherepa
              0 Vote for this issue
              5 Start watching this issue



                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.