Deployment Architecture

deploymentserver.conf gets empty after restart

a_naoum
Path Finder

Hello,

I have a strange behavior while trying to setup an UF (7.2.3) as deployment client. When I do 'set deploy-poll xxx.com:8089' I'm getting that configuration updated so everything looks ok but actually it adds only the 'target-broker:deploymentServer' stanza, even from empty file.

If I do edit manual according to the documentation then after the restart the file goes empty.
There is no permissions (at least as it shows) issues since in the first case the UF rights on the file something.

Anyone has any idea what is going on?

0 Karma

a_naoum
Path Finder

never mind. I found that an strange app from another team was doing this to "protect" direct changes.

0 Karma

sbattista09
Contributor

if splunk set deploy-poll <IP_address/hostname>:<management_port> then running
splunk restart is not working... I would just edit the deploymentclient.conf file directly. Is this only happening on one host?

[deployment-client]

phoneHomeIntervalInSecs = 500
[target-broker:deploymentServer]
# Change the targetUri
targetUri = dep.server.com:8089
0 Karma
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk, and empower your SOC to reach new heights! Duration: 1 hour  Prepare to ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...