![]() ![]() which is all well and fine, because that's where the Java executables live, right? Except in the jmx.py file, it was calling for $JAVA_HOME/bin When it had been set, it had been set to /usr/java/jrel1.8.0_161/bin The problem was.we had our JAVA_HOME set to the wrong directory. Plus, we had our JAVA_HOME environment variable set. ![]() Not a wrong version, because like I said, we were running a recent version of Java 8. So the problem, as per almost any one of these SPLUNK4JMX issues seems to point at, was Java. but durned if I can figure out where to put it. So does anyone have any suggestions about how to fix the prod box? I read on the APP page that you had to apply for a license, which I did, and I received same. Unable to initialize modular input "jmx" defined inside the app "SPLUNK4JMX": Introspecting scheme=jmx: script running failed (exited with code 1).įile "/data/splunk/etc/apps/SPLUNK4JMX/bin/jmx.py", line 154, in įile "/data/splunk/etc/apps/SPLUNK4JMX/bin/jmx.py", line 58, in do_run :-1:-1: Premature end of file.ĮRROR Error executing modular input : HTTP 401 - Īt (HttpException.java:84)Īt (HttpService.java:399)Īt (Service.java:1268)Īt (HttpService.java:151)Īt (Entity.java:381)Īt (Entity.java:1)Īt (Resource.java:174)Īt (Entity.java:462)Īt (Entity.java:157)Īt (Entity.java:279)Īt (ServiceInfo.java:155)Īt .runStateCheckerThread(Unknown Source)Īt .init(Unknown Source)Īt .JMXModularInput.main(Unknown Source)īut on my Prod box-the non-working one- I got the same thing as the -scheme errors above: Introspecting scheme=jmx: script running failed (exited with code 1). On my Dev box (the one which works) I got this output: License should have extension of '.lic' or '.license', ignoring file 5 GB license $SPLUNK_HOME/bin/splunk cmd splunkd print-modinput-config jmx | $SPLUNK_HOME/bin/splunk cmd $SPLUNK_HOME/bin/python $SPLUNK_HOME/etc/apps/SPLUNK4JMX/bin/jmx.py In an effort to troubleshoot further, I used another command, provided by what seemed to be the most knowledgeable yet: Monitor Java Virtual Machines via their exposed JMX MBean attributes, operations and notificationsīut on my Prod box.which is missing the Data Input method.I get this: Traceback (most recent call last):įile "/data/splunk/etc/apps/SPLUNK4JMX/bin/jmx.py", line 146, in įile "/data/splunk/etc/apps/SPLUNK4JMX/bin/jmx.py", line 61, in do_schemeįile "/data/splunk/etc/apps/SPLUNK4JMX/bin/jmx.py", line 124, in run_javaįile "/data/splunk/lib/python2.7/subprocess.py", line 390, in _init_įile "/data/splunk/lib/python2.7/subprocess.py", line 1024, in _execute_child $SPLUNK_HOME/bin/splunk cmd $SPLUNK_HOME/bin/python $SPLUNK_HOME/etc/apps/SPLUNK4JMX/bin/jmx.py -scheme Someone provided a check for the -scheme file: Someone suggested checking to make sure you weren't running multiple versions (or too new a version) of python. Check.Īnother suggested checking to make sure your Java could be called successfully. One particularly useful method suggested ensuring that your $SPLUNK_HOME and $JAVA_HOME environment variables were set correctly. ![]() ![]() I've spent the past 4 hours digging around in Splunk Answers trying to troubleshoot. Instead, under the Data Inputs, the JMX (Java Management Extensions) input method is missing. I had already gotten this app to work on my Splunk Dev box, and I anticipated simply copying the configs, changing the Index names, and off I would go. I have installed the SPLUNK4JMX app on my Prod box. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |