Thanks for the reply Sunil! I thought it might be a network issue, but when I enabled debug then ran netcat against it I could connect. Firewall and SELinux are both disabled on all nodes.
I went ahead and reran the ethernet for both sets of NIC to ensure the old hub I was using was not a factor. Now everything runs through an enterprise-class switch. Stats from netstat and ethtool look normal; I did not view them prior to the changes. I also pulled down the latest updates from RHEL (did I mention these are RHEL5.4?), which included kernel-2.6.18-164.15.1.el5. Now the ocfs2_stackglue and ocfs2_dlmfs modules are failing to load. -Chris On Mon, Mar 22, 2010 at 4:52 PM, Sunil Mushran <sunil.mush...@oracle.com> wrote: > > The network connect is failing. Could be because of a firewall, > or bad ip address, some switch issue. > > Mount the volume on node 2. Then enable tracing and > tail messages file. > # debugfs.ocfs2 -l TCP allow > # tail -f /var/log/messages > > Then from node 4, ping node 2 using netcat. > # nc -z 192.168.1.2 7777 > > If it succeeds, then you should see: > Connection to 192.168.1.2 7777 port [tcp/cbt] succeeded! > > Additionally, you will see a message on node 2 "attempt to connect > from node...". > > If not, then look at your network setup. > > Remember to disable tracing on node 2. > #debugfs.ocfs2 -l TCP off > > Sunil _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
