[Bugs] [Bug 1447523] Glusterd segmentation fault in ' _Unwind_Backtrace' while running peer probe

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1447523

Gaurav Yadav <gyadav at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gyadav at redhat.com
              Flags|                            |needinfo?(ben at apcera.com)



--- Comment #7 from Gaurav Yadav <gyadav at redhat.com> ---
I try recreating the issue locally with 2 ubuntu servers, and I was not able to
recreate the issue locally.

Repro steps
1. Install gluster on Ubuntu 14.04
2. sudo gluster peer probe 192.168.122.159

I am not seeing any issue while peer probing...command getting executed
succesfully.


I have few queries regarding the info you have provided..

1. Problematic peer entry:
2. cat /var/lib/glusterd/peers/ip-10-0-50-25.us-west-1.compute.internal 
3. uuid=00000000-0000-0000-0000-000000000000
4. state=0
5. hostname1=ip-10-0-50-25.us-west-1.compute.internal 

Line 2 shows file name as "ip-10-0-50-25.us-west-1.compute.internal" inside
peers directory, however glusterd generates file and named as per uuid.  In
your case filename is  similar to hostname which is wrong.

Could you please let me know whether it is glusterd generated file or manually
some changes have been done.?


Answer to your query..
There's another issue which may be related. I noticed that glusterd.info was
not self-populating. As a workaround I issue 'gluster pool list' which triggers
glusterd to generate and store a UUID:

glusterd.info file gets generated whenever we do probe and create volume for
the first time. It contains UUID of local node which is used by glusterd for
validation purpose.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.