healthd error: Could not kill <pid> : 3 logged on syslog

Products

• VMware vSphere ESXi

Issue/Introduction

• syslog server detected error message similar with
  

  YYYY-MM-DD    hh:mm:ss.xxx　(error)　HostName　<163>YYYY-MM-DDThh:mm:ss.xxxZ　HostName healthd[2099068]:　[Originator@6876　sub＝PluginLauncher]　Could　not　kill　<pid> :　3)
  
  

• /var/run/log/healthd logged similar with 
  

  yyyy-mm-ddThh:mm:ss.xxxZ In(166) healthd[2099055]: [Originator@6876 sub=HealthdHandler] Report Path: /var/lib/vmware/osdata/healthd/vmw.vSANStatus
  yyyy-mm-ddThh:mm:ss.xxxZ Er(163) healthd[2099068]: [Originator@6876 sub=PluginLauncher] Could not kill <pid> : 3
  yyyy-mm-ddThh:mm:ss.xxxZ In(166) healthd[2099068]: [Originator@6876 sub=PluginLauncher] 1 subgroups present in group xxx
  

  
  
  
  
• This is not a continuous error; it is a one-time or intermittent occurrence.

Environment

VMware vSphere ESXi

Cause

This error logged due to a race condition because process <PID> exited before the kill.

Resolution

This is non-fatal and safely ignore.