url_response: [<profile_name>] failed: Timeout was reached (28).
Article ID: 34955
Updated On:
Products
DX Unified Infrastructure Management (Nimsoft / UIM)
Unified Infrastructure Management for Mainframe
CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
Issue/Introduction
The url_response Timeout setting is set to 30 seconds (default) when you create a new profile. Some customers see timeout errors due to this out of the box default setting.
When a timeout occurs, the probe inserts a NULL value in the database, therefore, any related SLA calculations can potentially be impacted.
The alarms seem to come in waves: Server A will have 4 alarms from 4 of the 14 websites, but then work for another few hours with no problem. Usually, but not always, Server B will throw some alarms, but never from the same servers at the same time.
Often their presence in the alarm console/sub-console is short-lived as it can clear quickly.They are only visible via email alert or via nas Transaction history using a filter.
When a timeout occurs, the probe inserts a NULL value in the database, therefore, any related SLA calculations can potentially be impacted.
The alarms seem to come in waves: Server A will have 4 alarms from 4 of the 14 websites, but then work for another few hours with no problem. Usually, but not always, Server B will throw some alarms, but never from the same servers at the same time.
Often their presence in the alarm console/sub-console is short-lived as it can clear quickly.They are only visible via email alert or via nas Transaction history using a filter.
Environment
- Any UIM Release
Resolution
Set the Timeout for the profile(s) to 90 or higher. If this does not resolve the issue, you will likely need to investigate from the network/firewall side.
the following command can be helpful if you are running url_response from a Linux machine:
curl -v -i https://(url to test)
If "curl" cannot connect to the URL, neither can url_response.
Feedback
Yes
No
Powered by
