Troubleshooting database connection failures in virtual appliance - Identity Manager

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

The virtual appliance (vApp) monitor regularly checks network reachability to external databases with a hardcoded timeout of 3 seconds. When network latency exceeds this duration, connection errors are logged, even if the database is otherwise operational. This article provides steps to verify TCP connectivity and troubleshoot potential name resolution delays.

Environment

Virtual Appliance 14.x

Cause

Network latency or DNS resolution delays prevent the vApp monitor from establishing a database connection within the 3-second timeout threshold.

Resolution

To troubleshoot and resolve these connection errors, follow these steps:

1. Verify TCP Connectivity: Use the provided python script to test the connection directly from the vApp server to the database.
   • Attach the python_check_tcp.py script.
   • Run the script using the command: python python_check_tcp.py
   • Use the exact FQDN configured in your vApp settings.
2. Investigate Name Resolution: If the connection is slower when using an FQDN compared to an IP address, investigate your network's DNS resolution performance.
3. Configure Hosts File: As a workaround, you can add the database FQDN directly to the vApp's /etc/hosts file to bypass DNS lookup delays.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.