topic ArtifactReplicator - Connection failed in Deployment Architecture

ArtifactReplicator - Connection failed

btshivanand — Thu, 18 Jun 2020 11:35:30 GMT

I see below error message in my search head cluster . Can some one please assist on this?

06-18-2020 12:28:05.026 +0100 WARN ArtifactReplicator - Replication connection to ip=XXXX:8999 timed out
06-18-2020 12:28:05.026 +0100 WARN ArtifactReplicator - Connection failed
06-18-2020 12:28:05.026 +0100 WARN ArtifactReplicator - event=artifactReplicationFailed type=ReplicationFiles files="/opt/splunk/var/run/splunk/dispatch/_splunktemps/send/s2s/scheduler_c3ZjX3N1bW1hcmlzZXI_ZWVfc2VhcmNoX2V4cG9zdXJlbGF5ZXI__RMD5ac8aa10718becb19_at_1592479620_2301_644D578C-F001-4711-B459-2338E22DF399-638683B3-25D9-4D2A-AF2E-4E43362FDBFA.tar" guid=638683B3-25D9-4D2A-AF2E-4E43362FDBFA host=XXXX s2sport=8999 aid=4733. Connection failed

Re: ArtifactReplicator - Connection failed

richgalloway — Thu, 18 Jun 2020 12:20:13 GMT

Verify there is network connectivity between the reporting system and IP address in the first message. It's likely just a transient network error.

Re: ArtifactReplicator - Connection failed

btshivanand — Thu, 18 Jun 2020 12:39:52 GMT

Ping is success.I am not seeing any connectivity issue.

Re: ArtifactReplicator - Connection failed

richgalloway — Thu, 18 Jun 2020 13:25:47 GMT

Ping is a poor measure of connectivity because it doesn't consider the destination port. Use telnet, curl, traceroute, ncat, or some other tool that can make a connection to port 8999.

Re: ArtifactReplicator - Connection failed

btshivanand — Fri, 19 Jun 2020 09:44:41 GMT

We had connectivity hick up between the vms.So Vms rebooted .issue have been resolved Thanks