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

SST failing when enabling IPV6

Details

    Description

      Folks,

      After configuring the MariaDB Cluster with the settings to support SST over IPV6, with the below:

      [sst]
      		 
      sockopt="pf=ip6"

      I started seeing the below on error log when the SST fails:

      WSREP_SST: [INFO] Evaluating timeout -k 110 100 socat -u TCP-LISTEN:4444,reuseaddrpf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 18:34:41.545)
      		 
      2019/12/02 18:34:41 socat[15907] E parseopts(): unknown option "reuseaddrpf"

      I hacked it, so it works, but, weird case and easy to fix:

      [sst]
      		 
      sockopt=",pf=ip6"
      		 
      --
      		 
      WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr,pf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 20:30:40.546)
      		 
      WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20191202 20:30:40.547)
      		 
      removed '/var/lib/mysql/aria_log_control'
      		 
      removed '/var/lib/mysql/aria_log.00000001'
      		 
      removed '/var/lib/mysql/ibdata1'
      		 
      removed '/var/lib/mysql/ib_logfile1'
      		 
      removed '/var/lib/mysql/mysql.sock'
      		 
      ...

      Can we fix it?

      Thanks!

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18797 Make mariabackup/xtrabackup-v2 SST script autodetect ipv6 addresses and add relevant socat option

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            wagnerbianchi Wagner Bianchi (Inactive) created issue -
            wagnerbianchi Wagner Bianchi (Inactive) made changes -
            Field Original Value New Value
            Description Folks,

            After configuring the MariaDB Cluster with the settings to support SST over IPV6, with the below:

            {code:java}
            [sst]
            sockopt="pf=ip6"
            {code}

            I started seeing the below on error log when the SST fails:
            WSREP_SST: [INFO] Evaluating timeout -k 110 100 socat -u TCP-LISTEN:4444,reuseaddrpf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 18:34:41.545)
            2019/12/02 18:34:41 socat[15907] E parseopts(): unknown option "reuseaddrpf"

            I hacked it, so it works, but, weird case and easy to fix:

            {code:java}
            [sst]
            sockopt=",pf=ip6"
            --
            WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr,pf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 20:30:40.546)
            WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20191202 20:30:40.547)
            removed '/var/lib/mysql/aria_log_control'
            removed '/var/lib/mysql/aria_log.00000001'
            removed '/var/lib/mysql/ibdata1'
            removed '/var/lib/mysql/ib_logfile1'
            removed '/var/lib/mysql/mysql.sock'
            {code}


            Can we fix it?

            Thanks!             		Folks,

            After configuring the MariaDB Cluster with the settings to support SST over IPV6, with the below:

            {code:java}
            [sst]
            sockopt="pf=ip6"
            {code}

            I started seeing the below on error log when the SST fails:

            {code:java}
            WSREP_SST: [INFO] Evaluating timeout -k 110 100 socat -u TCP-LISTEN:4444,reuseaddrpf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 18:34:41.545)
            2019/12/02 18:34:41 socat[15907] E parseopts(): unknown option "reuseaddrpf"
            {code}


            I hacked it, so it works, but, weird case and easy to fix:

            {code:java}
            [sst]
            sockopt=",pf=ip6"
            --
            WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr,pf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 20:30:40.546)
            WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20191202 20:30:40.547)
            removed '/var/lib/mysql/aria_log_control'
            removed '/var/lib/mysql/aria_log.00000001'
            removed '/var/lib/mysql/ibdata1'
            removed '/var/lib/mysql/ib_logfile1'
            removed '/var/lib/mysql/mysql.sock'
            {code}


            Can we fix it?

            Thanks!
            wagnerbianchi Wagner Bianchi (Inactive) made changes -
            Description Folks,

            After configuring the MariaDB Cluster with the settings to support SST over IPV6, with the below:

            {code:java}
            [sst]
            sockopt="pf=ip6"
            {code}

            I started seeing the below on error log when the SST fails:

            {code:java}
            WSREP_SST: [INFO] Evaluating timeout -k 110 100 socat -u TCP-LISTEN:4444,reuseaddrpf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 18:34:41.545)
            2019/12/02 18:34:41 socat[15907] E parseopts(): unknown option "reuseaddrpf"
            {code}


            I hacked it, so it works, but, weird case and easy to fix:

            {code:java}
            [sst]
            sockopt=",pf=ip6"
            --
            WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr,pf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 20:30:40.546)
            WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20191202 20:30:40.547)
            removed '/var/lib/mysql/aria_log_control'
            removed '/var/lib/mysql/aria_log.00000001'
            removed '/var/lib/mysql/ibdata1'
            removed '/var/lib/mysql/ib_logfile1'
            removed '/var/lib/mysql/mysql.sock'
            {code}


            Can we fix it?

            Thanks!             		Folks,

            After configuring the MariaDB Cluster with the settings to support SST over IPV6, with the below:

            {code:java}
            [sst]
            sockopt="pf=ip6"
            {code}

            I started seeing the below on error log when the SST fails:

            {code:java}
            WSREP_SST: [INFO] Evaluating timeout -k 110 100 socat -u TCP-LISTEN:4444,reuseaddrpf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 18:34:41.545)
            2019/12/02 18:34:41 socat[15907] E parseopts(): unknown option "reuseaddrpf"
            {code}


            I hacked it, so it works, but, weird case and easy to fix:

            {code:java}
            [sst]
            sockopt=",pf=ip6"
            --
            WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr,pf=ip6 stdio | mbstream -x; RC=( ${PIPESTATUS[@]} ) (20191202 20:30:40.546)
            WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20191202 20:30:40.547)
            removed '/var/lib/mysql/aria_log_control'
            removed '/var/lib/mysql/aria_log.00000001'
            removed '/var/lib/mysql/ibdata1'
            removed '/var/lib/mysql/ib_logfile1'
            removed '/var/lib/mysql/mysql.sock'
            ...
            {code}


            Can we fix it?

            Thanks!
            elenst Elena Stepanova made changes -
            Fix Version/s 10.3 [ 22126 ]
            Assignee Jan Lindström [ jplindst ]
            sysprg Julius Goryavsky made changes -
            Assignee Jan Lindström [ jplindst ] Julius Goryavsky [ sysprg ]
            sysprg Julius Goryavsky made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            sysprg Julius Goryavsky made changes -
            Status Confirmed [ 10101 ] In Progress [ 3 ]
            sysprg Julius Goryavsky added a comment -

            Fixed + refactoring:
            https://github.com/MariaDB/server/commit/f8ee28aaafaf16c8fd1b74154bcf193c86f7f764
            http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.2-MDEV-21192-galera

            sysprg Julius Goryavsky added a comment - Fixed + refactoring: https://github.com/MariaDB/server/commit/f8ee28aaafaf16c8fd1b74154bcf193c86f7f764 http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.2-MDEV-21192-galera
            sysprg Julius Goryavsky made changes -
            Assignee Julius Goryavsky [ sysprg ] Jan Lindström [ jplindst ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            sysprg Julius Goryavsky made changes -
            jplindst Jan Lindström (Inactive) added a comment -

            ok to push

            jplindst Jan Lindström (Inactive) added a comment - ok to push
            jplindst Jan Lindström (Inactive) made changes -
            Assignee Jan Lindström [ jplindst ] Julius Goryavsky [ sysprg ]
            Status In Review [ 10002 ] Stalled [ 10000 ]
            sysprg Julius Goryavsky made changes -
            Fix Version/s 10.6.2 [ 25800 ]
            Fix Version/s 10.2.39 [ 25731 ]
            Fix Version/s 10.3.30 [ 25732 ]
            Fix Version/s 10.4.20 [ 25733 ]
            Fix Version/s 10.5.11 [ 25734 ]
            Fix Version/s 10.3 [ 22126 ]
            Resolution Fixed [ 1 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 101537 ] MariaDB v4 [ 157034 ]

            People

              sysprg Julius Goryavsky
              wagnerbianchi Wagner Bianchi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.