topic Re: Changing an existing Splunk Forwarder into a deployment client in Deployment Architecture

Changing an existing Splunk Forwarder into a deployment client

himynamesdave — Fri, 24 Mar 2017 19:30:52 GMT

I have an existing Splunk Forwarder currently forwarding data to an indexer.

I have a new deployment server I want to connect Splunk Forwarder to as deployment client.

Should I need to know anything before pointing Splunk Forwarder at deployment server? I cannot find any warnings in the docs. Will this interrupt current forwarding rules (and apps) currently installed on Forwarder?

Re: Changing an existing Splunk Forwarder into a deployment client

woodcock — Fri, 24 Mar 2017 19:46:56 GMT

There is no mention in any of the documentation about (warning against) the problems with losing file permissions (executable bit) if you use a Windows-hosted Deployment Server to push configurations to *Nix-based Deployment Clients. I just had another client bitten by this and the warning should definitely be in the docs, probably multiple places. See these:

https://answers.splunk.com/answers/70039/windows-deployment-server-to-nix-deployment-client-permission-issues.html
https://answers.splunk.com/answers/4460/application-scripts-not-executable-when-deployed-via-deployment-server.html
https://answers.splunk.com/answers/463274/deploy-unix-scripts-from-a-windows-deployment-serv.html

Bottom line: Best practice is to NEVER deploy DS on Windows (unless you are absolutely certain that you will never have any *Nix DCs). This is not mentioned anywhere.

To make your forwarder a Deployment Client is just to run this command:

/opt/splunkforwarder/bin/splunk set deploy-poll YourServerHere:8089 --accept-license --answer-yes --auto-ports --no-prompt -auth admin:changeme

Re: Changing an existing Splunk Forwarder into a deployment client

himynamesdave — Fri, 24 Mar 2017 19:51:18 GMT

Ah, good to know. Im running on Linux so should be OK to turn Forwarder into a Deployment Client then? I am worried about current inputs.conf / outputs.conf in search app /local directory being affected by change. So setting Forwarder as Deployment Client this won't be an issue? Thanks for your help!

Re: Changing an existing Splunk Forwarder into a deployment client

woodcock — Fri, 24 Mar 2017 20:19:15 GMT

In the beginning, nothing will happen when you connect your forwarder for the DS because you have not staged any apps in the $SPLUNK_HOME/etc/apps/deployment-apps/ directory on your DS so there is nothing to deploy. If you are concerned about Knowledge Objects in the search app, then be sure that you do not put a search app (directory) in the deployment-apps directory on your DS.

Re: Changing an existing Splunk Forwarder into a deployment client

himynamesdave — Fri, 24 Mar 2017 20:51:29 GMT

Thank you, sir!

Re: Changing an existing Splunk Forwarder into a deployment client

himynamesdave — Mon, 27 Mar 2017 20:53:17 GMT

To follow up on this, I recently switched our forwarders and encountered one issue: Splunk changed the host value for each forwarder to "ID" with all events, from all forwarders being indexed as host=ID

Re: Changing an existing Splunk Forwarder into a deployment client

woodcock — Tue, 28 Mar 2017 00:45:13 GMT

I saw that; that is BUG for SURE. I commented on that other Question, too. I have never seen that before.