Return
-
Title
Error, "Cannot connect to Cache Server at" -
Description
Receiving frequently email alerts from TPAM regarding Cache Server connectivity with the error, "Cannot connect to Cache Server at <ip address>" -
Cause
There is a Health and Welfare service on the console appliance that invokes code every 10 minutes to perform a subset of the steps that are performed when the “Current Status” button is clicked for a cache server. That code connects to the cache server via SSH and executes a command to verify if the application server is running, and then checks for pending messages, and raises alerts when something is wrong.
These alerts could potentially come from either the Primary or Replica appliance(s). If the alerts cannot be found in the Alerts Log or Mail Agent on the Primary, it is recommend to check the Replica(s) to confirm the source. -
Resolution
STATUS:
This issue has been submitted as BFER 9994. A hotfix is available which contains improvements related to these alert messages. The changes will also be included in the TPAM 2.5.920 release.
WORKAROUND:
A reboot of the affected appliance should stop the email alert notifications, assuming the communication issue has been resolved. -
Change Request
9994