Starting sfcbd-watchdog using the "/etc/init.d/sfcbd-watchdog start" command failed.
The following log output appears in /var/log/syslog.log when the command was executed:
YYYY-MM-DDT23:59:27.155Z sfcbd-init[#########]: Request to start sfcbd-watchdog, pid #########YYYY-MM-DDT23:59:27.172Z sfcbd-init[#########]: starting sfcbdYYYY-MM-DDT23:59:27.437Z sfcbd-init[#########]: Waiting for sfcb to start up.YYYY-MM-DDT23:59:27.446Z sfcbd[#########]: Missing routine GetSystemUUID in vmwSupport.so, using default uuidYYYY-MM-DDT23:59:27.446Z sfcbd[#########]: cimRPmodule: get rp info for pid=#########YYYY-MM-DDT23:59:27.446Z sfcbd[#########]: cimRPmodule: fetch VSI_NODE_sched_groups_groupName failed Not foundYYYY-MM-DDT23:59:27.446Z sfcbd[#########]: cimRPmodule: failed to get resource pool name and id by pid #########YYYY-MM-DDT23:59:27.446Z sfcbd[#########]: Not running in correct resource pool, exiting.
VMware vSphere ESXi 7.0.x
VMware vSphere ESXi 8.0.x
This is an rare occurrence. An id is assigned when sfcbd-watchdog starts, but there was an issue with how this id was handled.
This issue has been fixed in ESXi 8.0U3.
The workaround is to reboot the ESXi host.