You mentioned that you ran the command on the problematic host but I am assuming you ran it on vCenter Server Appliance as this service is not available at ESXi host level. This is a service at vCenter Server level.
Looks like there is some issue with the "vmware-vsan-health" service in vCenter Server which is causing this issue. Can you please try stopping it and starting it back using service-control as shown below:
Stopping "vmware-vsan-health" service with service-control command:
# service-control --stop vmware-vsan-health
Perform stop operation. vmon_profile=None, svc_names=['vmware-vsan-health'], include_coreossvcs=False, include_leafossvcs=False
Successfully stopped service vsan-health
Starting "vmware-vsan-health" service with service-control command:
# service-control --start vmware-vsan-health
Perform start operation. vmon_profile=None, svc_names=['vmware-vsan-health'], include_coreossvcs=False, include_leafossvcs=False
2016-12-14T20:17:50.216Z Service vsan-health state STOPPED
Successfully started service vsan-health
_________________________
Cheers!
-Shivam