Deployment Architecture

Debugging app deployment to AWS cluster

dave_null
Path Finder

Hello,

 

I have an on-prem Splunk cluster and an AWS cluster. Each one has its own indexers and clustermaster, though only the on-prem setup has a search head and a deployment server. 

 

When I use the deployment server to deploy configurations to a splunk forwarder in AWS, it keeps failing to deploy. I have checked:

Forwarder is installed on machine to send logs

DS can contact the machine to send apps via port 8089

I used TCPDump on the forwarder machine on port 8089 and can see packets from the deployment server 

Unfortunately all I can get from the internal logs is this delightfully descriptive error message:


05-19-2021 08:04:42.818 +0200 WARN ClientSessionsManager - ip=<omitted> name=<omitted> Updating record for sc=<serverclass name> app=<app name>: action=Download result=Fail checksum=0

 

Can anyone suggest more areas to look at? I can't figure out why it is not deploying properly.

Labels (1)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...