Getting Data In

Why does excludeFromUpdate not work in serverclass.conf?

schose
Builder

Hi all,

I'm managing my apps deployed through forwarder management using git. When running a scheduled "git pull" the file, .git/FETCH_HEAD is always newly created.
When running a splunk reload deploy-server, the app is always sent out to the clients and Splunk will be restarted.

To avoid this, I'm trying to use the excludeFromUpdate introduced in Splunk v6.2 but neither

[serverClass:splunkdebug:app:myapp]
restartSplunkd = 1
stateOnClient = enabled
excludeFromUpdate=myapp/.git

nor

[default]
excludeFromUpdate=$app_root$/.git

seems to work.

Any hints?

Cheers,

Andreas

1 Solution

hexx
Splunk Employee
Splunk Employee

What version are your deployment clients running? This particular setting requires both the deployment server and its deployment clients to be running Splunk Enterprise 6.2 or higher.

View solution in original post

hexx
Splunk Employee
Splunk Employee

What version are your deployment clients running? This particular setting requires both the deployment server and its deployment clients to be running Splunk Enterprise 6.2 or higher.

schose
Builder

You're right. 🙂

0 Karma

hexx
Splunk Employee
Splunk Employee

Oh good, let me convert my comment to an answer then.

0 Karma

schose
Builder

As hexx answered correctly you also need a v6.2 or higer client.

Workaround for everyone having the same issue with the older clients using git: it's save enough to delete the .git//FETCH_HEAD everytime after git pull.

Regards,

Andreas

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...