Forum Discussion
Sep 18, 2018
Ran into the same problem today when upgrading a cluster from 13.1.0.1 to 13.1.1 on the standby member. It turned out that the certificate key file that is stored in /config/filestore/files_d/Common_d/certificate_key_d was different than the one that was stored on the active member.
To solve the issue, I replaced the certificate key file on the standby member with the one from the active member. After that the configuration could be loaded successfully.