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

innodb_zip.wl6501_1, parts.partition_debug_innodb fail in buildbot with errno 2001: 'Can't create UNIX socket (24)'

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.2(EOL)
    • N/A
    • Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/5987/steps/test_3/logs/stdio

      innodb_zip.wl6501_1 'xtradb'             w2 [ fail ]
              Test ended at 2016-09-25 14:42:55
       
      CURRENT_TEST: innodb_zip.wl6501_1
      mysqltest: At line 448: query 'show status' failed with wrong errno 2001: 'Can't create UNIX socket (24)', instead of 0...
       
      The result from queries just before the failure was:
      < snip >
      select count(*) from t3;
      count(*)
      0
      select count(*) from t4;
      count(*)
      3
      select count(*) from t5;
      ERROR 42S02: Table 'test.t5' doesn't exist
      select count(*) from t6;
      count(*)
      3
      set session debug="+d,ib_trunc_crash_after_redo_log_write_complete";
      Warnings:
      Warning	1287	'@@debug' is deprecated and will be removed in a future release. Please use '@@debug_dbug' instead
      "---debug ib_trunc_crash_after_redo_log_write_complete point---"
      # Write file to make mysql-test-run.pl expect crash and restart
      # Run the crashing query
      truncate table t4;
      ERROR HY000: Lost connection to MySQL server during query
      # Restart the MySQL server
       
      More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.2.2/mysql-test/var/2/log/wl6501_1.log
       
       - saving '/mnt/buildbot/build/mariadb-10.2.2/mysql-test/var/2/log/innodb_zip.wl6501_1-xtradb/' to '/mnt/buildbot/build/mariadb-10.2.2/mysql-test/var/log/innodb_zip.wl6501_1-xtradb/'
       
      Retrying test innodb_zip.wl6501_1, attempt(2/3)...
      

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/5987/steps/test_6/logs/stdio

      parts.partition_debug_innodb 'xtradb'    w1 [ fail ]
              Test ended at 2016-09-25 17:02:48
       
      CURRENT_TEST: parts.partition_debug_innodb
      mysqltest: In included file "./include/wait_until_connected_again.inc": 
      included from ./suite/parts/inc/partition_crash.inc at line 22:
      included from ./suite/parts/inc/partition_crash_change.inc at line 10:
      included from ./suite/parts/inc/partition_mgm_crash.inc at line 33:
      included from /mnt/buildbot/build/mariadb-10.2.2/mysql-test/suite/parts/t/partition_debug_innodb.test at line 69:
      At line 23: query 'show status' failed with wrong errno 2001: 'Can't create UNIX socket (24)', instead of 0...
       
      The result from queries just before the failure was:
      < snip >
      a	b
      1	Original from partition p0
      11	Original from partition p1
      12	Original from partition p1
      13	Original from partition p1
      14	Original from partition p1
      2	Original from partition p0
      3	Original from partition p0
      4	Original from partition p0
      ALTER TABLE t1 REORGANIZE PARTITION p10 INTO
      (PARTITION p10 VALUES IN (10,11,12,13,14,15,16,17,18,19),
      PARTITION p20 VALUES IN (20,21,22,23,24,25,26,27,28,29));
      ERROR HY000: Lost connection to MySQL server during query
      # State after crash (before recovery)
      #sql-t1.frm
      #sql-t1.par
      t1#P#p0.ibd
      t1#P#p10.ibd
      t1.frm
      t1.par
      

      Attachments

        Issue Links

          Activity

            People

              georg Georg Richter
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.