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 after lkstart, shared memory is not cleared (for example, !lkstop flag is not cleared) which causes various issues in 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

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment