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

galera.galera_var_node_address fails in buildot, Failed to start mysqld or "Transport endpoint is not connected"

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.1, 10.2
    • N/A
    • Galera, Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-stretch-ppc64le/builds/1067

      galera.galera_var_node_address 'innodb_plugin' w3 [ fail ]
              Test ended at 2017-09-21 06:36:52
       
      CURRENT_TEST: galera.galera_var_node_address
       
       
      Failed to start mysqld.1
      mysqltest failed but provided no output
       
       
       - saving '/dev/shm/var/3/log/galera.galera_var_node_address-innodb_plugin/' to '/dev/shm/var/log/galera.galera_var_node_address-innodb_plugin/'
       
      Retrying test galera.galera_var_node_address, attempt(2/3)...
       
      worker[3] > Restart  - not started
      

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-jessie-amd64/builds/2907/steps/mtr/logs/stdio

      galera.galera_var_node_address 'innodb_plugin' w1 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-10-06 12:35:49
      line
      2017-10-06 12:35:43 140182460294912 [Warning] WSREP: Failed to send SYNC signal: -107 (Transport endpoint is not connected)
      ^ Found warnings in /dev/shm/var/1/log/mysqld.2.err
      ok
      

      Attachments

        Issue Links

          Activity

            People

              jplindst Jan Lindström (Inactive)
              elenst Elena Stepanova
              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.