Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Absent Member.. Bhati_Saurabh Absent Member..
Absent Member..
1692 views

RUM Probe not connecting to RUM Engine.

Hi Experts,

 

Need your help here. My RUM Probe is not communicating with Engine.

 

My RUM probe is installed on a Linux machine and Engine is on Windows box. 

 

Attached is the screenshot of the error message.

 

Please suggest.

 

Best Regards,

Saurabh

0 Likes
11 Replies
Micro Focus Expert
Micro Focus Expert

Re: RUM Probe not connecting to RUM Engine.

Hi Saurabh,

Are you using the default SSL connection method with the default certificates (e.g. no customisation)?

Can you see errors in the Configuration Manager log on the RUM Engine (config.manager.log)?

What versions are you using for Windows, Linux and RUM?

Regards,

Tim

0 Likes
Absent Member.. Bhati_Saurabh Absent Member..
Absent Member..

Re: RUM Probe not connecting to RUM Engine.

Hi Tim,

Yes, I believe so this is the default SSL connection method with te default certificates. If you can give me some steps to ckeck this.

I could see these errors as below:

16-01-21 07:00:39,915 [Timer-95] (ProbeConfigurationProcessor.java:81) INFO - Synchronization of probe time for probe: 159.231.245.80 ended successfully.
2016-01-21 07:00:39,915 [Timer-95] (ConfigManager.java:116) INFO - Retrieve Configuration started.
2016-01-21 07:00:39,915 [Timer-95] (BACSettingsRetriever.java:78) INFO - BAC settings loaded successfully. TMCRequestInvoker was set with new settings: {
BaseURL=https://cibcptebac.cibc.com:443
AuthenticationSettings=no authentication
Proxy=no proxy
SSL Settings={keystore=false, truststore=false, validate trusted=false, validate expiration=false, host validation=false}
Timeout Settings={new connection timeout =120000,response timeout=120000}
Retry Settings={retryOnSent =false,retries=3}
}
2016-01-21 07:00:39,931 [Timer-95] (BACSettingsRetriever.java:78) INFO - BAC settings loaded successfully. TMCRequestInvoker was set with new settings: {
BaseURL=https://cibcptebac.cibc.com:443
AuthenticationSettings=no authentication
Proxy=no proxy
SSL Settings={keystore=false, truststore=false, validate trusted=false, validate expiration=false, host validation=false}
Timeout Settings={new connection timeout =120000,response timeout=120000}
Retry Settings={retryOnSent =false,retries=3}
}
2016-01-21 07:00:39,931 [Timer-95] (EngineRegistratorJMXHelper.java:53) INFO - Warning occurred while trying to get pages rate from JMX
2016-01-21 07:00:40,197 [Timer-95] (MobileStaticConfigurationFileHandler.java:122) INFO - Folder for CM static configurations does not exist (D:\HPRUM\log\configuration\mobileStaticConfigs\). Skip cleaning it up.
2016-01-21 07:00:44,822 [Timer-95] (ConfigPublisher.java:148) INFO - Starting publish configuration
2016-01-21 07:00:44,822 [Timer-95] (BBConfigPublisher.java:29) INFO - Publishing configuration to Probe Configuration Processor.
2016-01-21 07:00:44,822 [Timer-95] (ProbeConfigurationProcessor.java:109) INFO - Creating Items Tree (for probe configuration).
2016-01-21 07:00:44,837 [Timer-95] (ProbeConfigurationProcessor.java:113) INFO - Items Tree creation ended.
2016-01-21 07:00:44,837 [Timer-95] (ProbeConfigurationProcessor.java:149) INFO - Processing probe configuration for probe: 10.161.57.233
2016-01-21 07:00:44,837 [Timer-95] (ProbeConfigurationProcessor.java:189) INFO - Building configuration for probe: 10.161.57.233...
2016-01-21 07:00:44,853 [Timer-95] (Section.java:711) INFO - In section: [global] Found an unknown parameter: 'regex_log_threshold'. this means that rum engine is not familier with it (for parsing purposes) but the probe may recognize it so it will be put in the probe configuration as is.
2016-01-21 07:00:44,853 [Timer-95] (BBConfigurationBuilder.java:328) WARN - probe-10.161.57.233: could not find expected constant section '[cache saveapprequest]'.
2016-01-21 07:00:44,853 [Timer-95] (Section.java:711) INFO - In section: [channel rum-tier-discovery] Found an unknown parameter: 'Content'. this means that rum engine is not familier with it (for parsing purposes) but the probe may recognize it so it will be put in the probe configuration as is.
2016-01-21 07:00:44,853 [Timer-95] (ProbeConfigurationProcessor.java:193) INFO - Finished building Configuration for probe: 10.161.57.233 .
2016-01-21 07:00:44,853 [Timer-95] (ProbeConfigurationProcessor.java:149) INFO - Processing probe configuration for probe: 159.231.245.80
2016-01-21 07:00:44,853 [Timer-95] (ProbeConfigurationProcessor.java:189) INFO - Building configuration for probe: 159.231.245.80...
2016-01-21 07:00:44,853 [Thread-307980] (ProbeConfigurationProcessor.java:206) INFO - Handling configuration for probe: 10.161.57.233...
2016-01-21 07:00:44,853 [Thread-307980] (BBConfigurationHandler.java:132) INFO - Configuration file path for probe 10 (10.161.57.233): D:\HPRUM\log\configuration\capture.conf_10.161.57.233_2020
2016-01-21 07:00:44,869 [Thread-307980] (BBConfigurationHandler.java:192) INFO - Sending configuration to probe 10.161.57.233
2016-01-21 07:00:44,869 [Thread-307980] (BBConfigurationHandler.java:247) INFO - request URL :https://10.161.57.233:2020/nohtml/config/file.html
2016-01-21 07:00:44,869 [Thread-307980] (BBConfigurationHandler.java:253) INFO - ssl: {keystore=true, truststore=true, validate trusted=false, validate expiration=false, host validation=false}

2016-01-21 07:00:44,869 [Timer-95] (Section.java:711) INFO - In section: [global] Found an unknown parameter: 'regex_log_threshold'. this means that rum engine is not familier with it (for parsing purposes) but the probe may recognize it so it will be put in the probe configuration as is.
2016-01-21 07:00:44,869 [Timer-95] (BBConfigurationBuilder.java:328) WARN - probe-159.231.245.80: could not find expected constant section '[cache saveapprequest]'.
2016-01-21 07:00:44,869 [Timer-95] (Section.java:711) INFO - In section: [channel rum-tier-discovery] Found an unknown parameter: 'Content'. this means that rum engine is not familier with it (for parsing purposes) but the probe may recognize it so it will be put in the probe configuration as is.
2016-01-21 07:00:44,884 [Timer-95] (ProbeConfigurationProcessor.java:193) INFO - Finished building Configuration for probe: 159.231.245.80 .
2016-01-21 07:00:44,884 [Thread-307981] (ProbeConfigurationProcessor.java:206) INFO - Handling configuration for probe: 159.231.245.80...
2016-01-21 07:00:44,884 [Thread-307981] (BBConfigurationHandler.java:132) INFO - Configuration file path for probe 11 (159.231.245.80): D:\HPRUM\log\configuration\capture.conf_159.231.245.80_2020
2016-01-21 07:00:44,900 [Thread-307981] (BBConfigurationHandler.java:192) INFO - Sending configuration to probe 159.231.245.80
2016-01-21 07:00:44,900 [Thread-307981] (BBConfigurationHandler.java:247) INFO - request URL :https://159.231.245.80:2020/nohtml/config/file.html
2016-01-21 07:00:44,900 [Thread-307981] (BBConfigurationHandler.java:253) INFO - ssl: {keystore=true, truststore=true, validate trusted=false, validate expiration=false, host validation=false}

2016-01-21 07:00:45,650 [Timer-95] (ProbeConfigurationProcessor.java:97) ERROR - Caught Exception:Failed to handle probe: 10.161.57.233 configuration.
com.mercury.rum.engine.probe.configuration.abstraction.exception.ConfigurationProcessFailedException: Failed to handle probe: 10.161.57.233 configuration.
at com.mercury.rum.engine.probe.configuration.abstraction.ProbeConfigurationProcessor.handleConfiguration(ProbeConfigurationProcessor.java:213)
at com.mercury.rum.engine.probe.configuration.abstraction.ProbeConfigurationProcessor.access$000(ProbeConfigurationProcessor.java:40)
at com.mercury.rum.engine.probe.configuration.abstraction.ProbeConfigurationProcessor$ProcessingThread.run(ProbeConfigurationProcessor.java:285)
Caused by: com.mercury.rum.engine.probe.configuration.impl.beatbox.exception.ConfigurationSendException: Could not send configuration for probe: 10.161.57.233.
at com.mercury.rum.engine.probe.configuration.impl.beatbox.BBConfigurationHandler.sendConfiguration(BBConfigurationHandler.java:142)
at com.mercury.rum.engine.probe.configuration.impl.beatbox.BBConfigurationHandler.handleConfiguration(BBConfigurationHandler.java:90)
at com.mercury.rum.engine.probe.configuration.abstraction.ProbeConfigurationProcessor.handleConfiguration(ProbeConfigurationProcessor.java:208)
... 2 more
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1884)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:804)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312)
at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:702)
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:122)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:121)
at java.io.FilterOutputStream.write(FilterOutputStream.java:97)
at org.apache.commons.httpclient.methods.ByteArrayRequestEntity.writeRequest(ByteArrayRequestEntity.java:90)
at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at com.mercury.rum.engine.common.connection.http.RUMHttpClient.executeMethod(RUMHttpClient.java:257)
at com.mercury.rum.engine.common.connection.http.RUMHttpClient.executePost(RUMHttpClient.java:189)
at com.mercury.rum.engine.probe.configuration.impl.beatbox.BBConfigurationHandler.send(BBConfigurationHandler.java:196)
at com.mercury.rum.engine.probe.configuration.impl.beatbox.BBConfigurationHandler.sendConfiguration(BBConfigurationHandler.java:138)
... 4 more
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
at sun.security.validator.Validator.validate(Validator.java:260)
at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:107)
at com.mercury.rum.engine.common.connection.http.CostumValidateX509TrustManagerDecorator.checkServerTrusted(CostumValidateX509TrustManagerDecorator.java:42)
at sun.security.ssl.AbstractTrustManagerWrapper.checkServerTrusted(SSLContextImpl.java:813)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1323)
... 26 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196)
at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268)
at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:380)
... 34 more
2016-01-21 07:00:45,681 [Timer-95] (ConfigPublisher.java:179) ERROR - Error occurred while publishing to PROBE_CONFIG Publisher
com.mercury.rum.engine.configmanager.configpublisher.NonCriticalModulePublisherException: Not all probes configured successfully
at com.mercury.rum.engine.configmanager.configpublisher.BBConfigPublisher.publish(BBConfigPublisher.java:47)
at com.mercury.rum.engine.configmanager.configpublisher.BBConfigPublisherForBSM.publish(BBConfigPublisherForBSM.java:12)
at com.mercury.rum.engine.configmanager.configpublisher.ConfigPublisher.publishConfiguration(ConfigPublisher.java:168)
at com.mercury.rum.engine.configmanager.configpublisher.ConfigPublisher.publish(ConfigPublisher.java:152)
at com.mercury.rum.engine.configmanager.configretriever.ConfigurationRetriever.retrieveAndPublishConfiguration(ConfigurationRetriever.java:103)
at com.mercury.rum.engine.configmanager.ConfigManager.retrieveConfiguration(ConfigManager.java:121)
at com.mercury.rum.engine.configmanager.ConfigManager.handleTimerTick(ConfigManager.java:179)
at com.mercury.rum.engine.configmanager.ConfigManager$1.handleNotification(ConfigManager.java:78)
at com.mercury.rum.engine.common.jmx.timer.NotificationAdapter.handleNotification(JMXTimer.java:433)
at sun.reflect.GeneratedMethodAccessor230.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.mx.notification.NotificationListenerProxy.invoke(NotificationListenerProxy.java:154)
at com.sun.proxy.$Proxy92.handleNotification(Unknown Source)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:274)
at javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:339)
at javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:324)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:247)
at javax.management.timer.Timer.sendNotification(Timer.java:1235)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1197)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1286)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
2016-01-21 07:00:46,853 [Timer-95] (LocationDimConfigParser.java:113) INFO - end of building location hierarchy. 1043 locations found.
2016-01-21 07:00:46,915 [Timer-95] (MappingTablePublisher.java:30) INFO - Publishing configuration to Mapping Tables Handler.
2016-01-21 07:00:47,119 [Timer-95] (ConfigManager.java:122) INFO - Retrieve and Publish of Configuration failed.

Have attached the config.manager.log file for ref please.

The versions:

HP RUM: 9.25

RUM Engine Windows:Windows Server 2008 R2 Enterprise SP1.

RUM Probe Linux:Red Hat Enterprise Linux Server release 5.6 (Tikanga)

 

Thanks,

Saurabh

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: RUM Probe not connecting to RUM Engine.

Hi Saurabh,

I can see handshake errors in the log so it looks like it's a problem with the SSL comms.  This is unusual for a default RUM install as it uses default pre-installed SSL config.

Can you post a screen shot of the Probe config in the RUM Engine console?  Go to Probe Management, click on Edit (for each probe), expand all sections (so I can see the Authentication, Proxy and SSL sections as well).

Can you also send rpsecurity.conf from each probe?  This is found in ...etc/rum_probe/

Please can you also confirm the installation paths of RUM Engine and RUM Probe?

Also, is this a new install or was it working previously?  Usually, the comms between Engine and Probe has to be working for the Probe to be added to the Engine.

It is possible to turn off SSL, but it's best to try and get it working first.

Regards,
Tim

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: RUM Probe not connecting to RUM Engine.

Hi Bhati,

Are you using default certificates to encrypt Engine\Probe communication?

Was you Engine upgraded or installed from scratch?

In case you are using default ones, please try to the following: find file on RUM Engine file system HPRUM\conf\probes\probe_keystore.jks, backup it and substitute with one from attachment.

Then try to connect Probe again.

Best regards, Alexey

 

Absent Member.. Bhati_Saurabh Absent Member..
Absent Member..

Re: RUM Probe not connecting to RUM Engine.

Hello Tim,

Please find the details attached.

This was working before. We noticed on 5th of Jan.

This was working properly.

It is possible to turn off SSL, but it's best to try and get it working first. -- How to do this?

 

Best Regards,

Saurabh

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: RUM Probe not connecting to RUM Engine.

Hi Saurabh,

Did you tried steps i have proposed in previous post?

Best regards, Alexey

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: RUM Probe not connecting to RUM Engine.

Hi Saurabh,

Try Alexey's recommendation first.

It may also be worth uninstalling and reinstalling the RUM Probe software on one of the Probes to see if that does make a difference.  Although it is strange that this would happen to both Probes at once, suggesting the problem is on the Engine or somewhere else.

Does the Engine communicate with the Probes directly, or is there some kind of proxy in the middle?

Also, does the Probe software run as root or as another user (e.g. the rum_probe user)?  I had another look at the config.manager.log you sent and saw this:

   unable to find valid certification path to requested target

Check the paths and permissions of the keystore on your Engine (the screenshot shows it as D:\HPRUM/conf/probes/probe_keystore.jks which is the default).  And also check the permissions on all the files starting "rum-probe-" in .../etc/rum_probe/ on the Probes - make sure the user that RUM Probe runs as is the owner with read write permissions, e.g.:

-rw-rw----. 1 rum_probe rum_probe   2842 Jan 25  2015 rum-probe-ca.crt
-rw-rw----. 1 rum_probe rum_probe   2517 Jan 25  2015 rum-probe-c.p12
-rw-rw----. 1 rum_probe rum_probe    272 Jan 25  2015 rum_probe_public_key.pem
-rw-rw----. 1 rum_probe rum_probe   1306 Jan 25  2015 rum-probe-server.crt
-rw-rw----. 1 rum_probe rum_probe   1679 Jan 25  2015 rum-probe-server.key

If RUM Probe runs as another user (e.g. rum_probe), run /usr/bin/rp_user.pl with the user name as a parameter (e.g. ./rpuser.pl rum_probe).  That should set the correct permissions on all the RUM Probe files and directories.

 

If you do want to disable SSL between Probe and Engine, you have to change the following:

1) RUM Probe: edit rpsecurity.conf and change use_ssl from true to false, then restart RUM Probe

2) RUM Engine: Go to Probe Management and change Protocol from HTTPS to HTTP in the Connection to Probe section

Regards,

Tim

0 Likes
Absent Member.. Bhati_Saurabh Absent Member..
Absent Member..

Re: RUM Probe not connecting to RUM Engine.

Hello Alexey,

Thanks for the steps provided. I did try the step now and it worked for me!

Thanks a ton for your help here.

But Alex, I just wanted to understand. Hw come this file had issues? does the  default keystore have a validity date? I mean how come this had a problem? If you can throw some light on this too.

 

Best Regards,

Saurabh

 

 

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: RUM Probe not connecting to RUM Engine.

Hi Saurabh,

When you do ugrade\import RUM configuration you actually import old keystore with old certificates. It is logically because you can harden your RUM Engine with your own certificates instead of HP defaults.

So, I suppose you have upgraded RUM Engine with old certificates in the keystore. R&N will provide an answer why they are  not working anymore (there is a case on that).

Best regards, Alexey

0 Likes
Absent Member.. Bhati_Saurabh Absent Member..
Absent Member..

Re: RUM Probe not connecting to RUM Engine.

Hi Alexey,

Thanks, this works for me. But I hava another issue, and I duubt this has something to do with it?

I am trying to decrypt SSL traffic for a perticular app and this is not working. This works in our Prod Environment, but surprised why this is not working In PTE.

Can you please suggest?

 

Regards,

Saurabh

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: RUM Probe not connecting to RUM Engine.

Hi Saurabh,

I do not think those issues are connected. But you can try to do the following:

1. Delete the key from Probe Management and upload it again;

2. Record traffic for this application with Wireshark and use this key in Wireshark to decrypt it.

Best regards, Alexey

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.