[MXS-1614] MariaDBMon yet adding mysqlbackend as the protocol instead of mariadbbackend Created: 2018-01-16  Updated: 2018-01-16  Resolved: 2018-01-16

Status: Closed
Project: MariaDB MaxScale
Component/s: mariadbmon
Affects Version/s: 2.2.1
Fix Version/s: 2.2.2

Type: Bug Priority: Major
Reporter: Wagner Bianchi (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

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!

 Comments   
Comment by markus makela [ 2018-01-16 ]

Fixed in a44e352f4f253c3822d179a48379d339f56eead3.

Comment by Johan Wikman [ 2018-01-16 ]

Already fixed in the forthcoming 2.2.2.

Generated at Thu Feb 08 04:08:07 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.