KB-2363 Record sync fails when ADS ports are unavailable

Appian Community — Tue, 09 Dec 2025 21:35:47 GMT

Current Revision posted to Appian Knowledge Base by Appian Community on 12/9/2025 9:35:47 PM

Symptoms

In a highly available (HA) environment, record syncs may fail with the following error in tomcat-stdOut.log:

YYYY-MM-DD HH:MM:SS,mmm [pool-23874-thread-2] ERROR com.appiancorp.record.data.write.BingeFinalizerWithRetries - Syncing via the binge client failed for unexpected reasons. Binge Id : #########;http://<IP>:5410
YYYY-MM-DD HH:MM:SS,mmm [RecordSyncScheduler_Worker-1] ERROR com.appiancorp.record.service.BulkLoadServiceImpl - Error fully syncing record type with UUID: <UUID>
com.appiancorp.suiteapi.common.exceptions.AppianException: Unable to sync due to a system failure. (APNX-1-4521-044)

Inside <APPIAN_HOME>/logs/data-server/binge-gateway.log, the following error is present:

{"level":"WARN","time":"YYYY-MM-DDTHH:MM:SS.mmmZ","logger":"binge-gateway","caller":"dist/distribute.go:84","msg":"Failure to send data to remote server","pid":18661,"hostname":"example-1","BingeID":#########,"ServerAddress":"example-2:5411","error":"send: dial tcp <IP>:5411: connect: no route to host"}
{"level":"ERROR","time":"YYYY-MM-DDTHH:MM:SS.mmmZ","logger":"binge-gateway","caller":"op/binger.go:181","msg":"Failed to execute load complete","pid":18661,"example-1","bingeID":#########,"error":"failed to distribute the data to the majority of nodes. Failed nodes: [example-2:5411 example-3:5411]","stacktrace":"github.com/appian/gateways/cmd/binge/internal/lib/op.binger.LoadComplete.func1\n\t/go/data-layer/src/github.com/appian/gateways/cmd/binge/internal/lib/op/binger.go:181"

The <APPIAN_HOME>/logs/data-server/client.log shows the following:

YYYY-MM-DDTHH:MM:SS.mmmZ WARN  [RecordSyncScheduler_Worker-1] com.appian.data.client.binge.impl.BingeClientImpl - Failed to verify Binge initialization on a Binge gateway. Binge id: #########. Address: <IP>:5410

Cause

The above messages indicate connectivity issues between the other nodes' Data Servers. This can result from not all of the ports required for the Appian Data Service being available, which results in connectivity issues to the binge component.

Action

Ensure all of the required ports needed for the Appian Data Service are opened as per the documentation.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: December 2025

[DRAFT SUPP-1815] KB-XXXX Record sync fails when ADS ports are unavailable

dan.endean — Mon, 24 Nov 2025 17:47:06 GMT

Revision 2 posted to Appian Knowledge Base by dan.endean on 11/24/2025 5:47:06 PM

Symptoms

In a highly available (HA) environment, record syncs may fail with the following error in tomcat-stdOut.log:

YYYY-MM-DD HH:MM:SS,mmm [pool-23874-thread-2] ERROR com.appiancorp.record.data.write.BingeFinalizerWithRetries - Syncing via the binge client failed for unexpected reasons. Binge Id : #########;http://<IP>:5410
YYYY-MM-DD HH:MM:SS,mmm [RecordSyncScheduler_Worker-1] ERROR com.appiancorp.record.service.BulkLoadServiceImpl - Error fully syncing record type with UUID: <UUID>
com.appiancorp.suiteapi.common.exceptions.AppianException: Unable to sync due to a system failure. (APNX-1-4521-044)

Inside <APPIAN_HOME>/logs/data-server/binge-gateway.log, the following error is present:

{"level":"WARN","time":"YYYY-MM-DDTHH:MM:SS.mmmZ","logger":"binge-gateway","caller":"dist/distribute.go:84","msg":"Failure to send data to remote server","pid":18661,"hostname":"example-1","BingeID":#########,"ServerAddress":"example-2:5411","error":"send: dial tcp <IP>:5411: connect: no route to host"}
{"level":"ERROR","time":"YYYY-MM-DDTHH:MM:SS.mmmZ","logger":"binge-gateway","caller":"op/binger.go:181","msg":"Failed to execute load complete","pid":18661,"example-1","bingeID":#########,"error":"failed to distribute the data to the majority of nodes. Failed nodes: [example-2:5411 example-3:5411]","stacktrace":"github.com/appian/gateways/cmd/binge/internal/lib/op.binger.LoadComplete.func1\n\t/go/data-layer/src/github.com/appian/gateways/cmd/binge/internal/lib/op/binger.go:181"

The <APPIAN_HOME>/logs/data-server/client.log shows the following:

YYYY-MM-DDTHH:MM:SS.mmmZ WARN  [RecordSyncScheduler_Worker-1] com.appian.data.client.binge.impl.BingeClientImpl - Failed to verify Binge initialization on a Binge gateway. Binge id: #########. Address: <IP>:5410

Cause

Action

Ensure all of the required ports needed for the Appian Data Service are opened as per the documentation.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: November 2025

[DRAFT SUPP-1815] KB-XXXX Record sync fails when ADS ports are unavailable

pauline.delacruz — Fri, 21 Nov 2025 21:33:20 GMT

Revision 1 posted to Appian Knowledge Base by pauline.delacruz on 11/21/2025 9:33:20 PM

Symptoms

In a highly available (HA) environment, record syncs may fail with the following error in tomcat-stdOut.log:

YYYY-MM-DD HH:MM:SS,mmm [pool-23874-thread-2] ERROR com.appiancorp.record.data.write.BingeFinalizerWithRetries - Syncing via the binge client failed for unexpected reasons. Binge Id : #########;http://<IP>:5410
YYYY-MM-DD HH:MM:SS,mmm [RecordSyncScheduler_Worker-1] ERROR com.appiancorp.record.service.BulkLoadServiceImpl - Error fully syncing record type with UUID: <UUID>
com.appiancorp.suiteapi.common.exceptions.AppianException: Unable to sync due to a system failure. (APNX-1-4521-044)

Inside <APPIAN_HOME>/logs/data-server/binge-gateway.log, the following error is present:

{"level":"WARN","time":"YYYY-MM-DDTHH:MM:SS.mmmZ","logger":"binge-gateway","caller":"dist/distribute.go:84","msg":"Failure to send data to remote server","pid":18661,"hostname":"example-1","BingeID":#########,"ServerAddress":"example-2:5411","error":"send: dial tcp <IP>:5411: connect: no route to host"}
{"level":"ERROR","time":"YYYY-MM-DDTHH:MM:SS.mmmZ","logger":"binge-gateway","caller":"op/binger.go:181","msg":"Failed to execute load complete","pid":18661,"example-1","bingeID":#########,"error":"failed to distribute the data to the majority of nodes. Failed nodes: [example-2:5411 example-3:5411]","stacktrace":"github.com/appian/gateways/cmd/binge/internal/lib/op.binger.LoadComplete.func1\n\t/go/data-layer/src/github.com/appian/gateways/cmd/binge/internal/lib/op/binger.go:181"

The <APPIAN_HOME>/logs/data-server/client.log shows the following:

YYYY-MM-DDTHH:MM:SS.mmmZ WARN  [RecordSyncScheduler_Worker-1] com.appian.data.client.binge.impl.BingeClientImpl - Failed to verify Binge initialization on a Binge gateway. Binge id: #########. Address: <IP>:5410

Cause

The above messages indicate connectivity issues between the other nodes' Data Servers. This results from not all of the ports required for the Appian Data Service being available, which results in connectivity issues to the binge component.

Action

Ensure all of the required ports needed for the Appian Data Service are opened as per the documentation.

Affected Versions

This article applies to all self-managed versions of Appian.

Last Reviewed: November 2025