[Bugs] [Bug 1447523] Glusterd segmentation fault in ' _Unwind_Backtrace' while running peer probe
bugzilla at redhat.com
bugzilla at redhat.com
Fri May 5 10:40:21 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1447523
Ben Werthmann <ben at apcera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(ben at apcera.com) |
|needinfo?(ben at apcera.com) |
--- Comment #11 from Ben Werthmann <ben at apcera.com> ---
(In reply to Gaurav Yadav from comment #10)
>
>
> content of cat /var/lib/glusterd/peers/10.0.50.215 shows uuid as
> 00000000-0000-0000-0000-000000000000, mean it is not generating properly. I
> believe uuid is not getting generated properly in your setup.
>
> Can you check if the following steps work:
> 1. Remove the faulty peer file from /var/lib/glusterd/peers/
> 2. On the host that is to be probed, i.e. 10.0.50.25, clean everything in
> /var/lib/glusterd/*
> 3. Restart glusterd services
> 4. Peer probe 10.0.50.25 again
> 5. check the content of /var/lib/glusterd/glusterd.info
> 6. check whether file inside /var/lib/glusterd/peers is generatd with the
> UUID.
$ ssh 10.0.50.128
$ cat /var/lib/glusterd/peers/10.0.50.125
cat: /var/lib/glusterd/peers/10.0.50.125: Permission denied
ubuntu at bwerthmann5-dc0936f3:~$ sudo cat /var/lib/glusterd/peers/10.0.50.125
uuid=00000000-0000-0000-0000-000000000000
state=0
hostname1=10.0.50.125
$ start glusterfs-server
glusterfs-server start/running, process 14453
$ logout
$ ssh 10.0.50.125
$ sudo ls -l /var/lib/glusterd/peers/
total 0
$ stop glusterfs-server
glusterfs-server stop/waiting
$ rm -rf /var/lib/glusterd/*
$ start glusterfs-server
glusterfs-server start/running, process 15170
$ logout
$ ssh 10.0.50.128
$ sudo gluster --log-level=TRACE peer probe 10.0.50.125
Connection failed. Please check if gluster daemon is operational.
$ cat /var/lib/glusterd/peers/10.0.50.125
uuid=00000000-0000-0000-0000-000000000000
state=0
hostname1=10.0.50.125
$ logout
/var/lib/glusterd/glusterd.info does not exist on either node. (I removed the
'peer list' command from the setup which used to generate this).
>
>
> If still issue is reproducing, please share the all logs from both the nodes.
I'll post them shortly.
>
> Please share your setup details also, so that I can also test in the same
> environment in order to reproduce the issue.
I'll attach a "apport" bundle which should have all of the info you need.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list