Stephane VAROQUI

Can you try to reproduce on last 2.2 ...

Ok that's an issue for me so i'll look deeper into it thanks for reporting

Are you sure you have restarted the replication-manager, i can not reproduce , i found other type of issues like with reloading dump failed because of new warning "mysql: [Warning]...

intresting it would really help to get the full replication-managr.log as an attachement Now there are things that does not work as expected from the few logs you send us...

if fix the old master by manual and becoming slave. This is the role dedicated by repman to do this automatically if your plan is to do it yourself please...

Hi, saw you closed it did --autorejoin=false fixed the issue ?

Please i think you get a duplicate of https://github.com/signal18/replication-manager/issues/434 please install mysql-server as well on the replication-manager server as well and provide information where to found the mysql and mysqldump...

Hello are you using the config files generated by replication-manager is this an opensvc cluster ?

Most of the parameters that control memory do not work dynamically and propably need a restart of the databases once you have setup replicatio-manger to upload the config file via...

can you ls in /etc/mysql/conf.d on the database servers ? and confirm you have many files coming from replication-manager here ?