Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Unable to initialize modular input "jmx" defined ...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unable to initialize modular input "jmx" defined inside the app "jmx_ta"
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,
01-11-2014 01:29:20.623 +0000 ERROR ModularInputs - Introspecting scheme=jmx: script running failed (exited with code 1).
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).
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 ?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've had a few issues with this on our setup similar to yours.
I'd suggest running ./splunk cmd <path to your python> <jmx script> --scheme (to show the introspection scheme as shown http://docs.splunk.com/Documentation/Splunk/6.0/AdvancedDev/ModInputsScripts#Define_a_scheme_for_int...)
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the quick response Damien.
Below are the paths set, we restarted the forwarder. We still get the same error no difference.
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"
declare -x PYTHONPATH="/home/ubuntu/downloads/Python-2.7.5"
What are we missing ?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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)
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On a Universal Forwarder(UF) ? If so , your UF will need a system python 2.7 installed and on the path.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
