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

Upgrading mariadb/galera cluster 10.4.12->10.4.13 causing any user authentication to fail

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 2.4.9
    • N/A
    • Authenticator
    • Debian Buster (db), Debian Stretch (maxscale)

    Description

      I am using a mariadb/galera cluster. PHP app is connected to db using maxscale from localhost. When upgrading mariadb from 10.4.12 to 10.4.13 user authentication started to fail.

      When starting maxscale, this is logged:

      2020-05-21 09:47:07   notice : [MariaDBAuth] [Read-Write-Service] Loaded 0 MySQL users for listener 'Read-Write-Listener' from server 'vsqdev-db1' with checksum 0xfd7d71d9.
      2020-05-21 09:47:07   notice : [MariaDBAuth] [Read-Write-Service] No users were loaded but 'inject_service_user' is enabled. Enabling service credentials for authentication until database users have been successfully loaded.
      
      

      All authentication request raises these logs:

      2020-05-21 09:59:18   warning: (3) [MariaDBAuth] Read-Write-Service: login attempt for user 'devvsq'@[127.0.0.1]:64892 to database 'mydb', authentication failed. User not found.
      2020-05-21 09:59:30   warning: (4) [Read-Write-Service] Refresh rate limit (once every 30 seconds) exceeded for load of users' table.
      2020-05-21 09:59:30   warning: (4) [MariaDBAuth] Read-Write-Service: login attempt for user 'devvsq'@[127.0.0.1]:64900 to database 'mydb', authentication failed. User not found.
      

      On DB side, these are logged:

      2020-05-20 12:13:29 82 [Warning] Aborted connection 82 to db: 'mydb' user: 'devvsq' host: 'myhost.com' (Got an error reading communication packets)
      2020-05-20 13:24:48 132 [Warning] Aborted connection 132 to db: 'mydb' user: 'devvsq' host: 'myhost.com' (Got timeout reading communication packets)
      

      It is important to note, that it had been a working system and mariadb upgrade caused it to fail. I tried many auth options in maxscale but have no idea what is a workaround. DB users are both available tied to "localhost" and "%" but this does not help.

      Interestingly, the only auth working is with maxscale ("vsqmaxscale") user, nothing else.

      my maxscale config:

      [maxscale]
      threads=auto
       
      [vsqdev-db1]
      type=server
      address=172.18.3.40
      port=3306
      protocol=MariaDBBackend
       
      [vsqdev-db2]
      type=server
      address=172.18.3.41
      port=3306
      protocol=MariaDBBackend
       
      [Read-Write-Service]
      type=service
      router=readwritesplit
      servers=vsqdev-db1,vsqdev-db2
      user=vsqmaxscale
      password=<snip>
       
      [Read-Write-Listener]
      type=listener
      service=Read-Write-Service
      protocol=MariaDBClient
      address=127.0.0.1
      port=3307
       
      [Galera-Monitor]
      type=monitor
      module=galeramon
      servers=vsqdev-db1,vsqdev-db2
      user=vsqmaxscale
      password=<snip>
      monitor_interval=10000
      use_priority=true
       
      [MaxAdmin-Service]
      type=service
      router=cli
       
      [MaxAdmin-Listener]
      type=listener
      service=MaxAdmin-Service
      protocol=maxscaled
      socket=default
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              akovacs Andras Kovacs
              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.