What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

JMX probe connectivity issue

Votes:

0

Facing issue with JMX probe. Getting below error.

Error
-------
 /opt/jmx/logs/wrapper.log


INFO   | jvm 1    | 2022/01/31 12:35:20 | Connection/SSL Problem; Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
INFO   | jvm 1    | 2022/01/31 12:35:20 |       java.net.SocketTimeoutException: Read timed out] (Service URL: service:jmx:rmi://broker.x.x.xx.:44445/jndi/rmi://broker.x.x.x:1100/karaf-amq1-broker-mq)


=======================================================================

[root@NM04 ~]# systemctl status jmxprobe.service
● jmxprobe.service - JMX MiniProbe
   Loaded: loaded (/etc/systemd/system/jmxprobe.service; enabled; vendor preset: disabled)
   Active: active (exited) since Mon 2022-01-31 13:23:12 +04; 20h ago
  Process: 48703 ExecStop=/opt/jmx/bin/JMXMiniProbe stop (code=exited, status=0/SUCCESS)
  Process: 48862 ExecStart=/opt/jmx/bin/JMXMiniProbe start (code=exited, status=0/SUCCESS)
 Main PID: 48862 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/jmxprobe.service
           ├─48908 /opt/jmx/bin/./wrapper-linux-x86-64 /opt/jmx/etc/wrapper.conf wrapper.syslog.ident=JMXMiniProbe wrapper.pidfile=/opt/jmx/logs/JMXMiniProbe.pid wr...
           └─48910 java -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.manageme...

Jan 31 13:23:12 SV-HQF-LEP-NM04 systemd[1]: Starting JMX MiniProbe...
Jan 31 13:23:12 SV-HQF-LEP-NM04 JMXMiniProbe[48862]: Starting JMXMiniProbe...
Jan 31 13:23:12 SV-HQF-LEP-NM04 systemd[1]: Started JMX MiniProbe.
[root@SV-HQF-LEP-NM04 ~]

jmx probe prtg

Created on Feb 1, 2022 7:43:22 AM

Last change on Feb 2, 2022 7:53:11 AM by Felix Wiesneth [Paessler Support]



4 Replies

Votes:

0

Hi there,

First, please note that the JMX Mini Probe has been thoroughly developed but meant as proof-of-concept it is officially not supported, so troubleshooting will be limited.

The error message ("Failed to retrieve RMIServer stub") most likely occurs if firewalls block the dynamic ports which are used for this connection, see:
https://serverfault.com/questions/308662/how-do-i-fix-a-failed-to-retrieve-rmiserver-stub-jmx-error

Here, I'd recommend to follow the configuration hints listed in the article.

Beside that please confirm that you've enabled the JMX Remote access as described in step 2 (Prepare and start the JMX Mini Probe):
https://kb.paessler.com/en/topic/61010-how-can-i-monitor-java-applications-via-jmx-with-a-prtg-mini-probe

Best,
Sebastian

Created on Feb 7, 2022 8:47:42 AM by Sebastian Kniege [Paessler Support]



Votes:

0

JMX remote probe was working fine a few months back. Since we are not using PRTG for the last 2 months, didn't notice it stop working.

I have added a new JMX probe by stopping the existing one and it is working fine. But adding the devices to the probe is getting the Connection/SSL Problem.

I am not sure if it issues with the application side SSL error.

Is there any way to check this?

Can you suggest on this?

Created on Feb 8, 2022 1:48:43 PM



Votes:

0

Hi,

Did you notice the following remark from this article:

If you get an SSL handshake failure, it might be necessary to choose the weakened SSL security option for the web server in the PRTG System Administration! (see Setup > System Administration > User Interface

Best,
Sebastian

Created on Feb 11, 2022 1:31:35 PM by Sebastian Kniege [Paessler Support]



Votes:

0

Thanks

Created on May 5, 2022 10:40:33 AM




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.