Restored Alfresco fails startup, tries to connect to old instance

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

ArtW

I did a backup of the content store and the database from our install in a docker setup.   When I try to restore to a different location, the service does not start:

com.hazelcast.spi.exception.RetryableIOException: Packet not sent to -> [172.18.0.4]:5701 over null

172.18.0.4 is the internal ip in the original docker setup.   The new restored location will never have access to that IP.  Where can I clear this link?  I cannot find where to tell the system to stop looking for other clusters, there is only one.   This error prevents Alfresco from starting.   If I start with an empty database and content store, this issue does not occur.

Using 7.2.0 container image using our enterprise license.  I will upgrade once I get it working.

victovrcel09

To resolve the issue, you need to update the cluster configuration in Alfresco to reflect the new IP address of the restored location. Look for the cluster configuration file or settings within Alfresco and update the IP address to match the new environment. By ensuring that the cluster configuration matches the new setup, you should be able to start Alfresco without encountering the "Packet not sent" error. PaybyPlateMa Invoice