Description of problem: glusterd related core observed while probing a node which is already in cluster. Version-Release number of selected component (if applicable): glusterfs-3.7.5-8 How reproducible: Steps to Reproduce: 1.While running automated cases related to snapshots observed core related to glusterd. 2.This happened while probing a node which is already a part of the cluster. Actual results: glusterd related core observed Expected results: Additional info:
sos reports are at http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1288085
Hi shashank, core file is missing from the sos report. could you check it again and attach core file somewhere so can we can analyse this issue. we need core file to analyse this issue.
core file is placed at http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/1288085/core/core.4750
Hi Shashank, Its very rare to reproduce this issue. glusterd crashed because at the time of sending response to CLI some application have corrupted dictionary data. by looking into backtrace using gdb we didn't found out much information regarding this which application have corrupted dictionary and freed its one of the member which is trying to free again.
Lowering both priority and severity as the crash is not reproducible.
Shashank, Since this bug is not reproducible and we haven't heard any such core in recent times closing this bug. Feel free to reopen if you hit it again.