RE: Unable to mount GFS on RHEL 3 U6

["Treece, Britt" <Britt.Treece@xxxxxxxxxx>]

The nodename in nodes.ccs and cluster.ccs needs to match the hostname of each server.  I'm getting the impression from the output below that it does not.
 
>From the GFS 6.0 Admin guide...
http://www.redhat.com/docs/manuals/csgfs/admin-guide/s1-sf-nodes.html
 
Make sure that you specify Nodename as the Linux hostname and that the primary IP address of the node is associated with the hostname. Specifying NodeName other than the Linux hostname (for example the interface name) can cause unpredictable results - especially if the node is connected to multiple networks. To determine the hostname of a node, use the uname -n command on the node. To verify the IP address associated with the hostname, issue a ping command to the hostname.

________________________________

From: linux-cluster-bounces@xxxxxxxxxx on behalf of Magnus Andersen
Sent: Fri 3/17/2006 7:37 PM
To: linux clustering
Subject: Re:  Unable to mount GFS on RHEL 3 U6



This is what I have now.

cluster.css
[root@backup root]# cat cluster_cca/cluster.ccs
cluster {
        name = "cluster_cca"
        lock_gulm {
                servers = ["backuphb", "oradwhb", "gistest2hb"]
        }
}

nodes.css
[root@backup root]# cat cluster_cca/nodes.ccs
nodes {
        backuphb {
                ip_interfaces {
                        eth1 = "10.0.0.1"
                }
                fence {
                        man {
                                manual {
                                        ipaddr = "10.0.0.1"
                                }
                        }
                }
        }
        oradwhb {
                ip_interfaces {
                        eth4 = "10.0.0.2"
                }
                fence {
                        man {
                                manual {
                                        ipaddr = "10.0.0.2"
                                }
                        }
                }
        }
        gistest2hb {
                ip_interfaces {
                        eth0 = "10.0.0.3"
                }
                fence {
                        man {
                                manual {
                                        ipaddr = "10.0.0.3"
                                }
                        }
                }
        }
}

/etc/hosts
[root@backup root]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               backup localhost.localdomain localhost
10.0.0.1        backuphb backuphb.walkerassoc.com backuphb
10.0.0.2        oradwhb oradwhb.walkerassoc.com oradwhb
10.0.0.3        gistest2hb gistest2hb.walkerassoc.com gistest2hb

I ran this to update the cluster_cca pool after I modified the ccs files
ccs_tool -O create /root/cluster_cca /dev/pool/cluster_cca

Result out of my messages log ( this looks the same on all servers
once I start lock_gulmd )
Mar 17 20:24:17 gistest2 lock_gulmd[2383]: Starting lock_gulmd 6.0.2.27. (built
Jan 30 2006 15:28:54) Copyright (C) 2004 Red Hat, Inc.  All rights reserved.
Mar 17 20:24:17 gistest2 lock_gulmd[2383]: You are running in Fail-over mode.
Mar 17 20:24:17 gistest2 lock_gulmd[2383]: I am (gistest2) with ip (127.0.0.1)
Mar 17 20:24:17 gistest2 lock_gulmd[2383]: Forked core [2384].
Mar 17 20:24:18 gistest2 lock_gulmd_LT000[2385]: Not serving locks from this nod
e.
Mar 17 20:24:18 gistest2 lock_gulmd[2383]: Forked locktable [2385].
Mar 17 20:24:19 gistest2 lock_gulmd[2383]: Forked ltpx [2386].


Result from gulm_tool nodelist localhost
[root@backup root]# gulm_tool nodelist localhost
 Name: backup
  ip    = 127.0.0.1
  state = Logged in
  mode = Pending
  missed beats = 0
  last beat = 0
  delay avg = 0
  max delay = 0


Thanks,

--
Magnus Andersen
Systems Administrator / Oracle DBA
Walker & Associates, Inc.

--

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

<<winmail.dat>>

--

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