CIM service needs to be restarted on esxi 5-1

[Mathew Kohnen]

We have several proliant servers of different models and generations runing esxi 5-1

On each server running esxi 5-1 the CIM stops reporting the hardwarware status of the server and we cannot open a properties page.

Restarting the CIM service will fix this but does not last more than a day or 2.

Is there a resolution for this or has anyone come up with a work around.

Thank you

Below is a sample from the syslo.log

2014-05-07T21:10:44Z sfcb-CIMXML-Processor[27305428]: Timeout (or other socket error) sending request to provider
2014-05-07T21:11:14Z sfcb-CIMXML-Processor[27313564]: Timeout (or other socket error) sending request to provider
2014-05-07T21:11:14Z sfcb-hhrc[10022]: Error getting provider context from provider manager: 11 (10022)
2014-05-07T21:11:14Z sfcb-ProviderManager[9966]: SendMsg sending to 72 9966-32 Broken pipe
2014-05-07T21:11:14Z sfcb-hhrc[10022]: HHRCWrapperProviderEnumInstances: unsupported class CIM_SoftwareIdentity
2014-05-07T21:11:15Z sfcb-CIMXML-Processor[27280971]:
*** 1822 Error accepting SSL connection -- exiting
2014-05-07T21:11:44Z sfcb-CIMXML-Processor[27305428]: Timeout (or other socket error) sending request to provider
2014-05-07T21:12:14Z sfcb-CIMXML-Processor[27313564]: Timeout (or other socket error) sending request to provider
2014-05-07T21:12:44Z sfcb-ProviderManager[9966]: SendMsg sending to 72 9966-32 Broken pipe
2014-05-07T21:12:44Z sfcb-CIMXML-Processor[27305548]: Timeout (or other socket error) sending request to provider
2014-05-07T21:12:44Z sfcb-pycim[10028]: Error getting provider context from provider manager: 11 (10028)
2014-05-07T21:12:55Z sfcb-CIMXML-Processor[27321962]:
***

[AMRIT RANJAN]

what is the version you are using of offline bundle?
can you post following outcome from command: esxcli software vib list | grep hp

[Aaron Eccles]

Did you ever get this issue resolved with the CIM service needing to be restarted?  I have not been able to find a solution...

Thanks

[Jagadish_P]

Hello,

This seems to be a known bug issue and there is a patch released to resolve the problem.

PR943946 info:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2041612

Patch Download link:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2041632

Thanks,

[Jagadish_P]

Check out my post and it might help in resolving the issue you are facing