[Gluster-users] Unable to peer probe after upgrade to 3.3

[Dan Bretherton]

Hello Rahul,

I followed the procedure you suggested and now I can do "gluster peer 
probe" again.  I didn't do the "gluster volume reset" because I had 
already done that after upgrading to version 3.3, but your procedure 
worked fine without it.  Thanks very much for your help.

Regards
-Dan.

On 08/03/2012 12:09 PM, Rahul Hinduja wrote:
> Hi Dan,
>
> I had a setup where I manually edited the username to "rahul" and password to "hinduja". Volume reset was done after editing the file. Looks like it does not matter weather what format the creds are (UUID in this case).
>
> Please try this out.
>
> Copied the gluster-users list.
>
> Thanks,
> Rahul Hinduja
>
> ----- Original Message -----
> From: "Dan Bretherton"<d.a.bretherton at reading.ac.uk>
> To: "Rahul Hinduja"<rhinduja at redhat.com>
> Cc: vs at redhat.com, "Sudhir Dharanendraiah"<sdharane at redhat.com>
> Sent: Friday, August 3, 2012 3:50:21 PM
> Subject: Re: [Gluster-users] Unable to peer probe after upgrade to 3.3
>
> Hello Rahul,
> Thanks for looking into this for me.  You are correct; my volume files
> don't have username and password entries.
>
> I created a test volume on a machine with 3.3 freshly installed and the
> username and password entries look like this.
>
> volume-id=d018547d-ceeb-4a55-b5fa-2237deaf572f
> username=5b1c5055-98b5-4b5b-a448-29eb7ac878b3
>
> Please can you tell me how to generate these long strings.  Are they
> randomly generated and can they be the same for every volume?  Can I
> copy and paste the above into my existing volume files?
>
> By the way I notice that your reply wasn't copied to the gluster-users
> list.  Was that deliberate?  I think it would be useful to update
> everyone on the list with the solution to my problem, so please let me
> know if you would be happy for me to CC gluster-users next time.
>
> Regards,
> Dan Bretherton
>