DX Unified Infrastructure Management

 Hi CA expert, I am really new to CA. I got this error for my URL_response probe (see the image below). 

What does this mean? Do not show any PID or PORT NO. Please advise me. Thanks

The attached screen shot is from archive ?

Hi Issac08,

Yup. However, I try to drag the probe to my host but do not show any PID and port no.

Have restart the probe and reinstall too.

Beside the URL_ Response probe, I encounter multiple probe that show this error as well.  

can you please increase the loglevel and share the error logs 

I increase the log level and show blank. 

please check the below thread . 

URL Response 4.43 Fails  

HI Issac08,

My probe did not go red as mention inside your article. I dun think is the same problem as yours. Mine got an error red icon (a red award picture).

After deploy no PID or PORT NO. Thanks 

Hi Hong,

Please raise support case to troubleshoot further. Hope compatibility is correct for url_response probe 

Hi, one thing to be sure to confirm is that you've met all the software requirements in the release notes.

Also make sure that you are deploying the probe to a supported platform.

If you confirm those things and still see issues, I recommend opening a Support ticket as Praveen mentioned.

Hope that helps!

Hong,

Since it is effecting multiple probes, Philip is right, make sure the OS is supported.

For troubleshooting, put url_response at log level 5 and log size 1000.

Deactivate all of the monitoring probes.

Set controller for log level 3 and log size 10000.

This will restart the robot.

Then activate url_response.

Check url_response.log & controller.log.

Hi David,

Will try it out later of the day. 

Hi Everyone,

I got it. URL_response probe does not really support Linux unless you do the KB step below.

Thanks for the support. 

https://comm.support.ca.com/kb/url-response-probe-fails-to-start-on-linux-robot/kb000036893

Hi Philip,

Yes, meet all the requirement.

There is no problem in the first place after putting in the probe. However, when days goes by it suddenly could not detect the probe on the archive (PID/Port)