Shared memory is not cleared if lbhcd continues to be used with lkstop -f

Symptom

Currently lbhcd is running even after lkstop -f because it needs to respond to the Load Balancer Health probe. However, if it is used as is after lkstart, shared memory is not cleared (for example, !lkstop flag is not cleared) and it causes various issues in different parts of LifeKeeper.

Workaround

Kill lbhcd just before lkstart. For example, start a command prompt with administrator privileges and execute the following command.

wmic process where "commandline like '%lbhcd%'" delete