KB Article #177137
Synchronization error with errors "Unable to send sync start event" and "no connected clients"
Problem
When performing manual synchronization of a cluster, it fails, and there appear errors in the Server Log similar to these:
Message: Cannot perform synchronization. Stack Trace: com.tumbleweed.st.server.cluster.manualsync.ManualSyncException: Unable to send Sync Start Event at com.tumbleweed.st.server.cluster.manualsync.ManualSyncExecutor.sendSyncStart(ManualSyncExecutor.java:254) at com.tumbleweed.st.server.cluster.manualsync.ManualSyncExecutor.performSync(ManualSyncExecutor.java:137) at com.tumbleweed.st.server.admin.configuration.ProcessClusterActionContext.synchronizeAll(ProcessClusterActionContext.java:112) ... Caused by: com.tumbleweed.st.server.events.AgentEventException: Event Error 7: Failed to send event AgentEvent [mAgentType=24, mAgentTrigger=64, mTarget=null, mEventData=(Enable debug to see), mExpectStream=true] on CommandChannel=null at com.axway.st.server.streaming.provider.StreamingProvider.processEvent(StreamingProvider.java:217) at com.tumbleweed.st.server.events.AbstractEvent.execute(AbstractEvent.java:319) at com.tumbleweed.st.server.events.SyncStartEvent.invoke(SyncStartEvent.java:31) at com.tumbleweed.st.server.events.SyncStartEvent.send(SyncStartEvent.java:27) at com.tumbleweed.st.server.cluster.manualsync.ManualSyncExecutor.sendSyncStart(ManualSyncExecutor.java:250) ... 43 more Caused by: com.tumbleweed.st.server.events.AgentEventException: Event Error 7: Unable to submit event AgentEvent [mAgentType=24, mAgentTrigger=64, mTarget=null, mEventData=(Enable debug to see), mExpectStream=true] on CommandChannel=null at com.axway.st.server.streaming.provider.StreamingProvider.sendEvent(StreamingProvider.java:241) at com.axway.st.server.streaming.provider.StreamingProvider.processEvent(StreamingProvider.java:215) ... 47 more Caused by: java.io.IOException: No connected clients at com.axway.st.server.streaming.client.StreamingClientImpl.connect(StreamingClientImpl.java:60) at com.axway.st.server.streaming.provider.StreamingProvider.makeChannel(StreamingProvider.java:159) at com.axway.st.server.streaming.provider.StreamingProvider.sendEvent(StreamingProvider.java:236) ... 48 more
Resolution
This occurs when the Administration streaming listener (by default, port 20444) is not up. Causes of this can include:
a misconfigured Private Network Zone. That Zone's address should be set to localhost
on each box in the cluster. Also, in that Zone, Admin needs to be enabled.
something else listening on that port
firewall issues (e.g. iptables
rules)