Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
736 views

Connectivity issue between Diagnostics Server & Probe

Hello Team,

I have installed Diagnostics 9.24 Server on windows machine & the Diagnostics probe 9.24 on Linux system.

This is Java probe which is installed on Orcle application server. 

Following check has been done.

--> Port connectivity from Application server ( Where java probe installed) to Diagnostics server. (2006 & 2612)

--> Application string has been updated successfully on Application server after probe installation.

--> We are not able to find probe.log file in log folder.

But We are not able to port 35000 to 35100 from Diagnostics server to Application server.

Could you please let me know the next action so we can proceed further.

Thanks in advance.

5 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Connectivity issue between Diagnostics Server & Probe

If you cannot find probe.log, it looks like your probe is not even running. Did you instrument your Oracle app server and started it afterwards?

Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: Connectivity issue between Diagnostics Server & Probe

Yes. we have instrumented the application string on server & then restarted the services.

Please let me know if we can validate, if the probe installed properly.

Thanks in advance.

Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: Connectivity issue between Diagnostics Server & Probe

Please find the attached "opmn.xml" file. Please validate the same for application instrumentation & let me know the next action items. Please go through the below application details for probe.

Oracle Application Server Version:- 10.1.2.3
Linux Operating System version:- RHEL 4.x
Java Version:- 1.4.2_04

 

Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: Connectivity issue between Diagnostics Server & Probe

Hi,

We have started java probe using "StartAgent.sh" & its running in backround. we are able to see vm & host details in Diagnostics profiler but not getting any server request, methods, load. We are getting application traffic for same server in RUM.

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: Connectivity issue between Diagnostics Server & Probe

Hi Vijay,

The test probe only collectects the host matrics. As the name shows it is just for testing.

Are you able to see the testprobe on the commander UI? Is so this means that the connectivity is ok. If now you need to confirm the poft connectivity. Also you can check the test probe logs inside the probe log directory.

If you are stating the application with the instrumentation and you are not able to see the logs you can also try adding the following argument to the instrumentation:

-Dprobe.log.dir=/<pathon where you want the logs>

 

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.