<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why is the deployment server not pushing updated inputs.conf configurations to forwarders automatically? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165928#M33658</link>
    <description>&lt;P&gt;I updated inputs.conf on an app in the deployment server yesterday. The update was done by logging into the server and editing the file. I checked the forwarders today and they didn't receive the updated inputs. I went to the GUI of deployment server and edited the server class; removed a server from the list and saved server class and that pushed the updated config to all forwarders. Is that an expected behavior?&lt;/P&gt;

&lt;P&gt;Doesn't the deployment server automatically send the updated config to its forwarders? or do we need to force it after a change?&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jun 2015 16:07:34 GMT</pubDate>
    <dc:creator>anoopambli</dc:creator>
    <dc:date>2015-06-17T16:07:34Z</dc:date>
    <item>
      <title>Why is the deployment server not pushing updated inputs.conf configurations to forwarders automatically?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165928#M33658</link>
      <description>&lt;P&gt;I updated inputs.conf on an app in the deployment server yesterday. The update was done by logging into the server and editing the file. I checked the forwarders today and they didn't receive the updated inputs. I went to the GUI of deployment server and edited the server class; removed a server from the list and saved server class and that pushed the updated config to all forwarders. Is that an expected behavior?&lt;/P&gt;

&lt;P&gt;Doesn't the deployment server automatically send the updated config to its forwarders? or do we need to force it after a change?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2015 16:07:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165928#M33658</guid>
      <dc:creator>anoopambli</dc:creator>
      <dc:date>2015-06-17T16:07:34Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the deployment server not pushing updated inputs.conf configurations to forwarders automatically?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165929#M33659</link>
      <description>&lt;P&gt;If you update a .conf file in a deployment app you need to run this CLI command to tell Splunk to send it to the deployment clients:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;./bin/splunk reload deploy-server
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;That will reload all serverclasses and send them any updates it finds. Optionally you can pass a severclass argument to only reload a specific serverclass, avoiding any unfinished changes being sent out to other serverclasses.&lt;/P&gt;

&lt;P&gt;Your change in the forwarder management UI implicitly triggered a reload of that serverclass, so it is indeed expected behaviour that Splunk sent the change then - but it's not the best way to trigger that reload at all.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2015 18:10:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165929#M33659</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2015-06-17T18:10:38Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the deployment server not pushing updated inputs.conf configurations to forwarders automatically?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165930#M33660</link>
      <description>&lt;P&gt;Thank you very much, that explains It well.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2015 18:13:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165930#M33660</guid>
      <dc:creator>anoopambli</dc:creator>
      <dc:date>2015-06-17T18:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the deployment server not pushing updated inputs.conf configurations to forwarders automatically?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165931#M33661</link>
      <description>&lt;P&gt;Martin, how do we pass serverclass argument to the command. I tried looking for it but didnt find any.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2015 19:35:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165931#M33661</guid>
      <dc:creator>anoopambli</dc:creator>
      <dc:date>2015-06-17T19:35:49Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the deployment server not pushing updated inputs.conf configurations to forwarders automatically?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165932#M33662</link>
      <description>&lt;P&gt;Run this command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;./bin/splunk help reload deploy-server
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You'll get this output:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Reload you deployment server, in entirety or by serverclass

Syntax:
    reload deploy-server [-class &amp;lt;serverclass_name&amp;gt;]

Objects:
    reload deploy-server                    Reload you deployment server, in entirety or by serverclass

Required Parameters:
    None

Optional Parameters:
    (For reload deploy-server)
            class                           serverclass to be reloaded.

Examples:
    ./splunk reload deploy-server
    ./splunk reload deploy-server -class my_serverclass
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 17 Jun 2015 20:01:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-is-the-deployment-server-not-pushing-updated-inputs-conf/m-p/165932#M33662</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2015-06-17T20:01:55Z</dc:date>
    </item>
  </channel>
</rss>

