Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- About nikduvall
nikduvall
Explorer
Member since:
10-05-2010
06-05-2020
Community Statistics
| Posts | 7 |
| Solutions | 1 |
| Karma Given | 0 |
| Karma Received | 0 |
| Member Since | 10-05-2010 |
Activity Feed
- Posted Re: Monitoring of Java Virtual Machines with JMX: How to clear the cache of input settings? on All Apps and Add-ons. 04-14-2015 05:10 AM
- Posted Re: Monitoring of Java Virtual Machines with JMX: How to clear the cache of input settings? on All Apps and Add-ons. 04-14-2015 05:04 AM
- Posted Monitoring of Java Virtual Machines with JMX: How to clear the cache of input settings? on All Apps and Add-ons. 04-13-2015 05:43 AM
- Tagged Monitoring of Java Virtual Machines with JMX: How to clear the cache of input settings? on All Apps and Add-ons. 04-13-2015 05:43 AM
- Tagged Monitoring of Java Virtual Machines with JMX: How to clear the cache of input settings? on All Apps and Add-ons. 04-13-2015 05:43 AM
- Tagged Monitoring of Java Virtual Machines with JMX: How to clear the cache of input settings? on All Apps and Add-ons. 04-13-2015 05:43 AM
- Posted Re: JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 01:01 PM
- Posted Re: JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:41 AM
- Posted Re: JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:39 AM
- Posted JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:28 AM
- Tagged JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:28 AM
- Tagged JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:28 AM
- Tagged JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:28 AM
- Tagged JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:28 AM
- Tagged JMS Modular Input - Unsupported major.minor version 51.0 on All Apps and Add-ons. 02-17-2015 06:28 AM
Topics I've Started
04-14-2015
05:10 AM
Eventually ran a packet capture and discovered that the IP listed in "Connection refused to host: 192.168.100.137;" actually came from the device itself. It has two NIC's and I was trying to route traffic to it on the NIC to which the JMX was not binded because I was trying to keep the JMX traffic on the same network and not have to route it through a series of security appliances and a firewall.
... View more
04-14-2015
05:04 AM
Good question. I edited both at the same time. I am getting the error on both stanzas:
4/13/15
11:20:50.365 AM
04-13-2015 11:20:50.365 -0400 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\SPLUNK4JMX\bin\jmx.py"" host=192.168.100.184, jmxServiceURL=, jmxport=1099, jvmDescription=EHE-FORUM-SOA-EXT-1, processID=0,stanza=jmx://Forum-EHE_EveryMinute,systemErrorMessage="Connection refused to host: 192.168.100.137; nested exception is:
Here is the Hourly config:
<!-- Hourly Polling -->
<jmxpoller>
<formatter className="com.dtdsoftware.splunk.formatter.TokenizedMBeanNameQuotesStrippedFormatter"/>
<cluster name="XXX" description="XXX">
<mbean domain="XXX" properties="XXX" dumpAllAttributes="true"/>
<jmxserver host="192.168.100.184" jmxport="1099" lookupPath="/fsjmx" jvmDescription="EHE-FORUM-SOA-EXT-1" jmxuser="XXX" jmxpass="XXX"/>
<jmxserver host="192.168.100.186" jmxport="1099" lookupPath="/fsjmx" jvmDescription="EHE-FORUM-SOA-EXT-2" jmxuser="XXX" jmxpass="XXX"/>
</cluster>
</jmxpoller>
Here is the EveryMinute Config:
<!-- Minute Polling -->
<jmxpoller>
<formatter className="com.dtdsoftware.splunk.formatter.TokenizedMBeanNameQuotesStrippedFormatter"/>
<cluster name="forum-prod_8x" description="PROD Forum Systems 8.x">
<mbean domain="XXX" properties="name=XXX">
<attribute name="CPU Utilization" outputname="cpuUtilization"/>
</mbean>
<jmxserver host="192.168.100.184" jmxport="1099" lookupPath="/fsjmx" jvmDescription="EHE-FORUM-SOA-EXT-1" jmxuser="XXX" jmxpass="XXX"/>
<jmxserver host="192.168.100.186" jmxport="1099" lookupPath="/fsjmx" jvmDescription="EHE-FORUM-SOA-EXT-2" jmxuser="XXX" jmxpass="XXX"/>
</cluster>
</jmxpoller>
This is a known good config set up as I have it deployed to 9 other Splunk servers successfully collecting both hourly and every minute data.
... View more
04-13-2015
05:43 AM
I have a JMX monitor I first deployed with a typo in the IP Address. I updated the JMX XML Config file with the new IP, however JMX is still trying to poll the old IP. I have done the following to try and clear the issue, however the problem still persists.
Restarted splunk
Removed the app that configures the inputs
Restarted splunk
Re-deployed the app that configures the input
Restarted splunk
Here are the log entries from splunkd.log that lead me to realize that I had keyed in the wrong IP:
04-13-2015 08:00:28.136 -0400 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\SPLUNK4JMX\bin\jmx.py"" host=192.168.100.137, jmxServiceURL=, jmxport=1099, jvmDescription=EHE-FORUM-SOA-EXT-1, processID=0,stanza=jmx://Forum-EHE_EveryMinute,systemErrorMessage="Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.100.137; nested exception is:
04-13-2015 08:00:28.136 -0400 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\SPLUNK4JMX\bin\jmx.py"" java.net.ConnectException: Connection timed out: connect]"
Here are the log entries from splunkd.log after correcting the IP:
04-13-2015 08:01:13.740 -0400 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\SPLUNK4JMX\bin\jmx.py"" host=192.168.100.184, jmxServiceURL=, jmxport=1099, jvmDescription=EHE-FORUM-SOA-EXT-1, processID=0,stanza=jmx://Forum-EHE_Hourly,systemErrorMessage="Connection refused to host: 192.168.100.137; nested exception is:
04-13-2015 08:01:13.740 -0400 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\SPLUNK4JMX\bin\jmx.py"" java.net.ConnectException: Connection timed out: connect"
Old Host IP: 192.168.100.137
New Host IP: 192.168.100.184
How do I clear the residual cache of the old IP?
... View more
02-17-2015
01:01 PM
Dug deeper and discovered that openjdk 1.6 is pre-installed on our RedHat server image. Not sure what has changed between 1.3.7 and 1.3.8 in terms of how you find the java executable to use, but 1.3.7 finds jre 1.7 and 1.3.8 was finds openjdk 1.6 and throwing the Unsupported version error even though JAVA_HOME is mapped to jre 1.7.
To resolve the issue, I first uninstalled openjdk 1.6, which caused jmy.py to throw a 'file not found' error. Next, I re-installed jre 1.7 and 1.3.8 worked fine.
... View more
02-17-2015
06:41 AM
I also have re-installed 1.3.7 and the same command returns the schema.
... View more
02-17-2015
06:39 AM
Only Java 1.7u67 is installed and $JAVA_HOME is mapped to /usr/java/latest:
[user@server java]$ sudo echo $JAVA_HOME
/usr/java/latest/bin/java
[user@server java]$ sudo ls -la /usr/java
total 12
drwxr-xr-x 3 root root 4096 Feb 17 09:08 .
drwxr-xr-x. 15 root root 4096 Feb 17 09:08 ..
lrwxrwxrwx 1 root root 16 Feb 17 09:08 default -> /usr/java/latest
drwxr-xr-x 6 root root 4096 Feb 17 09:08 jre1.7.0_67
lrwxrwxrwx 1 root root 21 Feb 17 09:08 latest -> /usr/java/jre1.7.0_67
[user@server java]$
... View more
02-17-2015
06:28 AM
Since installing JMS Modular Input version 1.3.8, I am getting the following errors when Splunk starts:
02-17-2015 09:19:30.278 -0500 ERROR ModularInputs - Unable to initialize modular input "jms" defined inside the app "jms_ta": Introspecting scheme=jms: script running failed (exited with code 1).
02-17-2015 09:19:30.237 -0500 ERROR ModularInputs - Introspecting scheme=jms: script running failed (exited with code 1).
02-17-2015 09:19:29.999 -0500 INFO SpecFiles - Found external scheme definition for stanza "jms://" with 23 parameters: jndi_initialcontext_factory, jndi_provider_url, jndi_user, jndi_pass, destination_user, destination_pass, jms_connection_factory_name, durable, index_message_properties, index_message_header, message_selector, strip_newlines, init_mode, local_init_mode_resource_factory_impl, local_init_mode_resource_factory_params, message_handler_impl, message_handler_params, client_id, user_jndi_properties, browse_queue_only, browse_frequency, browse_mode, jvm_system_properties
0
When I run the command 'splunk cmd python /opt/splunk/etc/apps/jms_ta/bin/jms.py --scheme' as the user splunkd runs as, I get the following error:
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/splunk/modinput/jms/JMSModularInput : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
Could not find the main class: com.splunk.modinput.jms.JMSModularInput. Program will exit.
What do I need to do to resolve this?
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
06-05-2020
02:02 AM
|
