<?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: Problem: scripted inputs stop running in certain time ? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69585#M14130</link>
    <description>&lt;P&gt;Thanks for your suggestion for logging. In fact, my problem is about time difference between the indexer and the machine that i used to view Splunk web. After i made a time balance between both of them, it seems to run well and the scipted input doesn't still get stuck. &lt;BR /&gt;
But i think Splunk should fairly deal with this issue in case of viewing web remotely.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Sep 2012 12:47:22 GMT</pubDate>
    <dc:creator>sieutruc</dc:creator>
    <dc:date>2012-09-25T12:47:22Z</dc:date>
    <item>
      <title>Problem: scripted inputs stop running in certain time ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69582#M14127</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have several scripted input written in python. At the beginning, it run well but after about 10 minutes, it stopped running, and in the splunkd.log i just see an error as below:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;09-25-2012 10:54:09.821 +0200 INFO  ExecProcessor - Ran script: "C:\Program Files\Splunk\etc\apps\Splunk_TA_windows\bin\memory.bat", took -3304.2 seconds to run, 617 bytes read
09-25-2012 10:54:47.977 +0200 WARN  DispatchCommand - Modtime 'Tue Sep 25 11:44:45 2012' for 'C:\Program Files\Splunk\var\run\splunk\dispatch\1348566284.10\status.csv' is 2998.0 seconds in the future; please check for clock skew
09-25-2012 11:58:56.175 +0200 INFO  WinEventLogChannel - getEvents: Unable to read Windows Event Logs 'System'; rec_id='0'; t_bytes_read='0'; bytes_needed='0'; buf_size='131071'; err_msg(38)='Reached the end of the file.';
09-25-2012 12:00:18.177 +0200 INFO  WinEventLogChannel - getEvents: Unable to read Windows Event Logs 'System'; rec_id='0'; t_bytes_read='0'; bytes_needed='0'; buf_size='131071'; err_msg(38)='Reached the end of the file.';
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I don't know why it likes that. It's strange that the error is not concerning about scripted input file . Any suggestion for solving that problem ?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 09:41:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69582#M14127</guid>
      <dc:creator>sieutruc</dc:creator>
      <dc:date>2012-09-25T09:41:34Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: scripted inputs stop running in certain time ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69583#M14128</link>
      <description>&lt;P&gt;I would suggest that nothing above relates to your script or is in fact a problem.&lt;/P&gt;

&lt;P&gt;Do a search for &lt;CODE&gt;index=_internal error *py*&lt;/CODE&gt; to see if you can locate any actual error.&lt;BR /&gt;
How does your script terminate?&lt;BR /&gt;
Also, do you have any logging inside your script? If not, I would suggest importing logging and generate your own logs to gain visibility to what your script is up to.&lt;/P&gt;

&lt;P&gt;P.S. The bits above are just talking about a batch file executing, monitor reaching the end of some event logs, a time issue on a CSV file..&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 11:13:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69583#M14128</guid>
      <dc:creator>Drainy</dc:creator>
      <dc:date>2012-09-25T11:13:31Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: scripted inputs stop running in certain time ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69584#M14129</link>
      <description>&lt;P&gt;To add some references to this...&lt;/P&gt;

&lt;P&gt;The following is the official docs on logging:&lt;BR /&gt;
&lt;A href="http://docs.python.org/howto/logging.html"&gt;http://docs.python.org/howto/logging.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;And this has various solutions in a cookbook format:&lt;BR /&gt;
&lt;A href="http://docs.python.org/howto/logging-cookbook.html"&gt;http://docs.python.org/howto/logging-cookbook.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 11:38:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69584#M14129</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2012-09-25T11:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: Problem: scripted inputs stop running in certain time ?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69585#M14130</link>
      <description>&lt;P&gt;Thanks for your suggestion for logging. In fact, my problem is about time difference between the indexer and the machine that i used to view Splunk web. After i made a time balance between both of them, it seems to run well and the scipted input doesn't still get stuck. &lt;BR /&gt;
But i think Splunk should fairly deal with this issue in case of viewing web remotely.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 12:47:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Problem-scripted-inputs-stop-running-in-certain-time/m-p/69585#M14130</guid>
      <dc:creator>sieutruc</dc:creator>
      <dc:date>2012-09-25T12:47:22Z</dc:date>
    </item>
  </channel>
</rss>

