Earlier today Virtual IEF posted a blog about not being able to access an ESX host, not by ssh, not by VIC and not even through vCenter. Evidently this is caused by the hardware monitoring agents (HP, Dell, etc) auto-detecting the management server and failing authentication. This causes cimservera to be spawned hundreds if not thousands of times thus causing so much CPU and Network traffic locally that it cannot respond within the thresholds for SSH, or VPX agents.
-
Unable to login through SSH to VMware ESX host
-
Unable to login on local Service console
-
HA errors.
root 6377 0.0 0.0 0 0 ? Z Sep24 0:00 [cimservera <defunct>]
root 6496 0.0 0.0 0 0 ? Z Sep24 0:00 [cimservera <defunct>]
Nov 17 18:29:34 blr-cpd-018 cimservera[506]: user “root” failed to authenticate
Nov 17 18:29:36 blr-cpd-018 cimservera[507]: user “root” failed to authenticate
Nov 17 18:29:39 blr-cpd-018 cimservera[508]: user “root” failed to authenticate
To resolve this issue you need to login to the console of the host and restart the pegasus service;
Created on January 6, 2009 by Rick Scherer
Posted under ESX 3.5 Tips, ESXi 3.5 Tips, Monitoring.
This blog has 3,702 views and one response.
Tags: cimservera, esx, pegasus, service console



