<?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: Unable to initialize modular input &amp;quot;jmx&amp;quot;  defined inside the app &amp;quot;jmx_ta&amp;quot; in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109922#M23085</link>
    <description>&lt;P&gt;Thanks for the quick response Damien.&lt;BR /&gt;
Below are the paths set, we restarted the forwarder. We still get the same error no difference.&lt;/P&gt;

&lt;P&gt;declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/ubuntu/downloads/Python-2.7.5:/home/ubuntu/downloads/Python-2.7.5"&lt;BR /&gt;
declare -x PYTHONPATH="/home/ubuntu/downloads/Python-2.7.5"&lt;/P&gt;

&lt;P&gt;What are we missing ?&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jan 2014 18:50:45 GMT</pubDate>
    <dc:creator>cparid</dc:creator>
    <dc:date>2014-01-13T18:50:45Z</dc:date>
    <item>
      <title>Unable to initialize modular input "jmx"  defined inside the app "jmx_ta"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109920#M23083</link>
      <description>&lt;P&gt;We were able to setup and run the jmx_ta on the splunk app(web app). It was able to connect and report JMX data from remote servers. But, we want to use that in a distributed system. For that we tried installing the same thing on the splunkForwarder installed on the application nodes. We did same configs as before, but it won't start up and just throw the below error,&lt;BR /&gt;
01-11-2014 01:29:20.623 +0000 ERROR ModularInputs - Introspecting scheme=jmx: script running failed (exited with code 1).&lt;BR /&gt;
01-11-2014 01:29:20.623 +0000 ERROR ModularInputs - Unable to initialize modular input "jmx"  defined inside the app "jmx_ta": Introspecting scheme=jmx: script running failed (exited with code 1).&lt;/P&gt;

&lt;P&gt;We checked JAVA_HOME and SPLUNK_HOME is set fine. Do we need Python set too ? Also is there a guide or specific steps for installing this on the forwarder ?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:38:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109920#M23083</guid>
      <dc:creator>cparid</dc:creator>
      <dc:date>2020-09-28T15:38:03Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to initialize modular input "jmx"  defined inside the app "jmx_ta"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109921#M23084</link>
      <description>&lt;P&gt;On a Universal Forwarder(UF) ? If so , your UF will need a system python 2.7 installed and on the path.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jan 2014 09:08:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109921#M23084</guid>
      <dc:creator>Damien_Dallimor</dc:creator>
      <dc:date>2014-01-11T09:08:21Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to initialize modular input "jmx"  defined inside the app "jmx_ta"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109922#M23085</link>
      <description>&lt;P&gt;Thanks for the quick response Damien.&lt;BR /&gt;
Below are the paths set, we restarted the forwarder. We still get the same error no difference.&lt;/P&gt;

&lt;P&gt;declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/ubuntu/downloads/Python-2.7.5:/home/ubuntu/downloads/Python-2.7.5"&lt;BR /&gt;
declare -x PYTHONPATH="/home/ubuntu/downloads/Python-2.7.5"&lt;/P&gt;

&lt;P&gt;What are we missing ?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2014 18:50:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109922#M23085</guid>
      <dc:creator>cparid</dc:creator>
      <dc:date>2014-01-13T18:50:45Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to initialize modular input "jmx"  defined inside the app "jmx_ta"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109923#M23086</link>
      <description>&lt;P&gt;I've had a few issues with this on our setup similar to yours.&lt;/P&gt;

&lt;P&gt;I'd suggest running &lt;CODE&gt;./splunk cmd &amp;lt;path to your python&amp;gt; &amp;lt;jmx script&amp;gt; --scheme&lt;/CODE&gt; (to show the introspection scheme as shown &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/AdvancedDev/ModInputsScripts#Define_a_scheme_for_introspection"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/AdvancedDev/ModInputsScripts#Define_a_scheme_for_introspection&lt;/A&gt;)&lt;/P&gt;

&lt;P&gt;That was they way I managed to find the issues with ours.  Also if deploying via a deployment server then it copies the app but leaves out one of the directories that is empty which caused us issues.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2014 11:37:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109923#M23086</guid>
      <dc:creator>samhughe</dc:creator>
      <dc:date>2014-01-14T11:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to initialize modular input "jmx"  defined inside the app "jmx_ta"</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109924#M23087</link>
      <description>&lt;P&gt;I had this exact error and I resolved it by removing Python v3.4 and using v2.7(which was listed as a prereq in the documentation)&lt;/P&gt;</description>
      <pubDate>Wed, 03 Dec 2014 17:08:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unable-to-initialize-modular-input-quot-jmx-quot-defined-inside/m-p/109924#M23087</guid>
      <dc:creator>chengka</dc:creator>
      <dc:date>2014-12-03T17:08:25Z</dc:date>
    </item>
  </channel>
</rss>

