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

`galera_3nodes.galera_gtid_2_cluster` fails

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: 10.4
    • Fix Version/s: N/A
    • Component/s: Galera, Tests
    • Labels:
      None

      Description

      galera_3nodes.galera_gtid_2_cluster 'innodb' w2 [ fail ]
      Test ended at 2020-02-19 06:13:16

      CURRENT_TEST: galera_3nodes.galera_gtid_2_cluster

      Failed to start mysqld.6
      mysqltest failed but provided no output

      • saving '/var/tmp/mtr/2/log/galera_3nodes.galera_gtid_2_cluster-innodb/' to '/var/tmp/mtr/log/galera_3nodes.galera_gtid_2_cluster-innodb/'

      Retrying test galera_3nodes.galera_gtid_2_cluster, attempt(2/3)...

      ***Warnings generated in error logs during shutdown after running tests: galera_3nodes.galera_gtid_2_cluster

      2020-02-19 6:13:12 0 [Warning] WSREP: error while trying to listen 'tcp://0.0.0.0:16021?socket.non_blocking=1', asio error 'bind: Address already in use'
      2020-02-19 6:13:12 0 [ERROR] WSREP: failed to open gcomm backend connection: 98: error while trying to listen 'tcp://0.0.0.0:16021?socket.non_blocking=1', asio error 'bind: Address already in use': 98 (Address already in use)
      2020-02-19 6:13:12 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():222: Failed to open backend connection: -98 (Address already in use)
      2020-02-19 6:13:12 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1614: Failed to open channel 'cluster2' at 'gcomm://127.0.0.1:16015': -98 (Address already in use)
      2020-02-19 6:13:12 0 [ERROR] WSREP: gcs connect failed: Address already in use
      2020-02-19 6:13:12 0 [ERROR] Plugin 'wsrep' init function returned error.
      2020-02-19 6:13:12 0 [ERROR] Plugin 'wsrep' registration as a STORAGE ENGINE failed.
      2020-02-19 6:13:12 0 [ERROR] Failed to initialize plugins.
      2020-02-19 6:13:12 0 [ERROR] Aborting

      galera_3nodes.galera_gtid_2_cluster 'innodb' w2 [ retry-fail ]
      Test ended at 2020-02-19 06:13:26

      CURRENT_TEST: galera_3nodes.galera_gtid_2_cluster
      CURRENT_TEST: galera_3nodes.galera_gtid_2_cluster

      Failed to start mysqld.5

      • skipping '/var/tmp/mtr/2/log/galera_3nodes.galera_gtid_2_cluster-innodb/'

      Test galera_3nodes.galera_gtid_2_cluster has failed 2 times, no more retries!

      ***Warnings generated in error logs during shutdown after running tests: galera_3nodes.galera_gtid_2_cluster

      WSREP_SST: [ERROR] rsync daemon port '16020' has been taken (20200219 06:13:19.128)
      2020-02-19 6:13:19 0 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_rsync --role 'joiner' --address '127.0.0.1:16020' --datadir '/var/tmp/mtr/2/mysqld.5/data/' --defaults-file '/var/tmp/mtr/2/my.cnf' --defaults-group-suffix '.5' --parent '16464' --binlog 'mysqld-bin' --binlog-index 'mysqld-bin.index' --mysqld-args --defaults-group-suffix=.5 --defaults-file=/var/tmp/mtr/2/my.cnf --log-output=file --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --core-file --loose-debug-sync-timeout=300
      2020-02-19 6:13:19 0 [ERROR] WSREP: Process completed with error: wsrep_sst_rsync --role 'joiner' --address '127.0.0.1:16020' --datadir '/var/tmp/mtr/2/mysqld.5/data/' --defaults-file '/var/tmp/mtr/2/my.cnf' --defaults-group-suffix '.5' --parent '16464' --binlog 'mysqld-bin' --binlog-index 'mysqld-bin.index' --mysqld-args --defaults-group-suffix=.5 --defaults-file=/var/tmp/mtr/2/my.cnf --log-output=file --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --core-file --loose-debug-sync-timeout=300: 16 (Device or resource busy)
      2020-02-19 6:13:19 2 [ERROR] WSREP: Failed to prepare for 'rsync' SST. Unrecoverable.
      2020-02-19 6:13:19 2 [ERROR] WSREP: SST request callback failed. This is unrecoverable, restart required.
      2020-02-19 6:13:18 0 [Warning] WSREP: error while trying to listen 'tcp://0.0.0.0:16021?socket.non_blocking=1', asio error 'bind: Address already in use'
      2020-02-19 6:13:18 0 [ERROR] WSREP: failed to open gcomm backend connection: 98: error while trying to listen 'tcp://0.0.0.0:16021?socket.non_blocking=1', asio error 'bind: Address already in use': 98 (Address already in use)
      2020-02-19 6:13:18 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():222: Failed to open backend connection: -98 (Address already in use)
      2020-02-19 6:13:18 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1614: Failed to open channel 'cluster2' at 'gcomm://127.0.0.1:16015': -98 (Address already in use)
      2020-02-19 6:13:18 0 [ERROR] WSREP: gcs connect failed: Address already in use
      2020-02-19 6:13:18 0 [ERROR] Plugin 'wsrep' init function returned error.
      2020-02-19 6:13:18 0 [ERROR] Plugin 'wsrep' registration as a STORAGE ENGINE failed.
      2020-02-19 6:13:18 0 [ERROR] Failed to initialize plugins.
      2020-02-19 6:13:18 0 [ERROR] Aborting

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jplindst Jan Lindström
              Reporter:
              tturenko Timofey Turenko
              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.