After installing conjur enterprise as a master with 2 standbys I tried to enable sync replication. The evoke output was that there must be a minimum of 2 standbys to support this config! I used the --force option and hoped it would be ok. After realising that my config had issues I restarted the 3 vms and now even though the containers are running, I can’t do a health check or load the UI. Am I able to use the containers without reconfiguring After a host restart? I guess I should …
What was the error on the config? You said it required two standby’s but you did have the two is that corect?
Thanks - Rob
Hi Rob, yes I had two standbys to satisfy the requirements for sync replication. I created the seed files and deployed the first standby, then recreated the seed files again referencing the 2nd standby and then deployed the 2nd standby. Not sure that this was correct. I did this because on the first attempt, I used the 1st set of seed files for both standbys. When I looked at the health report it looked like the first standby was replicating to the 2nd!.
This is when I killed the 2nd standby, created the 2nd set of seed files and reconfigured. When the sync failed to identify 2 standbys I restarted all containers and now ai can’t connect to any of them. The load balancers sees them all as down as well
I haven’t run this in while, but this is the standby config function in the script I use to stand up an HA cluster.