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

Client shows `utf8mb3` csname replace warning message while logging into server

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.6
    • 10.6.4
    • Character Sets
    • None

    Description

      Client shows `utf8mb3` csname replace warning message while logging into server. These warnings seem related to MDEV-8334.

      10.6.2 193bfdd831bbbf65e74acd12baf691d4305e3c11

      $ /test/GAL_MD150621-mariadb-10.6.2-linux-x86_64-dbg/bin/mysql -A -uroot -S/test/GAL_MD150621-mariadb-10.6.2-linux-x86_64-dbg/node1/node1_socket.sock
      /test/GAL_MD150621-mariadb-10.6.2-linux-x86_64-dbg/bin/mysql: Warning: Charset id '33' csname 'utf8' trying to replace existing csname 'utf8mb3'
      /test/GAL_MD150621-mariadb-10.6.2-linux-x86_64-dbg/bin/mysql: Warning: Charset id '83' csname 'utf8' trying to replace existing csname 'utf8mb3'
      Welcome to the MariaDB monitor.  Commands end with ; or \g.
      Your MariaDB connection id is 14
      Server version: 10.6.2-MariaDB-debug MariaDB Server
       
      Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
       
      Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
       
      MariaDB [(none)]>
      

      Attachments

        Issue Links

          Activity

            ramesh Ramesh Sivaraman added a comment - - edited

            This issue is reproduced only on our VM QA box and the issue may be with the build environment. Closing this issue.

            ramesh Ramesh Sivaraman added a comment - - edited This issue is reproduced only on our VM QA box and the issue may be with the build environment. Closing this issue.

            I've encountered the same issue when connecting to MariaDB 10.6 with a 10.5 client.
            Updating the client to 10.6 solved the issue.

            hendriks73 Hendrik Schreiber added a comment - I've encountered the same issue when connecting to MariaDB 10.6 with a 10.5 client. Updating the client to 10.6 solved the issue.
            Roel Roel Van de Paar added a comment - - edited

            hendriks73 Thank you. I have reopened the issue. Do you have any idea what may have caused the issue? Also, what was the exact 10.5 version you were using? Also, did you use a binary package from our website or a Linux distro, or did you self-compile? Finally, what is your OS? Thank you!

            Roel Roel Van de Paar added a comment - - edited hendriks73 Thank you. I have reopened the issue. Do you have any idea what may have caused the issue? Also, what was the exact 10.5 version you were using? Also, did you use a binary package from our website or a Linux distro, or did you self-compile? Finally, what is your OS? Thank you!
            serg Sergei Golubchik added a comment - - edited

            likely the same as MDEV-26165

            serg Sergei Golubchik added a comment - - edited likely the same as MDEV-26165

            This was on CentOS Linux release 7.8.2003 (Core).
            The 10.5 version was (probably) 10.5.5-1.el7.centos
            The 10.6 version was 10.6.4-1.el7.centos
            Installation happened via yum.

            The problem was probably that the instructions (sorry, don't know which page anymore) only talked about mariadb-server, not about mariadb-client, which meant it wasn't updated.

            hendriks73 Hendrik Schreiber added a comment - This was on CentOS Linux release 7.8.2003 (Core). The 10.5 version was (probably) 10.5.5-1.el7.centos The 10.6 version was 10.6.4-1.el7.centos Installation happened via yum. The problem was probably that the instructions (sorry, don't know which page anymore) only talked about mariadb-server, not about mariadb-client, which meant it wasn't updated.

            People

              serg Sergei Golubchik
              ramesh Ramesh Sivaraman
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.