Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3984

COM_CHANGE_USER from 'user' to 'user' succeeded on MaxScale yet failed on backends

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.2.1
    • Fix Version/s: 6.2.3
    • Component/s: Protocol
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-151

      Description

      After upgrading Maxscale from v2.5.18 to v6.2.1, I can see in maxscale.log this warnings:

      2022-02-02 09:54:42   warning: (65) [MariaDBProtocol] (WritableService); COM_CHANGE_USER from 'user' to 'user' succeeded on MaxScale yet failed on backends.
      2022-02-02 09:54:42   warning: (66) [MariaDBProtocol] (WritableService); COM_CHANGE_USER from 'user' to 'user' succeeded on MaxScale yet failed on backends.
      2022-02-02 09:54:44   warning: (71) [MariaDBProtocol] (WritableService); COM_CHANGE_USER from 'user' to 'user' succeeded on MaxScale yet failed on backends.
      

      We are primarily using PHP with the PDO_MYSQL driver to connect to the database. Users are generally configured statically and not changed on the fly.
      > Also, what connector you are using to connect with maxscale ?
      MariaDB-client-10.5.12_8-1.el8.x86_64

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            niljoshi Nilnandan Joshi
            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.