topic Re: Restored Alfresco fails startup, tries to connect to old instance in Alfresco Forum

Restored Alfresco fails startup, tries to connect to old instance

ArtW — Wed, 06 Sep 2023 15:54:26 GMT

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.

Re: Restored Alfresco fails startup, tries to connect to old instance

victovrcel09 — Wed, 20 Sep 2023 05:30:58 GMT

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

Re: Restored Alfresco fails startup, tries to connect to old instance

ArtW — Wed, 20 Sep 2023 12:26:10 GMT

Thank you.

I still am looking for exactly where to update it. I can not find where that configuration is stored. Also, if old setup has crashed hard and restoring from backups, no way to change the setting via UI before moving. It has to be in the database or file storage somewhere. I am running in Kubernetes and starting fresh pods, so not a file in the pod.

I was able to get something working by disabling clusters via adding the JAVA_OPS:

-Dalfresco.cluster.enabled=false

But I do not see where to clear old members of the cluster, or where that cluster configuration is. (other than via UI)