Deployment Architecture

How does the deployment server deploy to itself?

danielbb
Motivator

I have two DSs that fail to deploy the TA_nix to themselves, how is it normally done? meaning how does the deployment server deploy to itself?

Labels (1)
Tags (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

A Deployment Server cannot be a client of itself.  Any apps the DS needs should be installed manually.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

livehybrid
SplunkTrust
SplunkTrust

Hi @danielbb 

As @richgalloway said, you cant/shouldnt have the DS as a client to itself - You should deploy apps onto your DS under $SPLUNK_HOME/etc/apps in the same way you deploy to $SPLUNK_HOME/etc/deployment_apps

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

richgalloway
SplunkTrust
SplunkTrust

A Deployment Server cannot be a client of itself.  Any apps the DS needs should be installed manually.

---
If this reply helps you, Karma would be appreciated.

danielbb
Motivator

Why the DS shouldn't be a client of itself? any reasoning here?

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Being a client of oneself can have some strange results, especially if you deploy an app modifying DS behaviour (especially repo location). I suppose it could lead to a restart loop or some similar "funny" side effects. But even without it, you could accidentally push some general settings involuntarily modifying DS behaviour in an undesired way (even disabling it entirely).

livehybrid
SplunkTrust
SplunkTrust

Hi @danielbb 

The docs state : 

Important: The deployment server cannot be a deployment client of itself. If it is, the following error will appear in splunkd.log: "This DC shares a Splunk instance with its DS: unsupported configuration". This has the potential to lead to situations where the deployment clients lose their ability to contact the deployment server.

https://help.splunk.com/en/splunk-enterprise/administer/update-your-deployment/9.4/configure-the-dep...

🌟 Did this answer help you? If so, please consider:

  • Adding karma to show it was useful
  • Marking it as the solution if it resolved your issue
  • Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

richgalloway
SplunkTrust
SplunkTrust

It's an unsupported configuration.  It was explicitly prohibited at one time, but I can't find that documented now.

Note that it is possible for a DS to be a client of another DS.  This hierarchical structure has been used to manage multiple DSs when there are too many endpoints for a single DS to handle.

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...