Description of problem:
Gluster daemon on individual servers crash, with crashdump in log file. This has started happening since last upgrade from 3.6.x to 3.7.4.
Version-Release number of selected component (if applicable):
Incident occurs on random hosts approximately once every week.
Volume Name: Volume-xxxx
Volume ID: b19cc9e2-071e-4f68-95e3-7c3e26d263a8
Number of Bricks: 2 x 3 = 6
Crash Dump at the time of incident in logs:
signal received: 6
time of crash:
package-string: glusterfs 3.7.4
The information which you have given is insufficient. Could you provide us bt (back trace) of your core file and could you attach glusterd logs. do you remember what steps was you following which cause glusterd crash.
Unfortunately I am not able to provide any further details related to this particular incident. However I can provide logs and other information related to incidents that happened on later dates. Or I can close this issue and raise another one that is specific to that incident.
(In reply to Ali Abbas from comment #2)
> Hi Soumya,
> Unfortunately I am not able to provide any further details related to this
> particular incident. However I can provide logs and other information
> related to incidents that happened on later dates. Or I can close this issue
> and raise another one that is specific to that incident.
if the issue is related to glusterd crash then you can attach core_file/glusterd logs/command line history logs. if the issue is something else then you can close this bug and raise new bug specific to that issue.
Since we haven't received other information asked for, I am closing this bug, feel free to reopen if the issue persists.