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

MariaDBMon yet adding mysqlbackend as the protocol instead of mariadbbackend

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.1
    • 2.2.2
    • mariadbmon
    • None
    • CentOS 7.2

    Description

      Folks,

      After configuring Maxscale 2.2.1 to run with MariaDBMon with the below commands:

      #: creating a new monitor
      maxadmin create monitor cluster-monitor mariadbmon
       
      #: alter the monitor to add user and passwd for the user accessing the backends
      maxadmin alter monitor cluster-monitor user=maxmon password=143BBF6A44CA8A5A39B51E66FAFEE75F monitor_interval=1000 replication_user=mariadb replication_password=D45F400B660D992F8DE0EB7DC48BF773 failcount=5 auto_failover=true auto_rejoin=true
       
      #: restart the monitor we created
      maxadmin restart monitor cluster-monitor

      I'm seeing this log event in the logs:

      2018-01-16 11:27:57   info   : (8) [cli] MaxAdmin: create server "prod_mariadb01" "192.168.50.12" "3306"
      2018-01-16 11:27:57   warning: (8) Protocol module 'mysqlbackend' has been deprecated, use 'mariadbbackend' instead.
      2018-01-16 11:27:57   notice : (8) Loaded module mariadbbackend: V2.0.0 from /usr/lib64/maxscale/libmariadbbackend.so
      2018-01-16 11:27:57   notice : (8) Loaded module MySQLBackendAuth: V1.0.0 from /usr/lib64/maxscale/libmysqlbackendauth.so
      

      I think it should be reviewed soon, right?

      Thanks!

      Attachments

        Activity

          People

            Unassigned Unassigned
            wagnerbianchi Wagner Bianchi (Inactive)
            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.