url_response probe generates failed alert in uim but the url is up, available and working fine.

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

There was an IP change on the server and afterward, it stopped working.

Feb  2 16:29:10:436 [2068] url_response: [test_url] DBG: connect to ##.##.##.## port 80 failed: Timed out 
Feb  2 16:29:10:436 [2068] url_response: [test_url] DBG: Failed to connect to <hostname> port 80 after 21001 ms: Couldn't connect to server

and

Feb  2 16:29:10:436 [2068] url_response: [test_url] failed: Timeout was reached (28) 

Environment

• DX UIM 20.4
• url_response, latest version

Resolution

1. Check if anything is interfering with access to the web server/page such as a local or remote firewall, firewall rules, source host access to the target web server/site, SELinux, security software, etc. and/or check webserver httpd logs if there is any access/errors citing the source trying to connect to it.

2. The network team may use Wireshark to analyze the network traffic/conversation between the robot and the web server site url.

3. Check with ping and tracert were successful, in this particular scenario, each test was successful.

4. Test via browser on the Primary hub worked fine, page loaded, but the test failed when using url_response to connect to the url

5. Check if the browser uses a proxy configuration...

6. You can download and install curl and try the following curl command. This can be helpful in testing from the source robot machine that you're using to monitor the url:

7. Try something like this from the command line on the robot but replace the url with the one you are trying to monitor:
   
   curl -v -i http://<hostname>/<rest of the url>/<login_portion>

8. If "curl" cannot connect to the URL, neither can url_response as url_response probe uses curl.