RE: Freeze with cluster-2.03.11

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

 



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?

Best regards,
Jozsef
--
E-mail : kadlec@xxxxxxxxxxxx, kadlec@xxxxxxxxxxxxxxxxx
PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address: KFKI Research Institute for Particle and Nuclear Physics
         H-1525 Budapest 114, POB. 49, Hungary
--
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