Re: Freeze with cluster-2.03.11

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 27, 2009 at 06:19:50PM +0100, Kadlecsik Jozsef wrote:
> Hi,
> 
> Combing through the log files I found the following:
> 
> Mar 27 13:31:56 lxserv0 fenced[3833]: web1-gfs not a cluster member after 0 sec post_fail_delay
> Mar 27 13:31:56 lxserv0 fenced[3833]: fencing node "web1-gfs"
> Mar 27 13:31:56 lxserv0 fenced[3833]: can't get node number for node e1??e1?? 
> Mar 27 13:31:56 lxserv0 fenced[3833]: fence "web1-gfs" success
> 
> The line saying "can't get node number for node e1??e1??" might be 
> innocent, but looks suspicious. Why fenced could not get the victim name?

I've not seen that before, and I can't explain either how cman_get_node()
could have failed or why it printed a garbage string.  It's a non-essential
bit of code, so that error should not be related to your problem.

Dave

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux