ocfs2 at Xen / Problems

Happy New Year to All,

Peter,

Possibly you have some kind of network problem between
domU's. 
>> at 192.168.0.102:7777 has been idle for 10 seconds,
shutting it down.

Best run ocfs2 cluster from dom0 and make domU's as member
servers. See my white paper on this http://www.novell.com/coolsolutions/feature/18287.html
.

Regards,
Arun

>>> On 1/1/2007 at 1:44 PM, Peter Selzner
<peter_selznerweb.de> wrote:
> Hallo,
> 
> i have big trouble to build a ocfs2 cluster in a xen
environment.
> Here the basic data:
> 
> dom0 - SLES10 i586 - neweset updates
> domU(vm1-priv/1 ocfs2 cluster node) - SLES10 i586 -
neweset updates
> domU(vm2-priv/2 ocfs2 cluster node) - SLES10 i586 -
neweset updates
> 
> vm1-priv:~ # cat /etc/ocfs2/cluster.conf
> node:
>         ip_port = 7777
>         ip_address = 192.168.0.101
>         number = 0
>         name = vm1-priv
>         cluster = ocfs2
> 
> node:
>         ip_port = 7777
>         ip_address = 192.168.0.102
>         number = 1
>         name = vm2-priv
>         cluster = ocfs2
> 
> cluster:
>         node_count = 2
>         name = ocfs2
> 
> vm1-priv:~ # cat /proc/cmdline
>  TERM=xterm elevator=deadline
> 
> vm1-priv:~ # cat
/sys/kernel/config/cluster/ocfs2/heartbeat/dead_threshold
> 61
> 
> vm1-priv:~ # rco2cb status
> Module "configfs": Loaded
> Filesystem "configfs": Mounted
> Module "ocfs2_nodemanager": Loaded
> Module "ocfs2_dlm": Loaded
> Module "ocfs2_dlmfs": Loaded
> Filesystem "ocfs2_dlmfs": Mounted
> Checking O2CB cluster ocfs2: Online
> Checking O2CB heartbeat: Active
> 
> vm1-priv:~ # rcocfs2 status
> Configured OCFS2 mountpoints:  /u02/oradata/orcl
> Active OCFS2 mountpoints:  /u02/oradata/orcl
> 
> In a 1 node (vm1-priv) environment everythink is O.K..
> But when i try to mount the ocfs2 Partion on the second
node (vm2-priv)
> i get the following error message:
> 
> vm1-priv:~ # tail -f /var/log/messages
> Dec 31 10:10:14 vm1-priv kernel: o2net: accepted
connection from node
> vm2-priv (num 1) at 192.168.0.102:7777
> Dec 31 10:10:18 vm1-priv kernel: ocfs2_dlm: Node 1
joins domain
> EF66C393A04F4AD1BC3858E85D6DFF39
> Dec 31 10:10:18 vm1-priv kernel: ocfs2_dlm: Nodes in
domain
> ("EF66C393A04F4AD1BC3858E85D6DFF39"): 0 1
> Dec 31 10:10:24 vm1-priv kernel: o2net: connection to
node vm2-priv (num 1)
> at 192.168.0.102:7777 has been idle for 10 seconds,
shutting it down.
> Dec 31 10:10:24 vm1-priv kernel:
(0,0):o2net_idle_timer:1314 here are some
> times that might help debug the situation: (tmr
1167556214.138502 now
> 1167556224.136880 dr 1167556219.138509 adv
> 1167556219.138533:1167556219.138534 func (93c366ef:1)
> 1167556218.160081:1167556218.160083)
> Dec 31 10:10:24 vm1-priv kernel: o2net: no longer
connected to node
> vm2-priv (num 1) at 192.168.0.102:7777
> 
> and when i try to cd /u02/oradata/orcl on vm2-priv i
get:
> 
> vm2-priv:~ # cd /u02/oradata/Kernel panic - not
syncing: ocfs2 is very
> sorry to be fencing this system by panicing
> 
> Is it passibly e Xen-Problem?
> Thanks for each suggestion!
> 
> Peter





-- 
To unsubscribe, email: suse-oracle-unsubscribesuse.com
For additional commands, email: suse-oracle-helpsuse.com
Please see http://www.suse.com/oracl
e/ before posting