Stephane VAROQUI

Hi, Can you try to reproduce with last 2.0 build. If you can still reproduce with the last build than you can send me 2 extract of http://127.0.0.1:10001/debug/pprof/heap at different...

also issue with Auth is removed in 2.1 by using the https://server:10005/ witch is true secured JWT login

Re, I'm not able to reproduce yet event trying hard on centos . Can you send us the content of the file clusterstate.json under /var/lib/replication/cluster-name/ tx /svar

I’m testing a patch on 2.1 when ready would you like to test the 2.1 to see if that can be reproductible as well ! > Le 15 mai 2018...

Got some news ! I possibly found a cause about this issue ! If you get time to confirm hat using a non existing ip address instead of a hostname...

Hi, Can you check that you can connect with mysql client from the replication-manager host with the user password provided to replication-manager Could be that root@repman_host is not declared or...

> Le 22 juin 2018 à 16:15, dimon00 a écrit : > > I can connect properly with root from support01 and support02. > I tried to configure the same...

This is very unusual, Could it be that you get some config.toml overwriting the config you are using somewhere in file system

Humm .replication-manager.key tell the server that the password are encrypted and that they should be decrypted before using ! Hope it's not coming with the packages and it's something that...

There is something we should do for printing more verbosity on such feature ! so that it get less complicate to track it down