Error: "Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually" in Aria Operations Logs Tab
search cancel

Error: "Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually" in Aria Operations Logs Tab

book

Article ID: 406789

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • When accessing the Logs tab for any object type in VMware Aria Operations, the page may fail to load and display the following error message

    Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually



  • Additionally, in Administration > Integrations > Accounts > VMware Aria Operations for Logs Adapter (expand adapter instance), the collection state appears as Warning, and the Test Connection fails with the following error

    Wait for response of task 'Test connection' with id '###' is timed out for collector <vRealize Operations Collector-name>

Environment

VMware Aria Operations 8.18..x

Cause

Slow performance issues, hung, or unresponsive state of the Aria Operations for Logs cluster, leading to communication timeouts between Aria Operations and the Aria Operations for Logs cluster

Resolution

To resolve this issue, follow these steps:

  • Investigate and Resolve Performance Issues in Aria Operations for Logs:

    • Identify and address the slow performance or unresponsiveness of the Aria Operations for Logs cluster. This may involve checking for resource constraints, configuration issues, or other problems that could be impacting cluster performance

  • Re-Test Connection in Aria Operations for Logs Adapter:

    • In Aria Operations, navigate to:

      Administration > Integrations > Accounts > VMware Aria Operations for Logs Adapter

    • Select the affected adapter instance and click Test Connection

    • Once the test connection is successful, click Save to clear the warning state

  • Allow 2-3 collection cycles for system stabilization:

    • After saving the adapter, allow 2-3 collection cycles to complete. This will enable the system to stabilize and ensure that the Logs tab is populated correctly

  • Verify the Logs tab :

    •  After completing the above steps, check the Logs tab in Aria Operations to confirm that the issue has been resolved. The Logs tab should now load correctly, and the communication error should no longer occur