<style type="text/css">
<!--
@page { margin: 0.79in }
P { margin-bottom: 0.08in }
A:link { so-language: zxx }
-->
</style>
<p style="margin-bottom: 0in">Dear Sheepdog developers,</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in">First of all, we would like to thank
you for the support.</p>
<p style="margin-bottom: 0in">We have tried to install the sheepdog
version that you provided for us. However, we were not successful
with the installation due to the fact that we could not obtain the
result of the command collie node list (e.g., something like
connection failure). Thus, we adopted the sheepdog version available
at <a href="https://github.com/collie/sheepdog">https://github.com/collie/sheepdog</a>
(collie-sheepdog-v0.2.3-11-g3410623.tar.gz). Considering this
version, we were successful to see all machines in the cluster
(adopting the command collie node list). However, the command collie
cluster format –copies=2 seems to be not working as it is supposed
to (e.g., Invalid error code) . Besides that, we tried the command
collie node info
, and the result was:</p>
<p style="margin-bottom: 0in">Id Size Used Use%
</p>
<p style="margin-bottom: 0in">cannot get information from any nodes</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in">Another command “collie cluster
info
” seems also to be not working very well (we could not see the
creation time and epoch nodes)</p>
<p style="margin-bottom: 0in">Cluster status: running
</p>
<p style="margin-bottom: 0in">
</p>
<p style="margin-bottom: 0in">Creation time Epoch Nodes
</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in">In addition, although the command
“qemu-img create sheepdog:Callou 4G” seemed to work, once it has
executed the node is out of the cluster. Besides that, we executed
the command “collie vdi list”
, and we got:</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in"> name id size used
shared creation time vdi id
</p>
<p style="margin-bottom: 0in">------------------------------------------------------------------
<br>failed
to read a inode header 15507205, 0, 81</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in">Thus, we are not sure if the vm image
was created. In order to put the node again into the cluster, we had
to restart the corosync and sheepdog as well as to delete an create
again the sheepdog storage dir.</p>
<p style="margin-bottom: 0in">Then, we executed the command “collie
vdi list”
and got:</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in"> name id size used
shared creation time vdi id
</p>
<p style="margin-bottom: 0in">------------------------------------------------------------------
</p>
<p style="margin-bottom: 0in">Floating point exception</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in">We expect that those information
provided above may be useful to find out what is the problem that
might be happening in my sheepdog environment. Do you have any
suggestion?
</p>
<p style="margin-bottom: 0in"><br>
</p>
<p style="margin-bottom: 0in">Best regards,</p>
<p style="margin-bottom: 0in">Gustavo Callou / Rubens Matos</p>
<p style="margin-bottom: 0in"><br>
</p>
<br><br><div class="gmail_quote">On Mon, Jun 20, 2011 at 9:36 AM, MORITA Kazutaka <span dir="ltr"><<a href="mailto:morita.kazutaka@lab.ntt.co.jp">morita.kazutaka@lab.ntt.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
At Mon, 20 Jun 2011 00:12:59 -0300,<br>
<div><div></div><div class="h5">Gustavo Callou wrote:<br>
> Dear Sheepdog developers,<br>
><br>
> I’m a Brazilian PhD student from Federal University of Pernambuco and I'm<br>
> trying to configure the Sheepdog in order to test its features. I have 4 PCs<br>
> available to do such test, in which Ubuntu 10.04 64bits version are<br>
> installed. I'm adopting the Sheepdog package<br>
> “sheepdog_0.2.2-0ubuntu1_amd64.deb“, downloaded at Ubuntu repositories.<br>
> However, I’m not sure about the configuration due to the fact that once I<br>
> have installed the environment, machines sometimes are able to see each<br>
> other and sometimes not. What I mean is when I execute the command “sudo<br>
> collie node list”, there are machines that see that there is only one node<br>
> in the cluster (i.e., the host sees itself), others can see 2 nodes, and<br>
> other sometimes see 3 nodes. Another interesting fact is that, when I have<br>
> restarted the corosync and the sheepdog in all machines, such seen<br>
> configuration changes.<br>
><br>
> In a nutshell, I have attached in this message the logs from 3 machines<br>
> (e.g., named sheep1, sheep2, sheep3). Besides, I attached the corosync.conf<br>
> in which I have tried to configure the bindnetaddr with an ip like this<br>
> 172.20.10.0 as well as adopting the machine ip such as 172.20.10.116.<br>
><br>
> Please, let me know as soon as possible if there is something that is not<br>
> correctly configurated at the corosync.conf or any other issues that you may<br>
> detect through the nodes logs.<br>
<br>
</div></div>Your corosync.conf looks correct.<br>
<br>
>From sheep[1-3].log, your Sheepdog directories contains wrong<br>
information about node membership histories. I'm not sure why it<br>
happened, but it would work for you to clean the store directories and<br>
run 'collie cluster format' again.<br>
<br>
I highly recommend to upgrade Sheepdog to version 0.2.3 or use the<br>
latest development code:<br>
<a href="https://github.com/collie/sheepdog" target="_blank">https://github.com/collie/sheepdog</a><br>
<br>
It includes many important bug fixes.<br>
<br>
Thanks,<br>
<font color="#888888"><br>
Kazutaka<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Phd Candidate in Computer Science<br>Federal University of Pernambuco<br><a href="http://www.modcs.org">http://www.modcs.org</a><br><br>