The vpxd-svcs service stops due to out of memory, causing some vSphere Client operations to fail
Article ID: 435888
Updated On:
Products
Issue/Introduction
After logging into the vSphere Client, the following symptoms occur:
- Certificate information is not displayed in the [Administration] - [Certificate Management] menu.
- Launching the virtual machine Web Console fails with the following message:
Couldn't establish a connection to the VM web console. - In the output of the service-control --status --all command, the vmware-vpxd-svcs service is confirmed to be in the Stopped state.
- The following message is logged in /var/log/vmware/vpxd-svcs/vpxd-svcs-runtime.log.stderr:
XXX XX, XXXX XX:XX:XX XX org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-10080"] OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000e8a00000, 93847552, 0) failed; error='Cannot allocate memory' (errno=12)
Environment
VMware vCenter Server 8.0
Cause
This issue occurs because the available memory at the OS level on the vCenter Server is depleted, preventing the vpxd-svcs service from allocating the memory required to operate, which causes the service to stop.
Resolution
Workaround:
Rebooting the vCenter Server virtual machine will free up (cleanup) the memory space, allowing the vpxd-svcs service and other services to start normally, which temporarily resolves the issue.
Resolution:
This issue may occur as a result of other services consuming excessive memory, causing the entire system to experience an out-of-memory condition.
As a typical example, the memory consumption of the vc-ws1a-broker service may increase due to the impact of a known issue. For details and workarounds, please refer to KB 396939.
Additional Information
Feedback
