<?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 Re: Reload realtimeoutput.conf without restarting Splunkd in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168063#M98198</link>
    <description>&lt;P&gt;I feel like I'm closer now&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -k -u admin &lt;A href="https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/%252Fopt%252Fsplunk%252Fetc%252Fapps%252FSplunkRealTimeOutput%252Fbin%252Fscripted_inputs%252Frtoutput.py%20917074b6-865f-4c08-9f53-1aa9b5c6d33f/_reload" target="test_blank"&gt;https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/%252Fopt%252Fsplunk%252Fetc%252Fapps%252FSplunkRealTimeOutput%252Fbin%252Fscripted_inputs%252Frtoutput.py%20917074b6-865f-4c08-9f53-1aa9b5c6d33f/_reload&lt;/A&gt; -d ''

Enter host password for user 'admin':

&lt;RESPONSE&gt;
  &lt;MESSAGES&gt;
    &lt;MSG type="ERROR"&gt;In handler 'script': Invalid custom action for this internal handler (handler: script, custom action: _reload, eai action: edit).&lt;/MSG&gt;
&lt;/MESSAGES&gt;&lt;/RESPONSE&gt;&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Not sure what I am missing&lt;/P&gt;</description>
    <pubDate>Mon, 19 May 2014 14:21:49 GMT</pubDate>
    <dc:creator>areber04</dc:creator>
    <dc:date>2014-05-19T14:21:49Z</dc:date>
    <item>
      <title>Reload realtimeoutput.conf without restarting Splunkd</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168061#M98196</link>
      <description>&lt;P&gt;Is it possible to restart the RTO app without restarting Splunkd?  We have the RTO app installed on each of our indexers to spread out the load, but bringing down Splunk for 5 minutes while it restarts just to update the output is impacting our users.  I have tried using the REST API (servername:8089/services/apps/local/SplunkRealTimeOutput/_reload) but I receive a message on the indexer stating that "realtimeoutput" and "web" require a restart for the changes to take effect.  I have also tried using the "enable" and "disable" REST calls, but the result is the same.&lt;/P&gt;

&lt;P&gt;Is it possible to reload these configurations without restarting the entire indexer?&lt;/P&gt;</description>
      <pubDate>Fri, 16 May 2014 15:56:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168061#M98196</guid>
      <dc:creator>areber04</dc:creator>
      <dc:date>2014-05-16T15:56:02Z</dc:date>
    </item>
    <item>
      <title>Re: Reload realtimeoutput.conf without restarting Splunkd</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168062#M98197</link>
      <description>&lt;P&gt;Real-time outputs are in part scripted inputs.  Since you are familiar with the REST API, you are ahead of the game.  Try POSTing to this endpoint:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; &lt;A href="https://af-yolo.sv.splunk.com:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/your\_realtime\_output\/_reload" target="test_blank"&gt;https://af-yolo.sv.splunk.com:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/your\_realtime\_output\/_reload&lt;/A&gt;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 16 May 2014 21:32:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168062#M98197</guid>
      <dc:creator>araitz</dc:creator>
      <dc:date>2014-05-16T21:32:50Z</dc:date>
    </item>
    <item>
      <title>Re: Reload realtimeoutput.conf without restarting Splunkd</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168063#M98198</link>
      <description>&lt;P&gt;I feel like I'm closer now&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -k -u admin &lt;A href="https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/%252Fopt%252Fsplunk%252Fetc%252Fapps%252FSplunkRealTimeOutput%252Fbin%252Fscripted_inputs%252Frtoutput.py%20917074b6-865f-4c08-9f53-1aa9b5c6d33f/_reload" target="test_blank"&gt;https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/%252Fopt%252Fsplunk%252Fetc%252Fapps%252FSplunkRealTimeOutput%252Fbin%252Fscripted_inputs%252Frtoutput.py%20917074b6-865f-4c08-9f53-1aa9b5c6d33f/_reload&lt;/A&gt; -d ''

Enter host password for user 'admin':

&lt;RESPONSE&gt;
  &lt;MESSAGES&gt;
    &lt;MSG type="ERROR"&gt;In handler 'script': Invalid custom action for this internal handler (handler: script, custom action: _reload, eai action: edit).&lt;/MSG&gt;
&lt;/MESSAGES&gt;&lt;/RESPONSE&gt;&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Not sure what I am missing&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2014 14:21:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168063#M98198</guid>
      <dc:creator>areber04</dc:creator>
      <dc:date>2014-05-19T14:21:49Z</dc:date>
    </item>
    <item>
      <title>Re: Reload realtimeoutput.conf without restarting Splunkd</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168064#M98199</link>
      <description>&lt;P&gt;Looks like there are actually two actions, both implemented at the collection layer:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; &lt;A href="https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/_reload" target="test_blank"&gt;https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/_reload&lt;/A&gt;

 &lt;A href="https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/restart" target="test_blank"&gt;https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/restart&lt;/A&gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;According to the docs, I think you want to POST to the restart endpoint.&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2014 18:21:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168064#M98199</guid>
      <dc:creator>araitz</dc:creator>
      <dc:date>2014-05-19T18:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: Reload realtimeoutput.conf without restarting Splunkd</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168065#M98200</link>
      <description>&lt;P&gt;To follow up on this:&lt;BR /&gt;
 &lt;A href="https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/_reload"&gt;https://localhost:8089/servicesNS/nobody/SplunkRealTimeOutput/data/inputs/script/_reload&lt;/A&gt; appears to be the right command.  The "restart" command produces an error: &lt;MSG type="ERROR"&gt;In handler 'script': The following required arguments are missing: script.&lt;/MSG&gt;&lt;/P&gt;

&lt;P&gt;We are continuing testing to figure out how to get the _reload command to function consistently, but initial results show it working about 75% of the time.  There have been several cases where only 3 or 4 out of 6 of our RTO inputs actually reload on a given indexer.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jul 2014 20:18:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reload-realtimeoutput-conf-without-restarting-Splunkd/m-p/168065#M98200</guid>
      <dc:creator>areber04</dc:creator>
      <dc:date>2014-07-28T20:18:32Z</dc:date>
    </item>
  </channel>
</rss>

