<?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: why isn't the inputs.conf script running? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185226#M37101</link>
    <description>&lt;P&gt;thanks, I missed that, was referencing this doc for setup: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/Data/Setupcustominputs"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/Data/Setupcustominputs&lt;/A&gt; - this doesn't have any mention of directory requirements.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Dec 2013 14:02:26 GMT</pubDate>
    <dc:creator>brettcave</dc:creator>
    <dc:date>2013-12-19T14:02:26Z</dc:date>
    <item>
      <title>why isn't the inputs.conf script running?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185223#M37098</link>
      <description>&lt;P&gt;Hi, I have just tried adding my first scripted input to splunk (a forwarder), but I am not getting the output in my splunk index.&lt;/P&gt;

&lt;P&gt;The script (/var/lib/someapp/process.sh):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;#!/bin/sh
TIMESTAMP=`date "+%Y-%m-%d %T"`
CPU=`ps aux | grep someproc | grep -v grep | aws '{print $3 }'`
PROCS=`ps ax | grep someproc | grep -v grep | wc -l`
echo -e "$TIMESTAMP\tCPU=$CPU\tNumProcs=$PROCS"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The script is executable for all users (I can run the script as the splunk user and get the expected output). Here's inputs.conf (in $SPLUNK_HOME/etc/system/local/):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[script:///var/lib/someapp/process.sh]
disabled = 0
interval = 60
index = someIndex
sourcetype = txt
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;My understanding is that the script should then be executed every 60 seconds? When monitoring the splunkd.log, I don't see the script being run (however I see scripts from another installed app running). Also, I'm not getting anything in my search (running an RT search to monitor results).&lt;/P&gt;

&lt;P&gt;Am I doing something wrong here?&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2013 13:32:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185223#M37098</guid>
      <dc:creator>brettcave</dc:creator>
      <dc:date>2013-12-19T13:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: why isn't the inputs.conf script running?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185224#M37099</link>
      <description>&lt;P&gt;I moved the script to /opt/splunkforwarder/etc/system/bin and added the 'source' parameter to the input, and it started working.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2013 13:39:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185224#M37099</guid>
      <dc:creator>brettcave</dc:creator>
      <dc:date>2013-12-19T13:39:06Z</dc:date>
    </item>
    <item>
      <title>Re: why isn't the inputs.conf script running?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185225#M37100</link>
      <description>&lt;P&gt;You need to put the script into a /app/bin/ folder, is a requirement. Splunk will only execute scripts from bin folders. From docs:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; * The &amp;lt;cmd&amp;gt; must reside in one of 
 *  $SPLUNK_HOME/etc/system/bin/
 *  $SPLUNK_HOME/etc/apps/$YOUR_APP/bin/
 *   $SPLUNK_HOME/bin/scripts/
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Link:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/admin/inputsconf" target="test_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/admin/inputsconf&lt;/A&gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2013 13:57:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185225#M37100</guid>
      <dc:creator>gfuente</dc:creator>
      <dc:date>2013-12-19T13:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: why isn't the inputs.conf script running?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185226#M37101</link>
      <description>&lt;P&gt;thanks, I missed that, was referencing this doc for setup: &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/Data/Setupcustominputs"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/Data/Setupcustominputs&lt;/A&gt; - this doesn't have any mention of directory requirements.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2013 14:02:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/why-isn-t-the-inputs-conf-script-running/m-p/185226#M37101</guid>
      <dc:creator>brettcave</dc:creator>
      <dc:date>2013-12-19T14:02:26Z</dc:date>
    </item>
  </channel>
</rss>

