<?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: Troubleshooting Scripted Inputs in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-Scripted-Inputs/m-p/38422#M7078</link>
    <description>&lt;P&gt;The error output of scripted inputs is indexed by Splunk in the `_internal` index.  You can search the errors with a similar search to the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="_internal" error myscript.sh
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You should see notices that look like `ERROR ExecProcessor`, followed by the script path/name.&lt;/P&gt;

&lt;P&gt;This data is also kept in `$SPLUNK_HOME/var/log/splunk/splunkd.log`.&lt;/P&gt;</description>
    <pubDate>Fri, 04 Feb 2011 04:06:46 GMT</pubDate>
    <dc:creator>Ron_Naken</dc:creator>
    <dc:date>2011-02-04T04:06:46Z</dc:date>
    <item>
      <title>Troubleshooting Scripted Inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-Scripted-Inputs/m-p/38421#M7077</link>
      <description>&lt;P&gt;Where can I find the error messages generated by scripted inputs?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Feb 2011 04:06:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-Scripted-Inputs/m-p/38421#M7077</guid>
      <dc:creator>qix</dc:creator>
      <dc:date>2011-02-04T04:06:18Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting Scripted Inputs</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-Scripted-Inputs/m-p/38422#M7078</link>
      <description>&lt;P&gt;The error output of scripted inputs is indexed by Splunk in the `_internal` index.  You can search the errors with a similar search to the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index="_internal" error myscript.sh
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You should see notices that look like `ERROR ExecProcessor`, followed by the script path/name.&lt;/P&gt;

&lt;P&gt;This data is also kept in `$SPLUNK_HOME/var/log/splunk/splunkd.log`.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Feb 2011 04:06:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-Scripted-Inputs/m-p/38422#M7078</guid>
      <dc:creator>Ron_Naken</dc:creator>
      <dc:date>2011-02-04T04:06:46Z</dc:date>
    </item>
  </channel>
</rss>

