[Linux-cluster] DLM problem

[Richard Allen]

On 03/18/2011 12:50 AM, Fabio M. Di Nitto wrote:
> On 03/18/2011 12:47 AM, C.D. wrote:
>>
>> On Thu, Mar 17, 2011 at 10:29 PM, Richard Allen <ra at ra.is
>> <mailto:ra at ra.is>> wrote:
>>
>>     I have a simple test cluster up and running (RHEL 6 HA) on three
>>     vmware guests.  Each vmware guest has 3 vnic's.
>>
>>     After booting a node, I often get a dead rgmanager:
>>
>>     [root at syseng1-vm ~]# service rgmanager status
>>     rgmanager dead but pid file exists
>>
>>     Cluster is otherwise OK
>>
>>     [root at syseng1-vm ~]# clustat
>>     Cluster Status for RHEL6Test @ Thu Mar 17 16:10:38 2011
>>     Member Status: Quorate
>>
>>      Member Name                                               ID   Status
>>      ------ ----                                               ---- ------
>>      syseng1-vm                               1 Online, Local
>>      syseng2-vm                               2 Online
>>      syseng3-vm                               3 Online
>>
>>     There is a service running on node2 but clustat has no info on that.
>>
>>
>>
>>     [root at syseng1-vm ~]# cman_tool status
>>     Version: 6.2.0
>>     Config Version: 9
>>     Cluster Name: RHEL6Test
>>     Cluster Id: 36258
>>     Cluster Member: Yes
>>     Cluster Generation: 88
>>     Membership state: Cluster-Member
>>     Nodes: 3
>>     Expected votes: 3
>>     Total votes: 3
>>     Node votes: 1
>>     Quorum: 2
>>     Active subsystems: 1
>>     Flags:
>>     Ports Bound: 0
>>     Node name: syseng1-[CENSORED]
>>     Node ID: 1
>>     Multicast addresses: 239.192.141.48
>>     Node addresses: 10.10.16.11
>>
>>
>>     The syslog has some info:
>>
>>     Mar 17 15:47:55 syseng1-vm rgmanager[2463]: Quorum formed
>>     Mar 17 15:47:55 syseng1-vm kernel: dlm: no local IP address has been set
>>     Mar 17 15:47:55 syseng1-vm kernel: dlm: cannot start dlm lowcomms -107
> Make sure the VMs don't traverse any kind of NAT and that node names (as
> specified in cluster.conf) resolves to the correct ip addresses. Also
> cross check your iptables setup to allow traffic between nodes. DLM uses
> TCP vs userland that uses multicast.
>
> Fabio
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster

iptables ans selinux is disabled on my test setup.   All hosts are properly
set up in DNS and resolve fine in both directions and each node has a fully
populated /etc/hosts just to be on the safe side.


-- 
Rikki.         --  RHCE, RHCX, HP-UX Certified Administrator.
               --  Solaris 7 Certified Systems and Network Administrator.
Bell Labs Unix --  Reach out and grep someone.
Those who do not understand Unix are condemned to reinvent it, poorly.