[Bugs] [Bug 1787463] Glusterd process is periodically crashing with a segmentation fault
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jan 6 11:07:47 UTC 2020
https://bugzilla.redhat.com/show_bug.cgi?id=1787463
Sanju <srakonde at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |srakonde at redhat.com
Doc Type|--- |If docs needed, set a value
Flags| |needinfo?(awingerter at opente
| |xt.com)
--- Comment #1 from Sanju <srakonde at redhat.com> ---
I have tried to look at the backtrace from the cores. Even though I installed
release-6.1 I don't find any debug symbols.
It looks like:
Core was generated by `/usr/sbin/glusterd -p /var/run/glusterd.pid --log-level
INFO'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f442f3244a7 in ?? ()
[Current thread is 1 (LWP 21520)]
(gdb) bt
#0 0x00007f442f3244a7 in ?? ()
#1 0x4cce3ca800000001 in ?? ()
#2 0x0000000000018b1e in ?? ()
#3 0x00007f442f41faa8 in ?? ()
#4 0x00007f4400000000 in ?? ()
#5 0x00007f440c0174f0 in ?? ()
#6 0x00007f442f7b1b20 in ?? ()
#7 0x00007f441c4030c0 in ?? ()
#8 0x00007f442f7b1b90 in ?? ()
#9 0x00007f441c4030dc in ?? ()
#10 0x0000000000000007 in ?? ()
#11 0x0000562c75ecd4e0 in ?? ()
#12 0x00007f442f324db7 in ?? ()
#13 0x00007f4400000000 in ?? ()
#14 0x0000000000000000 in ?? ()
Can you please share output of "t a a bt" output?
Thanks,
Sanju
--
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