All Apps and Add-ons

How can I remove the error "Unable to initialize modular input "jmx" defined inside the app "SPLUNK4JMX"" received on our search heads?

michael_sleep
Communicator

Hey there, we're using Monitoring of Java Virtual Machines with JMX (SPLUNK4JMX) to capture JMX data from some of our applications. Right now we're getting the following error message from the SPLUNK4JMX deployment on our search heads:

Unable to initialize modular input "jmx" defined inside the app "SPLUNK4JMX": Introspecting scheme=jmx: script running failed (exited with code 1).

The solution to this error is to install the JDK and make sure the Java home path is set but I don't believe this should apply to the search heads because they will not be making any JMX calls (we have SPLUNK4JMX on a heavy forwarder with the JDK).

The app itself actually works perfectly well on the search heads and displays the JMX data without any problems. The only issue is that the error message keeps appearing. I've tried removing various files from the app, including the bin directory but it keeps trying to initialize the JMX modular input... I can't see where that information is coming from. Anyone know the solution to this?

1 Solution

lycollicott
Motivator

Delete etc\apps\SPLUNK4JMX\README\inputs.conf.spec and restart Splunk.

*.conf.spec files define the modular inputs.

View solution in original post

lycollicott
Motivator

Delete etc\apps\SPLUNK4JMX\README\inputs.conf.spec and restart Splunk.

*.conf.spec files define the modular inputs.

michael_sleep
Communicator

Enjoy your karma.

Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...