By the way, this less than useful error message has been reworked for 3.4.
On 07/10/2013 05:54 PM, Joe Julian wrote:
That error means (and if it means this, then why doesn't it just say
this???) that the hostname provided could not be converted to its
uuid. That probably means that the hostname assigned to the brick is
not in the peer list.
The hostname of the brick has to be a case insensitive match for the
peer hostname as displayed in "peer probe" (function uses
"strncasecmp") or the brick hostname has to be able to resolve to an
ip address which then must resolve to a hostname that matches the peer
hostname.
On 07/10/2013 05:18 PM, Matthew Sacks wrote:
Here is the startup sequence: https://gist.github.com/msacks/5971418
On Wed, Jul 10, 2013 at 3:02 PM, Matthew Sacks <[email protected]
<mailto:[email protected]>> wrote:
Hello,
I have a gluster cluster which keeps complaining about
ops.c:842:glusterd_op_stage_start_volume] 0-: Unable to resolve
brick gluster1:/export/brick1/sdb1
here is the full output : https://gist.github.com/msacks/5970713
Not sure how this happened or how to fix it.
All my peers are connected.
I tried to stop and start the volume but that didn't work.
Cheers for your help.
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
