<?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: Script input runs once, then never again in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Script-input-runs-once-then-never-again/m-p/66135#M13285</link>
    <description>&lt;P&gt;I tried many things, but in the end, changing the interval setting is all that was needed. I first tried 300, then 600, then 1200, and finally 1800. All worked without issue. Setting interval to 3600 causes the run-once-when-splunk-starts "feature."&lt;/P&gt;</description>
    <pubDate>Thu, 27 Sep 2012 16:12:46 GMT</pubDate>
    <dc:creator>twinspop</dc:creator>
    <dc:date>2012-09-27T16:12:46Z</dc:date>
    <item>
      <title>Script input runs once, then never again</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Script-input-runs-once-then-never-again/m-p/66133#M13283</link>
      <description>&lt;P&gt;Inputs entry is:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[script://./bin/db_lockout_query.rb]
disabled = 0
sourcetype = dbjobs
source = db_lockout_query.rb
interval = 3600
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When I restarted the Splunk forwarder, the input ran one time, and worked as expected. Splunkd.log shows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;09-18-2012 12:24:43.411 -0500 INFO  ExecProcessor - New scheduled exec process: /opt/splunkforwarder/etc/apps/db_queries/bin/db_lockout_query.rb
09-18-2012 12:24:43.411 -0500 INFO  ExecProcessor -     interval: 3600000 ms
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;09-18-2012 12:25:01.070 -0500 INFO  ExecProcessor - Ran script: /opt/splunkforwarder/etc/apps/db_queries
/bin/db_lockout_query.rb, took 15.16 seconds to run, 9722 bytes read
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But never refers to the lockout query script again. I just changed the inputs stanza to use cron instead to see if that helps.  &lt;/P&gt;

&lt;P&gt;In the meantime, any ideas?&lt;/P&gt;

&lt;P&gt;EDIT: Linux, 32-bit SUF, version 4.3.4&lt;/P&gt;</description>
      <pubDate>Thu, 20 Sep 2012 14:39:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Script-input-runs-once-then-never-again/m-p/66133#M13283</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2012-09-20T14:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: Script input runs once, then never again</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Script-input-runs-once-then-never-again/m-p/66134#M13284</link>
      <description>&lt;P&gt;Are you sure that the script is exiting properly?  If it is still running, Splunk won't run it again.&lt;/P&gt;

&lt;P&gt;Update:  Nevermind, from your output it appears that it is.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Sep 2012 14:58:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Script-input-runs-once-then-never-again/m-p/66134#M13284</guid>
      <dc:creator>mixolydian</dc:creator>
      <dc:date>2012-09-20T14:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: Script input runs once, then never again</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Script-input-runs-once-then-never-again/m-p/66135#M13285</link>
      <description>&lt;P&gt;I tried many things, but in the end, changing the interval setting is all that was needed. I first tried 300, then 600, then 1200, and finally 1800. All worked without issue. Setting interval to 3600 causes the run-once-when-splunk-starts "feature."&lt;/P&gt;</description>
      <pubDate>Thu, 27 Sep 2012 16:12:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Script-input-runs-once-then-never-again/m-p/66135#M13285</guid>
      <dc:creator>twinspop</dc:creator>
      <dc:date>2012-09-27T16:12:46Z</dc:date>
    </item>
  </channel>
</rss>

