Delayed vAPI response after vpxd reboot in VMware vCenter Server

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• The response to the executed vAPI is delayed
• In endpoint.log of vapi-endpoint on vCenter, you will see entries similar to:

 

<YYYY-MM-DD>T<time></time>.707Z | INFO  | vc-prop-collector-svc-executor-1 | VcPropertyCollector            | Waiting 15 seconds
<YYYY-MM-DD>T<time></time>.707Z | INFO  | vc-prop-collector-svc-executor-2 | VcPropertyCollector            | Waiting 15 seconds

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

• Communication between vapi-endpoint and vpxd has been interrupted due to the restart of vpxd in the past

Environment

VMware vCenter Server 7.0.x
VMware vCenter Server 6.x

Cause

A race condition could occur where if the communication between vpxd and vapi-endpoinnt is interrupted. Operation in two threads of VcPropertyCollector has a negative effect and delays the response to the executed vAPI.

Resolution

This is a known issue affecting vCenter Server 6.x and 7.x. Currently there is no resolution.

Workaround:

• If the response to the executed vAPI is delayed, restart vapi-endpoint.
• Prevent this issue by restarting the vapi-endpoint service whenever vpxd gets restarted.

Additional Information

How to stop, start, or restart vCenter Server 6.x/7.x services (2109881)