Share via

Connection Timeout Issues Between Azure Container App and Azure Database for PostgreSQL

Jan Matousek 0 Reputation points
2024-12-19T10:08:34.67+00:00

Establishing a connection to Azure Database for PostgreSQL from an Azure Container App randomly times out from a container. The connection works perfectly fine from a local workstation during the periods when timeouts occur.

The container runs Alpine Linux with Node 20, but the same issue arises when connecting directly to the container and executing psql. This happens inconsistently, usually during certain hours of the day, and not all connections during those hours fail.

Even when connections are timing out in the container, there are no issues from the local machine throughout the entire time. Additionally, metrics on the PostgreSQL service do not indicate overload or connection spikes during these problematic times.

Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
486 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Khadeer Ali 1,400 Reputation points Microsoft Vendor
    2024-12-23T19:56:05.52+00:00

    @Jan Matousek

    Welcome to the Microsoft Q&A Platform!

    Thank you for reaching out about the intermittent connection timeout issue between your Azure Container App and Azure Database for PostgreSQL.You're having intermittent connection problems between your Azure Container App and your Azure Database for PostgreSQL. Here's a simplified troubleshooting guide:

    1. Location and Network: Make sure both the app and database are in the same Azure region and connected via a private network (VNet) for better stability and security.
    2. Connection Management: Your application should efficiently manage database connections (connection pooling). Make sure it's not holding onto too many idle connections.
    3. App Resources: Check if your container app has enough CPU and memory. Low resources can cause connection issues, especially during high traffic.
    4. Database Capacity: Ensure your PostgreSQL database can handle the number of connections your app needs.
    5. Logging: Check logs from both your app and the database during connection failures to find clues. Use Azure Monitor or Application Insights for this.
    6. Firewall and DNS: Confirm the database firewall allows connections from your app. Test the connection using the database's IP address to rule out DNS problems.
    7. Network Monitoring: Use Azure's Connection Monitor to check for network problems between the app and database.

    If these steps don't help, you'll need to dig deeper into the PostgreSQL server logs and enable more diagnostics in Azure.

    If this answers your query, do click Accept Answer and Yes for "Was this answer helpful." And, if you have any further query, do let us know.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.