Hello All,

I had some traction on one of my VMware support cases. They found a memory issue with the hpHelper process/world, which was consuming almost all of the available memory in the init resource pool (with a defined maximum of 220MB). On a server that was acting up (ssh connections being dropped before you could enter credentials, plus the MKS console errors), stopping the hp-ams service instantly allowed the server to resume normal operations.

     /etc/init.d/hp-ams.sh stop

HP hasn't progressed on their side of the ticket yet, but for the time being, the workaround appears to be to stop the hp-ams service.

Cheers

-Joshua