Srijstha

Hi tanji, Many thanks for your response. Actually, I tried the Replication Manager first from command line without script in MaxScale with the command: ` /usr/bin/replication-manager failover --user root:rootpass --rpluser...

I tried to use daemon mode using the command: `replication-manager --config=/etc/config.toml --config-group=Test_Maxscale --verbose` The config file contains [Test_Maxscale] group with parameters: ``` [Test_Maxscale] title = "TestMaxscale" hosts = "dbm,dbs-1,dbs-2" prefmaster...

The command doesn't seem to create any log file. I also tried with --logfile parameter, but without luck!

Here is the command and output: ``` $replication-manager monitor --config=/etc/config.toml --config-group=Test_Maxscale --daemon --log-level=3 2017/04/05 12:40:37 INFO : Using configuration group Test_Maxscale 2017/04/05 12:40:37 ERROR: Could not parse configuration group Test_Maxscale...

That's strange! I am also using version 1.0.2: ``` $ replication-manager version 2017/04/05 12:56:10 INFO : Using config file: /etc/replication-manager/config.toml Replication Manager 1.0.2 for MariaDB 10.x Series Full Version: 1.0.2-1-g8faf64d...

Ok I figured it out, it was the problem of wrong path to the config file! Many thanks for your help and prompt answers. I am still trying to make...

Great, thanks. I will first try with 1.1:)

Hi tanji, Some progress now:) I am getting the following error now: ``` INFO[2017-04-05T15:33:58+02:00] [Test_Maxscale] DEBUG: Entering topology detection INFO[2017-04-05T15:33:58+02:00] [Test_Maxscale] ERROR: Could not connect to MaxScale:Incorrect maxscale protocol negotiation...

@tanji, I did have the listener and used the port 6603 as well but without success. It gives an ERROR: Could not connect to MaxScale:Connection failed to address maxscale:6603 As...