[Ocfs2-users] o2net_connect_expired:1637 ERROR

[Raheel Akhtar]

 Hi,

 Then why I am getting this error, according to error message it 
 couldn't connect to itself (node 2)? And it was working fine, since 
 yesterday I start getting this error message. Should I increase heartbeat
to 61 instead of 31?

 Thanks
 Raheel

-----Original Message-----
From: Sunil Mushran [mailto:sunil.mushran at oracle.com] 
Sent: Wednesday, June 24, 2009 2:54 PM
To: Raheel Akhtar
Cc: ocfs2-users at oss.oracle.com
Subject: Re: [Ocfs2-users] o2net_connect_expired:1637 ERROR

Not sure why you think it is trying to connect to itself. o2net
connects to other nodes only.

Raheel Akhtar wrote:
>
> Hi,
>
> I have OCFS2 Cluster of 5 nodes running on RHEL 5.2 (kernel version 
> 2.6.18-128.1.10.el5). I am getting error like
>
> Jun 24 09:26:54 alf2 kernel: (2095,0):o2net_connect_expired:1637 
> ERROR: no connection established with node 2 after 30.0 seco
>
> nds, giving up and returning errors.
>
> Jun 24 09:27:54 alf2 last message repeated 2 times
>
> Jun 24 09:29:24 alf2 last message repeated 3 times
>
> Jun 24 09:30:54 alf2 last message repeated 3 times
>
> Jun 24 09:32:24 alf2 last message repeated 3 times
>
> Even local firewall (iptables) is stopped, just wondering why node2 
> (alf2) can't connect to itself.
>
> 'Service o2cb status' shows
>
> Driver for "configfs": Loaded
>
> Filesystem "configfs": Mounted
>
> Driver for "ocfs2_dlmfs": Loaded
>
> Filesystem "ocfs2_dlmfs": Mounted
>
> Checking O2CB cluster ocfs2: Online
>
> Heartbeat dead threshold = 31
>
> Network idle timeout: 30000
>
> Network keepalive delay: 2000
>
> Network reconnect delay: 2000
>
> Checking O2CB heartbeat: Active
>
> Can someone please help to fix this problem. I can these errors on 
> other nodes also, nodes can't connect to itself.
>