Stephane VAROQUI

- a dump of the mysql.user table can help me to figure this out - the result of replication-manager-cli api --url="https://127.0.0.1:10005/api/clusters/pub/topology/servers" replication-manager-cli api --url="https://127.0.0.1:10005/api/clusters/pub/settings"

Nigel, also note that replication-manager-pro stand for provisioning and is used with opensvc for docker deployments is that what you would like to test ? If it is the case...

For other scenarios the -osc release is the one you should use !

Sorry the attachement as failed for some reason, may size or file format json unsupported can you send it to me [email protected] with a dump of the user table so...

yop so the user passed to the function is "mrm" not surprise here ! the dump of mysql.user can help to reproduce

There is sql error log plugin in MariaDB that do not exist yet in Percona to track isifreplication-manager send wrong SQL command, other than that you can activate database general...

Could it be that you did not grant but modify the underlying tables without flush privileges

It's because you are not using GTID or PSEUDO GTID and so the 10.1.1.172 stay under the old master until the 10.1.1.173 old master is restarted , without GTID they...

yes standalone or reattached to cluster if possible via rejoin method. The variable is --autorejoin-slave-positional-hearbeat

Hi i think i fixed this recently What is the release you are using ?