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
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
Check out https://bugzilla.redhat.com/show_bug.cgi?id=911290
It seems similar so hopefully it'll help...
Todd
On Wed, Jul 10, 2013 at 05:18:46PM -0700, Matthew Sacks wrote:
> Here is the startup sequence: https://gist.github.com/msacks/5971418
>
>
> On Wed, Jul 10, 2013 at 3:02 PM, Matthew Sac
Here is the startup sequence: https://gist.github.com/msacks/5971418
On Wed, Jul 10, 2013 at 3:02 PM, Matthew Sacks 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
>
>
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 connecte
