Bug 694296 - report_Logger does not append last report event in event_log section of report
Summary: report_Logger does not append last report event in event_log section of report
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-06 21:22 UTC by Steve Tyler
Modified: 2015-02-01 22:53 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-04-08 10:50:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Steve Tyler 2011-04-06 21:22:08 UTC
Description of problem:
When the report_Logger saves a report to a file, the last event is not saved in the event_log section.
This event is, however, saved in the ccpp*/event_log file.
It is also displayed in the "Reporting" window (without the timestamp).

For example /tmp/abrt6.log, is missing the line:
2011-04-06-12:16:24> The report was stored to /tmp/abrt6.log
which is present in 
ccpp-2011-04-05-04:07:08-1789/event_log.

Snippet from /tmp/abrt6.log:
...
event_log
-----
2011-04-05-14:43:43> (exited with 0)
2011-04-05-14:43:44> Analyzing coredump '/home/joeblow/.abrt/spool/ccpp-2011-04-05-04:07:08-1789/coredump'
...
2011-04-05-14:50:30> Backtrace is generated and saved, 40216 bytes
2011-04-05-14:50:30> (exited with 0)
2011-04-05-14:50:39> The report was appended to /tmp/abrt1.log
2011-04-05-14:52:24> The report was appended to /tmp/abrt2.log
2011-04-05-14:56:35> The report was appended to /tmp/abrt3.log
2011-04-05-15:01:40> The report was stored to /tmp/abrt4.log
2011-04-05-15:33:48> The report was stored to /tmp/abrt4.log
2011-04-05-15:36:35> The report was stored to /tmp/abrt4.log
2011-04-05-15:37:44> The report was stored to /tmp/abrt4.log
2011-04-05-15:39:12> The report was stored to /tmp/abrt4.log
2011-04-05-15:42:17> The report was stored to /tmp/abrt4.log
2011-04-06-12:11:16> The report was stored to /tmp/abrt4.log
2011-04-06-12:14:29> The report was stored to /tmp/abrt5.log

smaps
-----
...


$ tail -3 ccpp-2011-04-05-04:07:08-1789/event_log
2011-04-06-12:11:16> The report was stored to /tmp/abrt4.log
2011-04-06-12:14:29> The report was stored to /tmp/abrt5.log
2011-04-06-12:16:24> The report was stored to /tmp/abrt6.log

Version-Release number of selected component (if applicable):
abrt-2.0.0-4.fc15.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Configure the report_Logger to overwrite a log file /tmp/abrt1.log.
   (That is, set Append to "no". Overwriting is for simplicity.)
2. Save a report.
3. Configure the report_Logger to write to /tmp/abrt2.log.
4. Save the same report again.
  
Actual results:
The "report was stored" event for /tmp/abrt2.log is not recorded in /tmp/abrt2.log.

Expected results:
The "report was stored" event is recorded in /tmp/abrt2.log.

Additional info:
This appears to be the only place in the report itself where the time of report generation would be recorded in a user-readable format.

Comment 1 Jiri Moskovcak 2011-04-08 10:50:54 UTC
This is just a confusing name of the reporter you used, so I try to explain:

event_log is a file where we store the std output from all applications run during some event (analyzing, reporting) the log file created by report_Logger is a place where it stores the report and thus the line "report was stored" doesn't belong there. From ABRT's view the /tmp/abrtX.log is the same as bugzilla so that's why it stores there only the "report data". I know that now you can see event_log even in bugzilla, but that's just another bug in the bugzilla reporter.

Comment 2 Steve Tyler 2011-04-08 13:27:17 UTC
(In reply to comment #1)
> This is just a confusing name of the reporter you used, so I try to explain:
> 
> event_log is a file where we store the std output from all applications run
> during some event (analyzing, reporting) the log file created by report_Logger
> is a place where it stores the report and thus the line "report was stored"
> doesn't belong there. From ABRT's view the /tmp/abrtX.log is the same as
> bugzilla so that's why it stores there only the "report data". I know that now
> you can see event_log even in bugzilla, but that's just another bug in the
> bugzilla reporter.

So the event_log should not be included in the bug report?
(I will open a new bug, but would like to confirm this.)

Comment 3 Jiri Moskovcak 2011-04-08 14:21:27 UTC
> So the event_log should not be included in the bug report?
> (I will open a new bug, but would like to confirm this.)

Exactly.


Note You need to log in before you can comment on or make changes to this bug.