Host Profile application, creation, or compliance check fails: Error extracting indication configuration: (0, 'Socket error: [Errno 111] Connection refused')

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• You encounter an error when:
  
  
  • Creating a host profile
  • Applying a host profile
  • Checking host profile compliance
    
    
• You see the error:
  
  Error extracting indication configuration: (0, 'Socket error: [Errno 111] Connection refused')
  
  
• You encounter intermittent host profile compliance errors when using AutoDeploy
• The host syslog.log located in /var/log contains entries similar to:
  
  
  YYYY-MM-DDT<time>Z YYYY-MM-DD <time> Host Profiles[12089]: ERROR: Exception while checking host compliance. Exception: (LocalizedException) {</time></time>
  dynamicType = <unset>,
  dynamicProperty = (vmodl.DynamicProperty) [],
  msg = <unset>,
  faultCause = <unset>,
  faultMessage = (vmodl.LocalizableMessage) [
  (LocalizableMessageWithPath) {
  dynamicType = <unset>,
  dynamicProperty = (vmodl.DynamicProperty) [],
  key = 'com.vmware.profile.Profile.CimXmlIndicationsProfile.ExtractionException',
  arg = (vmodl.KeyAnyValue) [
  (vmodl.KeyAnyValue) {
  dynamicType = <unset>,
  dynamicProperty = (vmodl.DynamicProperty) [],
  key = 'ErrArg0',
  value = "(0, 'Socket error: [Errno 111] Connection refused')"
  }
  ],
  message = u'Error extracting indication configuration: "(0, \'Socket error: [Errno 111] Connection refused\')"'
  }
  ]
  }^@

Environment

VMware vCenter Server 5.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 5.5.x

Cause

This issue occurs when host profiles cannot configure CIM Indications due to the sfcbd service not being started on the host. The sfcbd service can be down for multiple reasons. It is important to note that during a normal boot it is expected that the sfcbd service is restarted multiple times.

Resolution

This is a known issue affecting VMware vCenter Server 5.x.

This issue is resolved in ESXi 5.1 Update 3, available at VMware Downloads. For more information see the VMware ESXi 5.1 Update 3 Release Notes.

This issue is resolved in ESXi 6.5 available at VMware Downloads.

To work around this issue, perform these steps:

When you experience compliance errors on booting a host using AutoDeploy

If CIM Indicators are a part of the host profile, it is currently expected behavior that host profiles fail with the error as starting and stopping of the sfcbd service is a part of the boot process for ESXi.

To work around this issue, remove the CIM Indication Subscriptions from the host profile.

To remove the CIM Indication Subscriptions from the host profile:

1. Select Home within the vSphere Client.
2. Select Host Profiles.
3. Right click on the host profile that the host is attached to.
4. Select Enable/Disable Profile Configuration.
5. Remove the check mark next to CIM Indication Subscriptions.
6. Click OK to save the changes to the host profile.

When you experience errors when creating, applying, or checking compliance of a host profile

Restart the CIM service to work around this issue:

1. Log in to vCenter Server as an administrator from the vSphere Client.
2. Select the ESXi host you want to create or update a host profile from the inventory.
3. Click the Configuration tab.
4. Click the Security Profile link.
5. Click Properties.
6. Click CIM Server > Options.
7. Select Start and Stop with host if it is not set this way by default.
8. Click Restart.
9. Click Start > OK.

Additional Information

For the latest compatibility list of third party CIM modules, see the VMware Compatibility Guide.

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box ホスト プロファイルの適用、作成、またはコンプライアンス チェックに次のエラーで失敗する：インディケーションの構成の抽出中にエラーが発生しました: (0, 'ソケット エラー: [Errno 111] 接続が拒否されました') （Error extracting indication configuration: (0, 'Socket error: [Errno 111] Connection refused')）
主机配置文件应用、创建或合规性检查失败：提取指示配置时出错: (0，“套接字错误: [Errno 111] 连接被拒绝”) (Error extracting indication configuration: (0, 'Socket error: [Errno 111] Connection refused'))

Impact/Risks: