Cluster Troubleshooting

If your Seq Disaster Recovery (DR) Instance is is failing to sync, check out the frequently-encountered errors below. Feel free to contact the Seq support team for another set of eyes on it!

The node failed at the follower with: the replication can't be completed because the leader is part of a different group

This generally indicates that the follower instance was started/initialized before joining the cluster; the error is caused by a safety mechanism intended to prevent deletion of existing data by mistake.

You can resolve this by stopping the follower node, and deleting its Stream/ subfolder under the Seq storage root (the default location will be C:\ProgramData\Seq on Windows, or the /data volume mount under Docker) before starting it back up.

Initial sync timing out

If you're configuring disaster recovery on an existing Seq instance with a lot of data you may find the follower fails to get itself initially synced before timing out.

If this happens, reach out to the Seq support team and we'll help you get started.

UI/API requests succeed, but the follower node does not appear in the Cluster screen

Check in this case that the --peer-cluster URL is correct. The URL scheme should be ws:// or wss://. The hostname in the URL must be one that the follower machine can resolve. The port in this URL will be different from the one being used to serve the Seq UI/API.

Node shows in the Cluster screen, but UI/API requests through the load balancer fail intermittently

When this problem occurs, some requests will succeed, and others fail with a message like The target server could not be contacted..

Check in this case that the --peer-internal-api URL is correct. The URL scheme should be http:// or https://. The hostname in the URL must be one that the follower machine can resolve. The port in this URL must be one that the Seq UI/API are being served on.