AnsweredAssumed Answered

What is CIM_ERR_Failed caused by and/or what is the fix?

Question asked by rtirak on Aug 21, 2018
Latest reply on Aug 21, 2018 by Gene_Howard

We are having lots of performance issues with out Hitach probe. It takes about an hour for data collection to complete a cycle, and when you make a change in the Infastrecture Manager to the probe like turning on a metric the probe locks up and goes back into pending state for long periods of time. We are using the probe with 2GB to 4GB of RAM also as a note. 

 

I am seeing this in the log:

 

Aug 21 08:01:54:319 [CommandPoolExecutor_0_42, hitachi] null
Aug 21 08:01:54:319 [CommandPoolExecutor_0_42, hitachi] WBEMException: CIM_ERR_FAILED
Aug 21 08:01:54:319 [CommandPoolExecutor_0_42, hitachi] stdout: Exception in dumping HITACHI_CIMXMLObjectManagerAdapter WBEMException: CIM_ERR_FAILED
Aug 21 08:01:54:319 [CommandPoolExecutor_0_42, hitachi] stdout: 235839642
Aug 21 08:01:54:319 [CommandPoolExecutor_0_42, hitachi] Class dumping: HITACHI_CIMXMLObjectManagerAdapter end differnce in nanoseconds 235839642
Aug 21 08:01:54:319 [CommandPoolExecutor_0_42, hitachi] Class dumping: HITACHI_CIMXMLSObjectManagerAdapter started
Aug 21 08:01:54:319 [CommandPoolExecutor_0_42, hitachi] NameSpace : root/hitachi/smis Class Name HITACHI_CIMXMLSObjectManagerAdapter Properties [Ljava.lang.String;@314d5aad Wbem Client org.sblim.cimclient.internal.wbem.WBEMClientCIMXML@5d3d150a
Aug 21 08:01:55:585 [CommandPoolExecutor_0_42, hitachi] null
Aug 21 08:01:55:585 [CommandPoolExecutor_0_42, hitachi] WBEMException: CIM_ERR_FAILED
Aug 21 08:01:55:585 [CommandPoolExecutor_0_42, hitachi] stdout: Exception in dumping HITACHI_CIMXMLSObjectManagerAdapter WBEMException: CIM_ERR_FAILED
Aug 21 08:01:55:585 [CommandPoolExecutor_0_42, hitachi] stdout: 1269554481
Aug 21 08:01:55:585 [CommandPoolExecutor_0_42, hitachi] Class dumping: HITACHI_CIMXMLSObjectManagerAdapter end differnce in nanoseconds 1269554481
Aug 21 08:01:55:585 [CommandPoolExecutor_0_42, hitachi] Class dumping: HITACHI_StorageManagementSoftware started
Aug 21 08:01:55:585 [CommandPoolExecutor_0_42, hitachi] NameSpace : root/hitachi/smis Class Name HITACHI_StorageManagementSoftware Properties [Ljava.lang.String;@72d045f8 Wbem Client org.sblim.cimclient.internal.wbem.WBEMClientCIMXML@5d3d150a
Aug 21 08:01:55:944 [attach_socket, hitachi] cbGetStatus (hds-g1500-20458.erieinsurance.com)
Aug 21 08:01:55:944 [attach_socket, hitachi] getStatus() for get_status callback called: resource = 'hds-g1500-20458'
Aug 21 08:01:55:944 [attach_socket, hitachi] getStatus() for get_status callback returning 'OK'

 

 

 

 

Any ideas what that means or how to fix it? Or has anyone ran into this before?

Outcomes