<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font color="#000099">I have been plagued by errors of this kind
every so often, mainly because we are in a development phase and
we reboot our servers so frequently. If you start glusterd in
debug mode:<br>
<br>
sh$ glusterd --debug<br>
<br>
you can easily pinpoint exactly which volume/peer data is causing
the initialization failure for mgmt/glusterd.<br>
<br>
In addition, from my own experiences, two of the leading reasons
for failure include:<br>
a) Bad peer data if glusterd is somehow killed during an active
peer probe operation, and<br>
b) I have noticed that if glusterd needs to update info for
volume/brick (say "info" for volume testvol) in /var/lib/glusterd,
it first renames /var/lib/glusterd/vols/testvol/info to info.tmp,
and then creates a new file info, which is probably written into
_freshly_. If glusterd were to crash at this point, it would cause
failures in glusterd startup till this is manually resolved.
Usually, moving info.tmp into info works for me.<br>
<br>
Thanks,<br>
Anirban<br>
<br>
</font>
<div class="moz-cite-prefix">On Saturday 12 April 2014 08:45 AM, 吴保川
wrote:<br>
</div>
<blockquote
cite="mid:CANpG8_KjyhqtN+OJ8xFxSVqwMBM4JhKfzgHNpaL7fKOyOLwQ=w@mail.gmail.com"
type="cite">
<div dir="ltr">It is tcp.<br>
<div><br>
[root@server1 wbc]# gluster volume info<br>
<br>
Volume Name: gv_replica<br>
Type: Replicate<br>
Volume ID: 81014863-ee59-409b-8897-6485d411d14d<br>
Status: Started<br>
Number of Bricks: 1 x 2 = 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: 192.168.1.3:/home/wbc/vdir/gv_replica<br>
Brick2: 192.168.1.4:/home/wbc/vdir/gv_replica<br>
<br>
Volume Name: gv1<br>
Type: Distribute<br>
Volume ID: cfe2b8a0-284b-489d-a153-21182933f266<br>
Status: Started<br>
Number of Bricks: 2<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: 192.168.1.4:/home/wbc/vdir/gv1<br>
Brick2: 192.168.1.3:/home/wbc/vdir/gv1<br>
<br>
</div>
<div>Thanks,<br>
</div>
<div>Baochuan Wu<br>
</div>
<div>
<br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-04-12 10:11 GMT+08:00 Nagaprasad
Sathyanarayana <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:nsathyan@redhat.com" target="_blank">nsathyan@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div><span>If you run</span></div>
<div><span><br>
</span></div>
<div><span> </span><span
style="background-color:rgba(255,255,255,0)"># gluster
volume info</span></div>
<div><span><br>
</span></div>
<div><span>What is the value set for transport-type?</span></div>
<div><span><br>
</span></div>
<div><span>Thanks</span></div>
<div><span>Naga</span></div>
<div>
<div class="h5">
<div><br>
</div>
<div><br>
On 12-Apr-2014, at 7:33 am, 吴保川 <<a
moz-do-not-send="true"
href="mailto:wildpointercs@gmail.com"
target="_blank">wildpointercs@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>Thanks, Joe. I found one of my machine has
been assigned wrong IP address. This leads to
the error.<br>
</div>
Originally, I thought the following error is
critical:<br>
<span style="color:rgb(255,0,0)">[2014-04-11
18:12:03.433371] E
[rpc-transport.c:269:rpc_transport_load]
0-rpc-transport:
/usr/local/lib/glusterfs/3.4.3/rpc-transport/rdma.so:
cannot open shared object file: No such file
or directory</span></div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-04-12 5:34
GMT+08:00 Joe Julian <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:joe@julianfamily.org"
target="_blank">joe@julianfamily.org</a>></span>:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div>On 04/11/2014 11:18 AM, 吴保川 wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
[2014-04-11 18:12:05.165989] E
[glusterd-store.c:2663:glusterd_resolve_all_bricks]
0-glusterd: resolve brick failed in
restore<br>
</blockquote>
</div>
I'm pretty sure that means that one of the
bricks isn't resolved in your list of peers.<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
</div>
</div>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Gluster-users mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org"
target="_blank">Gluster-users@gluster.org</a></span><br>
<span><a moz-do-not-send="true"
href="http://supercolony.gluster.org/mailman/listinfo/gluster-users"
target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></span></div>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>