Lack of fencing in my case (without GFS) is only a problem if the
failing NIC fades in and out. The larger problem during real operation
is the lack of service recovery. I plugged the public nic back in and
it was rejected as a node and then the service was relocated (late).
scottb
Scott Becker wrote:
Lon Hohberger wrote:
On Mon, 2007-11-26 at 14:36 -0800, Scott Becker wrote:
openais[9498]: [CLM ] CLM CONFIGURATION CHANGE
openais[9498]: [CLM ] New Configuration:
kernel: dlm: closing connection to node 3
fenced[9568]: 205.234.65.133 not a cluster member after 0 sec
post_fail_delay
openais[9498]: [CLM ] r(0) ip(205.234.65.132)
openais[9498]: [CLM ] Members Left:
openais[9498]: [CLM ] r(0) ip(205.234.65.133)
openais[9498]: [CLM ] Members Joined:
openais[9498]: [CLM ] CLM CONFIGURATION CHANGE
openais[9498]: [CLM ] New Configuration:
openais[9498]: [CLM ] r(0) ip(205.234.65.132)
openais[9498]: [CLM ] Members Left:
openais[9498]: [CLM ] Members Joined:
openais[9498]: [SYNC ] This node is within the primary component and
will provide service.
openais[9498]: [TOTEM] entering OPERATIONAL state.
openais[9498]: [CLM ] got nodejoin message 205.234.65.132
openais[9498]: [CPG ] got joinlist message from node 2
Did it even try to run the fence_apc agent? It should have done
*something* - it didn't even look like it tried to fence.
-- Lon
No sign of an attempt. How do I turn up the verbosity of fenced? I'll
repeat the test. The only mention I can find is -D but I don't know how
I can use that. I'll browse the source and see if I can learn anything.
I'm using 2.0.73.
thanks
scottb
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
|
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
