LHC : IpmHandle::recv _read_errno is 5
Strange Warning in engine_A log at system startup...
Background: HP-UX 11i with VCS 5.0.10.2, 3-node cluster.
Node 0 in the cluster was rebooted this morning. All processes started normally,...
Forum Discussion
VOS seems to indicate this is not a major problem:
https://vos.symantec.com/ecls/umi/V-16-1-10638
It also mentions: "A possible action is to determine the reason why the client has suddenly gone down."
Off the top of my head, the only thing I can think is that had was busy/still starting so hastatus wasn't able to return cleanly? Even if that was the case, it doesn't explain why there would be hundreds of messages though (ie: implies hastatus being run hundreds of times in that window?)
https://vos.symantec.com/ecls/umi/V-16-1-10638
It also mentions: "A possible action is to determine the reason why the client has suddenly gone down."
Off the top of my head, the only thing I can think is that had was busy/still starting so hastatus wasn't able to return cleanly? Even if that was the case, it doesn't explain why there would be hundreds of messages though (ie: implies hastatus being run hundreds of times in that window?)
