Bug 761883 (GLUSTER-151) - crash dump log should be in 'logviewer' friendly format
Summary: crash dump log should be in 'logviewer' friendly format
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-151
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-17 20:08 UTC by Amar Tumballi
Modified: 2013-12-19 00:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Amar Tumballi 2009-07-17 17:14:25 UTC 
So, it can be highlighted in webgui very prominently. Current log format of crash is very unfriendly to scripting mechanisms.
Comment 1 Amar Tumballi 2009-07-17 20:08:35 UTC 
so the time of the crash can be related to previous logs. The timing of the crash, relative to previous error/critical/warning logs is very important to debug the crash sometimes.
Comment 2 Anand Avati 2009-07-20 18:29:26 UTC 
PATCH: http://patches.gluster.com/patch/781 in master (added timestamp to crash dump log.)
Comment 3 Anand Avati 2009-07-20 18:29:37 UTC 
PATCH: http://patches.gluster.com/patch/771 in release-2.0 (added timestamp to crash dump log.)
Comment 4 Amar Tumballi 2009-11-11 18:03:01 UTC 
one patch sent to this.. more will be done as per the request of web ui or so.. currently closing the ticket.
Note You need to log in before you can comment on or make changes to this bug.