Description of problem: Rarely reproducible issues leaving only backtraces in gluster log files need a tool to resolve the backtraces to symbols and line numbers Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/18144 (extras/devel-tools: script to resolve backtraces) posted (#1) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/18144 (extras/devel-tools: script to resolve backtraces) posted (#2) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/18144 (extras/devel-tools: script to resolve backtraces) posted (#3) for review on master by Milind Changire (mchangir)
REVIEW: https://review.gluster.org/18144 (extras/devel-tools: script to resolve backtraces) posted (#5) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/18144 (extras/devel-tools: script to resolve backtraces) posted (#6) for review on master by Amar Tumballi
COMMIT: https://review.gluster.org/18144 committed in master by "Amar Tumballi" <amarts> with a commit message- extras/devel-tools: script to resolve backtraces print-backtrace.sh script to resolve backtraces Change-Id: I24688ae5160cc706d9f4794521d17290bef6765b BUG: 1486532 Signed-off-by: Milind Changire <mchangir>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.0, please open a new bug report. glusterfs-6.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/