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

Could not manage the replication instance of binlog router

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 2.4.17
    • Fix Version/s: N/A
    • Component/s: binlogrouter
    • Labels:
      None
    • Environment:
      NAME="Ubuntu"
      VERSION="18.04.4 LTS (Bionic Beaver)"

      Description

      Several months ago, I use mariadb maxscale built a binlog router for backup mysql binlog. At the beginning, everything was good.
      Today I found one of the instance could not be logged in. The error said my password is incorrect.
      However, I use the same password that I record to login into the other replication instance, it login succussfully.
      (I only setted two replication instance, and both of them use the same use and password to connect the source mysql instance and manage themselves).
      I also use the same use and password to login into the source instances, it works good.
      After that, I check the master.ini config in datadir, the user and password also not changed.
      I think this may be a bug, please help!

      Here is my config.

      cat /etc/maxscale.cnf
       
      [maxscale]
      threads=auto
      logdir=/data/maxscale/logs
      datadir=/data/maxscale/data
      cachedir=/data/maxscale/cache
      execdir=/data/maxscale/exec
      persistdir=/data/maxscale/persist
       
      [Replication1]
      type=service
      router=binlogrouter
      user=repl
      password=57FFB3A814B198622160312A241D447DBD86459C5BCDA333CBA4BD4F86DEA7D9
      server_id=185301
      slave_hostname=172.16.0.18
      binlogdir=/data/maxscale/binlog/tencent_biz
      transaction_safety=1
      heartbeat=30
      send_slave_heartbeat=1
      semisync=0
      mariadb10-compatibility=0
       
      [Replication2]
      type=service
      router=binlogrouter
      user=repl
      password=57FFB3A814B198622160312A241D447DBD86459C5BCDA333CBA4BD4F86DEA7D9
      server_id=185302
      slave_hostname=172.16.0.18
      binlogdir=/data/maxscale/binlog/tencent_biz_divedb
      transaction_safety=1
      heartbeat=30
      send_slave_heartbeat=1
      semisync=0
      mariadb10-compatibility=0
       
      [Replication-Listener1]
      type=listener
      service=Replication1
      protocol=MySQLClient
      port=5301
       
      [Replication-Listener2]
      type=listener
      service=Replication2
      protocol=MySQLClient
      port=5302
       
      [MaxAdminService]
      type=service
      router=cli
       
      [MaxAdminUnixListener]
      type=listener
      service=MaxAdminService
      protocol=maxscaled
      socket=default
       
      [MaxAdminInetListener]
      type=listener
      service=MaxAdminService
      protocol=maxscaled
      address=localhost
      port=5400
      

      I try to log into Replication1, it works good.
      I try to log into Replication2, it works bad.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            michael-liumh Michael Liu
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.