cancel
Showing results for 
Search instead for 
Did you mean: 

cluster_lockd

cluster_lockd

Can anybody tell me why after rebooting one member of a 5 member cluster, did the cluster_lockd keep on relocating itself? From the original member that was rebooted and then back to another member then a whlie later back to the original member and so on... It kept on doing this and slowed down the entire cluster. We then rebooted the entire cluster and now the problem has gone away. Surely, you do not have to reboot the entire cluster evertime you have aproblem like this?
2 REPLIES
Ralf Puchner
Honored Contributor

Re: cluster_lockd

maybe time to have a look within the event logs. caa is a very good friend of the eventlogs...

It is also time to check proper cluster configuration depending on the event leading to the caa failover.
Help() { FirstReadManual(urgently); Go_to_it;; }
Roberto Romani
Occasional Visitor

Re: cluster_lockd

You may want to check a few things when this happens again or part of your cluster monitoring.

#caa_stat -t(check status)
#caa_stat -p cluster_lockd ( for more detail).
#sysman -menu ->trucluster specific -> CAA ->cluster_lockd

after that a sys_check -escalate or the EVM logs could be useful.

Regards
Roberto