Troubleshooting Tip: When existing connectors on a primary can't be synced to a secondary between HA

[bbae]

Description	This article describes what should be checked and done when existing connectors on a primary cannot be synced to a secondary between HA, and Active-Active after upgrading from v7.4.3 to v7.5.0.
Scope	FortiSOAR v7.5.0.
Solution	The existing connectors only on the Primary FortiSOAR, for certain reasons before the upgrade, are not synced to a secondary after the upgrade. New connectors, not the existing ones, can be synced when they are installed after the upgrade. Check the following log while trying to sync between both FortiSOARs: cat /var/log/cyops/cyops-auth/ha.log or tail -F /var/log/cyops/cyops-auth/ha.log An error message below might be seen: Error: Failed to execute command [du -sh --total -b /opt/cyops/configs/cyops-api/.Defuse.key /opt/cyops/configs/keys/PASSWORD_E ities/models/ /opt/cyops-archival/archival/entities/migrations/ /opt/cyops/configs/cyops-ui/locales/mmd /opt/cyops/confi opt/cyops/configs/integrations/connectors_development] with error b"du: cannot access '/opt/cyops/configs/keys/PASSWORD_ This message means that PASSWORD_ENCRYPTION_KEY didn't exist in Primary. Follow next and resolve this issue: Create the file on Primary FortiSOAR because the key file will be synced to Secondary after forming a cluster. touch /opt/cyops/configs/keys/PASSWORD_ENCRYPTION_KEY Change file mode bits appropriately: chmod 644 /opt/cyops/configs/keys/PASSWORD_ENCRYPTION_KEY Perform this during the maintenance window because one of the Postgres Group processes gets up and down while regenerating the key: python3 /opt/cyops/scripts/manage_passwords.py --generate-encryption-key Perform join cluster: csadm ha join-cluster --status active --role secondary