Handling Error Messages and Alerts in ScaleArc Logs

Article Summary

This article addresses common error messages encountered in ScaleArc logs, specifically related to connection issues with the SQL DB Server. It provides an explanation of the errors, the underlying causes, and the recommended steps to resolve them.

Problem

Error Messages:

1. Connection to server failed due to error: 'Cannot assign requested address'
2. Unable to put the connection in the used pool. debuginfo

Cause

1. Connection Error ('Cannot assign requested address'):

   • This error occurs when ScaleArc attempts to use a specific IPcombination to connect to the SQL database, but the port is currently in use or exhausted.
   • ScaleArc retries using a new IPcombination.
   • Impact: This error does not typically impact application performance, as ScaleArc continues retrying connections until a valid port is found.

2. Connection Pool Error ('Unable to put the connection in the used pool. debuginfo'):

   • This alert is triggered by ScaleArc's health monitor when a specific user (e.g., GIW_WEB_user) is missing from the  Users & DBs  section.
   • Impact: It does not affect the normal query traffic or the overall functionality of the cluster.

Solution

1. Port Exhaustion (Connection to Server Failed):

   • ScaleArc automatically retries the connection with a different IP combination. The alert does not require any manual intervention unless persistent failures occur.

2. Used Pool Alert (Unable to Put the Connection in the Used Pool):

   • Ensure that the user in question is properly configured in the Users & DBs section.
   • Perform a cluster restart to resolve persistent alerts related to the health monitor.

   For instructions on restarting the cluster, refer to Starting/Stopping a Cluster.

Additional Information

• These alerts should not cause errors on the application side. ScaleArc's built-in mechanisms, such as retrying connections and automatic health monitoring, mitigate potential issues.
• Recommended Action: If these alerts persist or impact the application, restarting the cluster should resolve the issue.