[Ocfs2-users] O2CB heartbeat not active on 2nd node

[McKinley, Reid]

Yes, I had tcpdump running in separate sessions on both servers.

The port is correct.  Here is the cluster.conf.

node:
        ip_port = 7777
        ip_address = 192.168.0.218
        number = 0
        name = nyclx1
        cluster = tiaa

node:
        ip_port = 7777
        ip_address = 192.168.0.217
        number = 1
        name = nyclx2
        cluster = tiaa

cluster:
        node_count = 2
        name = tiaa

-----Original Message-----
From: Sunil Mushran [mailto:sunil.mushran at oracle.com] 
Sent: Wednesday, June 03, 2009 5:35 PM
To: McKinley, Reid
Cc: ocfs2-users at oss.oracle.com
Subject: Re: [Ocfs2-users] O2CB heartbeat not active on 2nd node

Did you have tcpdump running on a terminal when you attempted
the mount on another terminal? Is the interface and port correct?

It is one thing to not see the packets on the nyclx2. But what
confuses me is that there is no traffic on nyclx1 too.


McKinley, Reid wrote:
> We can bring up the ocfs2 cluster on 1 of 2 nodes only.  So, it
appears
> that it's not specific to only one specific node.  Right now we have
the
> ocfs2 heartbeat operational on node2 (node1 in the cluster.conf).
>
> Here are the results of the mount and tcpdump.
>
> [root at nyclx1 ~]# mount -t ocfs2 /dev/mapper/mpath1 /oragrid
> mount.ocfs2: Transport endpoint is not connected while mounting
> /dev/mapper/mpath1 on /oragrid. Check 'dmesg' for more information on
> this error.
> [root at nyclx1 ~]#
>
> [root at nyclx2 ~]#  tcpdump -i eth1 -s 2500 -ttt 'port 7777'
> tcpdump: verbose output suppressed, use -v or -vv for full protocol
> decode
> listening on eth1, link-type EN10MB (Ethernet), capture size 2500
bytes
>
> 0 packets captured
> 0 packets received by filter
> 0 packets dropped by kernel
>
> [root at nyclx2 ~]# /etc/init.d/o2cb status
> Driver for "configfs": Loaded
> Filesystem "configfs": Mounted
> Driver for "ocfs2_dlmfs": Loaded
> Filesystem "ocfs2_dlmfs": Mounted
> Checking O2CB cluster tiaa: Online
> Heartbeat dead threshold = 31
>   Network idle timeout: 30000
>   Network keepalive delay: 2000
>   Network reconnect delay: 2000
> Checking O2CB heartbeat: Active
>
> [root at nyclx1 ~]# tcpdump -i eth1 -s 2500 -ttt 'port 7777'
> tcpdump: verbose output suppressed, use -v or -vv for full protocol
> decode
> listening on eth1, link-type EN10MB (Ethernet), capture size 2500
bytes
>
> 0 packets captured
> 0 packets received by filter
> 0 packets dropped by kernel
>
> [root at nyclx1 ~]# /etc/init.d/o2cb status
> Driver for "configfs": Loaded
> Filesystem "configfs": Mounted
> Driver for "ocfs2_dlmfs": Loaded
> Filesystem "ocfs2_dlmfs": Mounted
> Checking O2CB cluster tiaa: Online
> Heartbeat dead threshold = 31
>   Network idle timeout: 30000
>   Network keepalive delay: 2000
>   Network reconnect delay: 2000
> Checking O2CB heartbeat: Not active
>
>
> -----Original Message-----
> From: Sunil Mushran [mailto:sunil.mushran at oracle.com] 
> Sent: Wednesday, June 03, 2009 4:55 PM
> To: McKinley, Reid
> Cc: ocfs2-users at oss.oracle.com
> Subject: Re: [Ocfs2-users] O2CB heartbeat not active on 2nd node
>
> Do:
> $ tcpdump -i ethX -s 2500 -ttt 'port 7777'
>
> on both nodes. Replace ethX with the appropriate interface.
> Then issue the mount command on node 1. Do you see the traffic
> on node 0?
>
> McKinley, Reid wrote:
>   
>> No, iptables is shutdown and disabled.  No firewalls.
>>
>> [root at nyclx1 ~]# service iptables status
>> Firewall is stopped.
>>
>> -----Original Message-----
>> From: Sunil Mushran [mailto:sunil.mushran at oracle.com] 
>> Sent: Wednesday, June 03, 2009 12:57 PM
>> To: McKinley, Reid
>> Cc: ocfs2-users at oss.oracle.com
>> Subject: Re: [Ocfs2-users] O2CB heartbeat not active on 2nd node
>>
>> The connect requests are not getting through. Do you
>> have any firewalls setup? Is iptables running? If so, either
>> shut it down or allow traffic on the o2cb port.
>>     
>
>
************************************************************************
********************
> This message, including any attachments, contains confidential
information intended 
> for a specific individual and purpose, and is protected by law. If you
are not the intended 
> recipient, please contact the sender immediately by reply e-mail and
destroy all copies.
> You are hereby notified that any disclosure, copying, or distribution
of this message, or
> the taking of any action based on it, is strictly prohibited.
>
> TIAA-CREF
>
************************************************************************
********************
>
>   


********************************************************************************************
This message, including any attachments, contains confidential information intended 
for a specific individual and purpose, and is protected by law. If you are not the intended 
recipient, please contact the sender immediately by reply e-mail and destroy all copies.
You are hereby notified that any disclosure, copying, or distribution of this message, or
the taking of any action based on it, is strictly prohibited.

TIAA-CREF
********************************************************************************************