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

MariaDB Galera mysqldump fails to produce error messages, rsync_wan does not exist

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.5.28a-galera
    • Fix Version/s: 5.5.34-galera
    • Component/s: None
    • Labels:
    • Environment:
      Ubuntu 12.04, repository install

      Description

      Following the instructions on:
      https://kb.askmonty.org/en/getting-started-with-mariadb-galera-cluster/

      The mysqldump SST Script does not seem to work by default. I get an "no such file or directory" error.

      The script has a number of lines where it attempts to use a function 'err', only the function isn't defined in the script:

      if test -z "$WSREP_SST_OPT_USER";  then err "USER cannot be nil";  exit $EINVAL; fi
      if test -z "$WSREP_SST_OPT_HOST";  then err "HOST cannot be nil";  exit $EINVAL; fi
      if test -z "$WSREP_SST_OPT_PORT";  then err "PORT cannot be nil";  exit $EINVAL; fi
      if test -z "$WSREP_SST_OPT_LPORT"; then err "LPORT cannot be nil"; exit $EINVAL; fi
      if test -z "$WSREP_SST_OPT_SOCKET";then err "SOCKET cannot be nil";exit $EINVAL; fi
      if test -z "$WSREP_SST_OPT_GTID";  then err "GTID cannot be nil";  exit $EINVAL; fi
      

      rsync_wan as described does not exist. But rsync works fine.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment - - edited

            Hi Tomas,

            Could you please provide the full error log from the node where you are getting "no such file" error?

            Thanks.

            Show
            elenst Elena Stepanova added a comment - - edited Hi Tomas, Could you please provide the full error log from the node where you are getting "no such file" error? Thanks.
            Hide
            primetomas Tomas Gustavsson added a comment -

            Attaching two files. node0.txt is from the first nodein the cluster, i.e. the one started with gcomm://

            node1.txt is the second node that I start trying to connect to the first node, i.e. started with gcomm://192.168.1222.192

            Show
            primetomas Tomas Gustavsson added a comment - Attaching two files. node0.txt is from the first nodein the cluster, i.e. the one started with gcomm:// node1.txt is the second node that I start trying to connect to the first node, i.e. started with gcomm://192.168.1222.192
            Hide
            elenst Elena Stepanova added a comment -

            This is a bad error message. What in fact happens is that you don't have wsrep_sst_auth in your configuration (see http://www.codership.com/wiki/doku.php?id=mysql_options_0.8), so your wsrep_sst_mysqldump gets an empty user name, as we can see in the log:

            Try 1/3: 'wsrep_sst_mysqldump --user '' --password '' ...

            It is supposed to throw a nice message "USER cannot be nil", only it doesn't work. It needs to be fixed in the script. Meanwhile, if you want to use mysqldump, you can try to configure it and see where it gets you (there might be more wrong error messages on the way).

            Show
            elenst Elena Stepanova added a comment - This is a bad error message. What in fact happens is that you don't have wsrep_sst_auth in your configuration (see http://www.codership.com/wiki/doku.php?id=mysql_options_0.8 ), so your wsrep_sst_mysqldump gets an empty user name, as we can see in the log: Try 1/3: 'wsrep_sst_mysqldump --user '' --password '' ... It is supposed to throw a nice message "USER cannot be nil", only it doesn't work. It needs to be fixed in the script. Meanwhile, if you want to use mysqldump, you can try to configure it and see where it gets you (there might be more wrong error messages on the way).
            Hide
            elenst Elena Stepanova added a comment -

            Updated the description with examples of not working error messages.

            Show
            elenst Elena Stepanova added a comment - Updated the description with examples of not working error messages.
            Hide
            primetomas Tomas Gustavsson added a comment -

            Ok after fiddling a lot with grant's I managed to get mysqldump state transfer to work. The only setting needed was the wsrep_sst_auth as you said.

            No other problems encountered, except that it only says "operation not permitted" in the error instead of "host 'galera1' is not permissed to connect to this MariaDB", which was the real error message.

            Show
            primetomas Tomas Gustavsson added a comment - Ok after fiddling a lot with grant's I managed to get mysqldump state transfer to work. The only setting needed was the wsrep_sst_auth as you said. No other problems encountered, except that it only says "operation not permitted" in the error instead of "host 'galera1' is not permissed to connect to this MariaDB", which was the real error message.
            Hide
            elenst Elena Stepanova added a comment -

            The part about rsync_wan is extracted into a subtask, the main task stays with the bad error messages in mysqldump.

            Show
            elenst Elena Stepanova added a comment - The part about rsync_wan is extracted into a subtask, the main task stays with the bad error messages in mysqldump.
            Hide
            nirbhay_c Nirbhay Choubey added a comment -

            This issue has already been fixed :

            • cat scripts/wsrep_sst_mysqldump.sh
              ...
              if test -z "$WSREP_SST_OPT_USER"; then wsrep_log_error "USER cannot be nil"; exit $EINVAL; fi
              ...
            • Donor's output in case of no user used for mysqldump sst:
              ...
              WSREP_SST: [ERROR] USER cannot be nil (20131125 22:51:35.618)
            Show
            nirbhay_c Nirbhay Choubey added a comment - This issue has already been fixed : cat scripts/wsrep_sst_mysqldump.sh ... if test -z "$WSREP_SST_OPT_USER"; then wsrep_log_error "USER cannot be nil"; exit $EINVAL; fi ... Donor's output in case of no user used for mysqldump sst: ... WSREP_SST: [ERROR] USER cannot be nil (20131125 22:51:35.618)

              People

              • Assignee:
                seppo Seppo Jaakola
                Reporter:
                primetomas Tomas Gustavsson
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 15 minutes
                  15m