Deployment Architecture

How to verify deployment client configuration

beaunewcomb
Communicator

On Windows 8-based Splunk Forwarder-

C:\Program Files\SplunkUniversalForwarder\etc\system\local\deploymentclient.conf

[deployment-client]
disabled = false

[target-broker:deploymentServer]
targetUri = 192.168.0.100:8089

On Linux-based deployment server-

/opt/splunk/etc/system/local/serverclass.conf

[global]

[serverClass:testClass]
whitelist.0 = *
restartSplunkd = true

[serverClass:testClass:app:testapp]

I restart splunk and reload deployment configuration (./splunk reload deploy-server) but I still get:

No deployment clients have contacted this server.

I've verified that the win8 machine can connect to the deployment server on 8089, restarted both services, but nothing.

Is there a command I can run on the forwarder to verify the deployment server it's trying to connect to?

Tags (1)
0 Karma

MarioM
Motivator

Here Troubleshoot deployment will give you infos on troubleshooting Splunk Deployment Server and Client

0 Karma
Get Updates on the Splunk Community!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

May 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...