gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] Fwd: [Gluster-users] Command "/etc/init.d/glusterd s


From: Vijay Bellur
Subject: Re: [Gluster-devel] Fwd: [Gluster-users] Command "/etc/init.d/glusterd start" failed
Date: Sat, 12 Apr 2014 07:15:18 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0

On 04/11/2014 07:51 PM, Justin Clift wrote:
Kind of thinking this would be better as WARNING level instead of ERROR.

Any objections?  If not, I'll whip up a change for it for master on Monday.

This would be an error in the rpc layer if rdma is a legitimate transport type for volume/data or glusterd/management. This error is being seen since glusterd is instructed to listen on both tcp & rdma in glusterd.vol.

Maybe it is time to get our FAQ page current and add this in there?

Another change that seems necessary is the brick detail in this message:

"0-glusterd: resolve brick failed in restore"

Providing server name and path of the brick would make this log message a lot more meaningful.

-Vijay


+ Justin

Begin forwarded message:
*From: *吴保川 <address@hidden <mailto:address@hidden>>
*Subject: **Re: [Gluster-users] Command "/etc/init.d/glusterd start"
failed*
*Date: *12 April 2014 3:02:55 AM GMT+01:00
*To: *Joe Julian <address@hidden <mailto:address@hidden>>
*Cc: address@hidden <mailto:address@hidden>

Thanks, Joe. I found one of my machine has been assigned wrong IP
address. This leads to the error.
Originally, I thought the following error is critical:
[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


2014-04-12 5:34 GMT+08:00 Joe Julian <address@hidden
<mailto:address@hidden>>:

    On 04/11/2014 11:18 AM, 吴保川 wrote:

        [2014-04-11 18:12:05.165989] E
        [glusterd-store.c:2663:__glusterd_resolve_all_bricks]
        0-glusterd: resolve brick failed in restore

    I'm pretty sure that means that one of the bricks isn't resolved
    in your list of peers.


_______________________________________________
Gluster-users mailing list
address@hidden <mailto:address@hidden>
http://supercolony.gluster.org/mailman/listinfo/gluster-users

--
Open Source and Standards @ Red Hat

twitter.com/realjustinclift <http://twitter.com/realjustinclift>



_______________________________________________
Gluster-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/gluster-devel





reply via email to

[Prev in Thread] Current Thread [Next in Thread]