[Sheepdog] nodes not joing the cluster automaticaly

[Sonali Jadhav]

Hi Kazutaka,

I tried to reinstall sheepdog. And in new sheep.log file it seems ok except one line,

" read_epoch(1928) failed to read epoch 0"

But still they are not in cluster. :(

I have attached new sheep.log files of both kvmboxes. Please have a look. Why both node are not joining cluster automatically?

Thanks,
Sonali Jadhav. 


-----Original Message-----
From: sheepdog-bounces at lists.wpkg.org [mailto:sheepdog-bounces at lists.wpkg.org] On Behalf Of Sonali Jadhav
Sent: Wednesday, March 09, 2011 6:13 PM
To: sheepdog at lists.wpkg.org
Subject: Re: [Sheepdog] nodes not joing the cluster automaticaly

HI Kazutaka,

While starting sheepdog I ran command for xattr attribute. And it also applied that attribute to disk. See here,

[root at kvmbox1 ~]# mount
/dev/cciss/c0d0p2 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/cciss/c0d0p1 on /boot type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw)
/dev/cciss/c0d0p5 on /store type ext3 (rw,user_xattr) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) none on /var/lib/xenstored type tmpfs (rw)

NOTE : /store is our sheepdog disk.
We are getting same output for kvmbox2.
Now I am attaching corosync logs of both kvmboxes too.


Thanks,
Sonali Jadhav

-----Original Message-----
From: MORITA Kazutaka [mailto:morita.kazutaka at lab.ntt.co.jp] 
Sent: Wednesday, March 09, 2011 12:01 AM
To: Sonali Jadhav
Cc: sheepdog at lists.wpkg.org
Subject: Re: [Sheepdog] nodes not joing the cluster automaticaly

At Tue, 8 Mar 2011 14:02:48 +0100,
Sonali Jadhav wrote:
> We have set up sheepdog cluster for 2 KVM boxes. I have successfully installed sheepdog on both boxes. But when I try to retrieve cluster info, both boxes are showing only itself information.
> 
> On KVMbox1 its showing as,
> 
> [root at kvmbox1 ~]# collie cluster info
> running
> Ctime                Epoch Nodes
> 2011-03-08 13:04:41      1 [192.168.1.162:7000]
> [root at kvmbox1 ~]# collie node list
>   Idx        Node id (FNV-1a) - Host:Port
> ------------------------------------------------
> * 0          db28f1360c4eded6 -192.168.1.162:7000
> 
> 
> And on  KVMbox2 its showing as,
> 
> [root at kvmbox2 ~]# collie cluster info
> running
> Ctime                Epoch Nodes
> 2011-03-08 13:05:28      1 [192.168.1.163:7000]
> [root at kvmbox2 ~]# collie node list
>   Idx        Node id (FNV-1a) - Host:Port
> ------------------------------------------------
> * 0          363e4ccce90dc0c3 - 192.168.1.163:7000
> 
> I want to know why both of them are not getting added in cluster automatically? Also my corosync.conf files are configured correctly. I have configured them same as shown on http://wiki.qemu.org/Features/Sheepdog/Corosync_Config .
>  For more info I have attached sheep.log files of both boxes.
> 

It seems that your local file system doesn't support an extended attribute.  In case of ext3, you need to add 'user_xattr' to the mount options.

Anyway, we should print a more user friendly log message, sorry.


Thanks,

Kazutaka


-------------- next part --------------
A non-text attachment was scrubbed...
Name: sheep.log.kvmbox1.rar
Type: application/octet-stream
Size: 937 bytes
Desc: sheep.log.kvmbox1.rar
URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20110311/e77270cb/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sheep.log.kvmbox2.rar
Type: application/octet-stream
Size: 972 bytes
Desc: sheep.log.kvmbox2.rar
URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20110311/e77270cb/attachment-0007.obj>