<?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: ExecProcessor - Ignoring my new script in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/ExecProcessor-Ignoring-my-new-script/m-p/74383#M15199</link>
    <description>&lt;P&gt;Thanks, Ayn. It was the slashes. I think I added the script through the UI first, then edited it later and removed the wrong slashes when I changed the script location after I discovered that scripts have to be in certain directories.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Sep 2011 18:53:45 GMT</pubDate>
    <dc:creator>jordans</dc:creator>
    <dc:date>2011-09-13T18:53:45Z</dc:date>
    <item>
      <title>ExecProcessor - Ignoring my new script</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ExecProcessor-Ignoring-my-new-script/m-p/74381#M15197</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;ERROR ExecProcessor - Ignoring: "\\C:\Program Files\Splunk\etc\apps\test\bin\intodns.py"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This new scripted input I created isn't generating data, but it runs fine from the command line. The only error I can find in Splunk is the above. No other indication of why it is being ignored.&lt;/P&gt;

&lt;P&gt;I've tried using a wrapper .bat:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ERROR ExecProcessor - Ignoring: "\\C:\Program Files\Splunk\etc\apps\test\bin\intodns_wrapper.bat"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and moving the script to various locations. &lt;/P&gt;

&lt;P&gt;Can someone help with troubleshooting?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2011 16:11:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ExecProcessor-Ignoring-my-new-script/m-p/74381#M15197</guid>
      <dc:creator>jordans</dc:creator>
      <dc:date>2011-09-13T16:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: ExecProcessor - Ignoring my new script</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ExecProcessor-Ignoring-my-new-script/m-p/74382#M15198</link>
      <description>&lt;P&gt;Judging by the leading &lt;CODE&gt;\\&lt;/CODE&gt; in the error message it seems you are not entering the path to the script correctly. How are you referring to the script in inputs.conf?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2011 16:51:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ExecProcessor-Ignoring-my-new-script/m-p/74382#M15198</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2011-09-13T16:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: ExecProcessor - Ignoring my new script</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/ExecProcessor-Ignoring-my-new-script/m-p/74383#M15199</link>
      <description>&lt;P&gt;Thanks, Ayn. It was the slashes. I think I added the script through the UI first, then edited it later and removed the wrong slashes when I changed the script location after I discovered that scripts have to be in certain directories.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2011 18:53:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/ExecProcessor-Ignoring-my-new-script/m-p/74383#M15199</guid>
      <dc:creator>jordans</dc:creator>
      <dc:date>2011-09-13T18:53:45Z</dc:date>
    </item>
  </channel>
</rss>

