Member since
04-19-2021
3
Posts
0
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1193 | 06-25-2021 12:36 AM |
06-26-2021
09:54 AM
Yes /etc/krb5.conf was the issue in the destination TST cluster. Specifically the [domain_realm] section did not have proper mapping for the replication source prod hosts and the prod realm. Since the PRD and TST hosts were all in the same domain so it was not easy to map the domain and realm using just the .proddomainxyz.com = PRODREALM . Instead we had to specify the individual source prod hosts in the destination TST /etc/krb5.conf file as below: [domain_realm] prodhostxx1 = PRODREALM prodhostxx2 = PRODREALM prodhostxx3 = PRODREALM etc. specify all the source prod hosts here If we don't specify the prodhosts like above replication doesn't know how to map the prodhosts to the PRODREALM and picks up the default TSTREALM which is why the original wrong realm error happened. Thanks!
... View more
06-25-2021
12:36 AM
Solved - increasing the number of connection on postgresql - editing postgresql.conf, incrising max_connections number and restart postgresql.
... View more