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

galera_sr.galera_sr_small_gcache: Test failure: signal 6; mysqltest: Can't connect to local MySQL server

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.4.3
    • 10.4.5
    • Galera, Tests
    • OS: CentOS Linux release 7.6.1810 (Core).

    Description

      MariaDB Server: 10.4.3-MariaDB-debug built from sources, commit: c4f39983652ca4490e83c6ef4b157494484f6b75.
      Galera4 lib: debug built from sources.

      Run: 

      ./mtr --suite galera_sr --force --big-test --max-test-fail=0 --parallel=auto

      stdout.log: (the whole file is attached: 190211_galera_sr_stdout_desktop.log)

      galera_sr.galera_sr_small_gcache 'innodb' w1 [ fail ]  timeout after 900 seconds
      		 
       
      		 
      mysqltest: Could not open connection 'default' after 500 attempts: 2002 Can't connect to local MySQL server through socket '/home/stepan/galera/git/10.4/server/mysql-test/var/tmp/1/mysqld.' (111)
      		 
       
      		 
      Program terminated with signal 6, Aborted.

      See also attached 190211_galera_sr.galera_sr_small_gcache-innodb.zip.

      Attachments

        1. 190211_galera_sr_stdout_desktop.log
          1.04 MB
          Stepan Patryshev

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-17046 Galera 4: Streaming replication

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              jplindst Jan Lindström (Inactive)
              stepan.patryshev Stepan Patryshev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.