The vpxd service on vCenter Server crashes with a memory panic when connected to SRM 8.5.0.7 or lower.

Products

• VMware vCenter Server

Issue/Introduction

• vpxd crashes with "Panic: Memory exceeds hard limit. Panic"
• SRM is connected to the vCenter and its version is 8.5.0.7 or lower.
• You may see messages similar to this in vmware-dr.log in SRM.

YYYY-MM-DDTHH:MM:SS.932-06:00 warning vmware-dr[15150] [SRM@6876 sub=vmomi.soapStub[114935]] SOAP request returned HTTP failure; <SSL(<io_obj p:0x00007f19b2b7b088, h:110, <TCP '10.x.x.x : 42794'>, <TCP '##:##:##:## : 8043'>>), />, method: fetchProperties; code: 500(Internal Server Error)
YYYY-MM-DDTHH:MM:SS.932-06:00 warning vmware-dr[15150] [SRM@6876 sub=LocalHms HMSUM] Exceptions during initial content retrieval for filter with token '23'
--> [(vmodl.fault.InvalidRequest) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>
-->    msg = "Received SOAP response fault from [<SSL(<io_obj p:0x00007f19b2b7b088, h:110, <TCP '##:##:##:## : 42794'>, <TCP '##:##:##:## : 8043'>>), />]: fetchProperties
--> Missing value for non-optional field propSet"

Environment

VMware vCenter Server 7.0.x

Cause

This issue occurs when SRM attempts to recreate a very large number of filters after vpxd is restarted.

Resolution

This issue is resolved in Site Recovery Manager 8.5.0.8.

Workaround:
The only workaround for this issue is to temporarily shut down the SRM server.