|
Folks,
When creating a monitor with the below command:
maxadmin alter monitor replication-cluster-monitor user=maxmon password=341EFE7FA99C09DB796C0C39E6620FA1 monitor_interval=1000 replication_user=mariadb replication_password=0A8C9D1F240571C0C7657E8AB482E05D failcount=5 auto_failover=true auto_rejoin=true
|
Why do we see the below error saying that it wasn't passed?
2018-07-28 21:27:54.299 error : (4) [mariadbmon] (startMonitor): Both 'replication_user' and 'replication_password' must be defined
|
The complete log for the alter monitor command:
2018-07-28 21:27:54.299 notice : (4) (runtime_alter_monitor): Updated monitor 'replication-cluster-monitor': user=maxmon
|
2018-07-28 21:27:54.299 notice : (4) (runtime_alter_monitor): Updated monitor 'replication-cluster-monitor': password=341EFE7FA99C09DB796C0C39E6620FA1
|
2018-07-28 21:27:54.299 notice : (4) (runtime_alter_monitor): Updated monitor 'replication-cluster-monitor': monitor_interval=1000
|
2018-07-28 21:27:54.299 error : (4) [mariadbmon] (startMonitor): Both 'replication_user' and 'replication_password' must be defined
|
2018-07-28 21:27:54.299 error : (4) (monitorStart): Failed to start monitor 'replication-cluster-monitor'.
|
2018-07-28 21:27:54.300 notice : (4) (runtime_alter_monitor): Updated monitor 'replication-cluster-monitor': replication_user=mariadb
|
2018-07-28 21:27:54.300 notice : (4) (secrets_readKeys): Using encrypted passwords. Encryption key: '/var/lib/maxscale/.secrets'.
|
2018-07-28 21:27:54.300 notice : (4) (runtime_alter_monitor): Updated monitor 'replication-cluster-monitor': replication_password=0A8C9D1F240571C0C7657E8AB482E05D
|
Is it something to check on the runtime_alter_monitor() method/function? Even if I don't set the replication_user and the replication_password, is it not true that the monitor user will be used for the failover/switchover/rejoin? Not sure why this is complaining.
Thanks, folks!
|