Two node Cluster

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

 



Hi,

I want to setup a two node cluster using cman. here are the steps I followed

=========================================
Cluster nodes: node1 & node2
=========================================

[root@node1 ~]# cman_tool status
Version: 6.1.0
Config Version: 5
Cluster Name: k7
Cluster Id: 269
Cluster Member: Yes
Cluster Generation: 48
Membership state: Cluster-Member
Nodes: 2
Expected votes: 1
Total votes: 2
Quorum: 1 
Active subsystems: 8
Flags: 2node Dirty
Ports Bound: 0 11 
Node name: node1
Node ID: 2
Multicast addresses: 239.192.1.14
Node addresses: 10.10.10.40

[root@node2 ~]# cman_tool status
Version: 6.1.0
Config Version: 5
Cluster Name: k7
Cluster Id: 269
Cluster Member: Yes
Cluster Generation: 48
Membership state: Cluster-Member
Nodes: 2
Expected votes: 1
Total votes: 2
Quorum: 1 
Active subsystems: 8
Flags: 2node Dirty
Ports Bound: 0 11 
Node name: node2
Node ID: 1
Multicast addresses: 239.192.1.14
Node addresses: 10.10.10.39

=========================================
Logical volumes on node node1
=========================================

/dev/vg1/lvol0 formatted as GFS

[root@node1 ~]#gfs_mkfs -p lock-dlm -t k7:CLVM0 -j 2 /dev/vg1/lvol0
[root@node1 ~]#mkfs -t gfs -p lock-dlm -t k7:CLVM0 -j 2 /dev/vg1/lvol0

=========================================
Procedures on node node1
=========================================

[root@node1 ~]# service cman start
Starting cluster:
   Enabling workaround for Xend bridged networking... done
   Loading modules... done
   Mounting configfs... done
   Starting ccsd... done
   Starting cman... done
   Starting daemons... done
   Starting fencing... done
                                                           [  OK  ]
[root@node1 ~]# service clvmd start
Starting clvmd:                                            [  OK  ]
Activating VGs:   1 logical volume(s) in volume group "vg1" now active


  Error locking on node node2: Command timed out
                                                           [  OK  ]
[root@node1 ~]# gnbd_serv -n
gnbd_serv: startup succeeded
[root@node1 ~]# gnbd_export -c -e gnbd1 -d /dev/vg1/lvol0
gnbd_export: created GNBD gnbd1 serving file /dev/vg1/lvol0
[root@node1 ~]# mount /dev/vg1/lvol0 /mnt/gfs_local/
[root@node1 ~]# cd /mnt/gfs_local/
[root@node1 gfs_local]# ls
fence.css   mantisbt-1.1.6.tar.gz     vkarmalicense.lic
JMeter.pdf  mysql-cheat-sheet-v1.pdf
[root@node1 gfs_local]#


=========================================
Procedures on node node2
=========================================
[root@node2 ~]# service cman start
Starting cluster:
   Enabling workaround for Xend bridged networking... done
   Loading modules... done
   Mounting configfs... done
   Starting ccsd... done
   Starting cman... done
   Starting daemons... done
   Starting fencing... done
                                                           [  OK  ]
[root@node2 ~]# service clvmd start
Starting clvmd:                                            [  OK  ]
[root@node2 ~]# gnbd_serv -n
gnbd_serv: startup succeeded
[root@node2 ~]# gnbd_import -i 10.10.10.40
[root@node2 ~]# mount /dev/gnbd/gnbd1 -o lockproto=lock_dlm /mnt/gfs_gnbd/
[root@node2 ~]# cd /mnt/gfs_gnbd/
[root@node2 gfs_gnbd]# ls
fence.css   mantisbt-1.1.6.tar.gz     vkarmalicense.lic
JMeter.pdf  mysql-cheat-sheet-v1.pdf

My /etc/cluster/cluster.conf is

<?xml version="1.0"?>
<cluster config_version="5" name="k7">
    <fence_daemon post_fail_delay="0" post_join_delay="3"/>
    <clusternodes>
        <clusternode name="node2" nodeid="1" votes="1">
            <fence/>
        </clusternode>
        <clusternode name="node1" nodeid="2" votes="1">
            <fence/>
        </clusternode>
    </clusternodes>
    <cman expected_votes="1" two_node="1"/>
    <fencedevices/>
    <rm>
        <failoverdomains>
            <failoverdomain name="node2" ordered="0" restricted="0">
                <failoverdomainnode name="node1" priority="1"/>
            </failoverdomain>
            <failoverdomain name="node1">
                <failoverdomainnode name="node2" priority="1"/>
            </failoverdomain>
        </failoverdomains>
        <resources/>
    </rm>
</cluster>

Why do the message "Error locking on node node2: Command timed out" pops up every time ?
Can a cluster be created without specifying fencing and all that stuff ? I just wanted to use GFS over a clustered environment.....

Sreejith K
K 7 - C O M P U T I N G
www.k7computing.com


--
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