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

before upgrade to 2.3, all works well ,after upgrade maxscale to 2.3.7,some programing drivers can not work well

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.1, 2.3.5
    • 2.2.22, 2.3.8
    • Protocol
    • None

    Description

      mysql 5.7 client work ok as follows

      mysql 5.1 client not work well

      harbor 1.3 which write in go , report error as follows

      ####
      May 25 11:37:27 172.20.0.1 jobservice[785]: 2019-05-25T03:37:27Z [FATAL] [main.go:41]: failed to initialize database: register db Ping `default`, This server only supports the insecure old password authentication. If you still want to use it, please add 'allowOldPasswords=1' to your DSN. See also https://github.com/go-sql-driver/mysql/wiki/old_passwords
      May 25 11:37:27 172.20.0.1 jobservice[785]: [ORM]register db Ping `default`, This server only supports the insecure old password authentication. If you still want to use it, please add 'allowOldPasswords=1' to your DSN. See also https://github.com/go-sql-driver/mysql/wiki/old_passwords
      ####
      *

      php report as follows*

      Failed to issue SQL query: query = SET NAMES 'utf8' COLLATE 'utf8_unicode_ci', mysql_error = Bad handshake, mysql_errno = 1045.

      node report as follows

      MySQL server is requesting the old and insecure pre-4.1 auth mechanism.Upgrade the user password or use the

      {insecureAuth: true}

      option

      Other tools

      Attachments

        Activity

          People

            markus makela markus makela
            xqzt xqzt
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.