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
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!

Agent Mode Engaged! Enchaining Agentic Operations with Splunk AI Assistant 2.0

    Are you ready to transform how your team handles complex data requests? We invite you to our upcoming ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...