VCF Ops displays log collection status error 'Failed to get the status for VC log collection configuration. Internal Error - An error occurred on the server '

Products

• VCF Operations

Issue/Introduction

In VCF Ops, the following error may be displayed when validating vCenter log collection status:

Failed to get the status for VC log collection configuration. Internal Error - An error occurred on the server side.

Failed to configure component

Despite the error, the log forwarding configuration is successfully applied and logs continue to flow to the configured destination without interruption.

applmgmt.log @ /var/log/vmware/applmgmt/ in the vCenter reports the below:

VCF Ops performs two separate vCenter API operations:

1. Apply Configuration
   • PUT /rest/appliance/logging/forwarding
   • Successfully persists the log forwarding configuration.
2. Validate/Test Configuration
   • POST /rest/appliance/logging/forwarding?action=test
   • Requires a new socket connection to validate the configuration.
   • Fails with OSError: [Errno 24] Too many open files when the appliance has exhausted available file descriptors, causing vCenter to return an HTTP 500 error.

As a result, VCF Ops reports a status validation failure even though log collection itself remains functional.

Environment

VCF Operations for logs 9.0.x 
VCF Operations 9.0.x 

Cause

This issue occurs when the vCenter Appliance Management service (applmgmtd/VAMI) exhausts its available file descriptors due to a socket leak. The service reaches its soft limit of 1024 open file descriptors, preventing it from opening new connections.

Resolution

Recommended Fix:

Upgrade the VCF version to 9.1.0, where this issue has been addressed. Refer to Upgrading to VMware Cloud Foundation 9.1 for insight towards the upgrade. 

Workaround:

Restart the Appliance Management service on the affected vCenter appliance to release the leaked file descriptors.

service-control --restart applmgmt

After the service restart, the VCF Ops UI typically recovers within approximately 5 minutes, and the log collection status changes back to CONFIGURED during the next status polling cycle.