<?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: retrying a scripted input after a failure in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/retrying-a-scripted-input-after-a-failure/m-p/9850#M202</link>
    <description>&lt;P&gt;The interval need to be set to 1 not -1 for auto-retry on exit.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Feb 2010 05:10:18 GMT</pubDate>
    <dc:creator>Will_Hayes</dc:creator>
    <dc:date>2010-02-23T05:10:18Z</dc:date>
    <item>
      <title>retrying a scripted input after a failure</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/retrying-a-scripted-input-after-a-failure/m-p/9849#M201</link>
      <description>&lt;P&gt;&lt;EM&gt;[I heard this question on an internal mailing list, but it seemed generally relevant so asking it here too]&lt;/EM&gt;&lt;/P&gt;

&lt;P&gt;I have a scripted input that talks to an SDEE interface on the Cisco IPS. This interface can be flakey at times and I am running into an issue where if a connection fails Splunk will no longer retry the script. I assumed with the scheduler set -1 it would just try to reconnect after the script exits. I am catching the exception and exiting gracefully but that doesn't seem to work or I am just doing it wrong. Can anyone give me a pointer as to what I need my script to do in order to get Splunk to retry it if the first connection fails.?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2010 04:47:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/retrying-a-scripted-input-after-a-failure/m-p/9849#M201</guid>
      <dc:creator>Justin_Grant</dc:creator>
      <dc:date>2010-02-23T04:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: retrying a scripted input after a failure</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/retrying-a-scripted-input-after-a-failure/m-p/9850#M202</link>
      <description>&lt;P&gt;The interval need to be set to 1 not -1 for auto-retry on exit.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2010 05:10:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/retrying-a-scripted-input-after-a-failure/m-p/9850#M202</guid>
      <dc:creator>Will_Hayes</dc:creator>
      <dc:date>2010-02-23T05:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: retrying a scripted input after a failure</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/retrying-a-scripted-input-after-a-failure/m-p/9851#M203</link>
      <description>&lt;P&gt;If you set the interval to -1, it runs the script just once, when Splunk starts up. If you set it to 1, it runs the script again 1 second after the previous invocation exits. It's generally true for all scripted inputs that the next instance runs &lt;CODE&gt;interval&lt;/CODE&gt; seconds after the exit of the previous invocation.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2010 06:30:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/retrying-a-scripted-input-after-a-failure/m-p/9851#M203</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-02-23T06:30:08Z</dc:date>
    </item>
  </channel>
</rss>

