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

mysqlbinlog command does not work on new MariaDB 10.5.6 install

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.5.6
    • N/A
    • Scripts & Clients
    • None
    • Ubuntu 20 LTS

    Description

      The installed /etc/mysql/mariadb.conf.d/50-client.cnf file contains:
      [client]
      default-character-set = utf8mb4

      The mysqlbinlog client does not support the --default-character-set command line option, and thus it returns error:
      /usr/bin/mysqlbinlog: unknown variable 'default-character-set=utf8mb4'

      It is not possible to use mysqlbinlog without commenting out that option.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-22981 Bad "default-character-set" option in [client] option group 50-client.cnf on Debian/Ubuntu

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            greenlion Justin Swanhart added a comment -

            Also it exits with 0 instead of a non-zero error code and it doesn't prefix the output with ERROR: like other errors

            greenlion Justin Swanhart added a comment - Also it exits with 0 instead of a non-zero error code and it doesn't prefix the output with ERROR: like other errors
            serg Sergei Golubchik added a comment -

            This looks like MDEV-22981, that was fixed in 10.5.4.

            Could it be that your /etc/mysql/mariadb.conf.d/50-client.cnf came from before 10.5.4 and then you upgraded the server while the config file stayed old?

            serg Sergei Golubchik added a comment - This looks like MDEV-22981 , that was fixed in 10.5.4. Could it be that your /etc/mysql/mariadb.conf.d/50-client.cnf came from before 10.5.4 and then you upgraded the server while the config file stayed old?
            greenlion Justin Swanhart added a comment - - edited

            Oh. This is kind of weird. I spun up two EC2 machines, installed the repo in the same manner (using the script provided by mariadb) and used 'apt-get install mariadb-server' on both machines. One ended up with 10.5.6, but the other machine ended up with 10.3.22.

            I don't know why the older version ended up on the second machine, but that was the machine I was using mysqlbinlog on. So this is not a bug. Any idea why 10.3 would end up being installed from the repo on one machine when I followed the same steps on both?

            greenlion Justin Swanhart added a comment - - edited Oh. This is kind of weird. I spun up two EC2 machines, installed the repo in the same manner (using the script provided by mariadb) and used 'apt-get install mariadb-server' on both machines. One ended up with 10.5.6, but the other machine ended up with 10.3.22. I don't know why the older version ended up on the second machine, but that was the machine I was using mysqlbinlog on. So this is not a bug. Any idea why 10.3 would end up being installed from the repo on one machine when I followed the same steps on both?
            greenlion Justin Swanhart added a comment -

            You can close this. Sorry for the non-bug bug report.

            greenlion Justin Swanhart added a comment - You can close this. Sorry for the non-bug bug report.

            People

              Unassigned Unassigned
              greenlion Justin Swanhart
              Votes:
              1 Vote for this issue
              Watchers:
              4 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.