Red Hat Bugzilla – Bug 429514
Administration Server Console : incorrect apache server error log parsing
Last modified: 2015-01-04 18:30:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20071127 Firefox/184.108.40.206
Description of problem:
The contents of the apache "error" log is incorrectly parsed and displayed in the java Administration console. The "Date" and "Time" fields are incorrect.
Version-Release number of selected component (if applicable):
Windows Console for Fedora DS 1.1
Steps to Reproduce:
1.Connect to the Administration Server console.
2.Choose the tab "Configuration" -> Logs -> Errors
3.Choose any line
4.Look at the parsed result (the bottom right panel)
The parsed results incorrectly show the contents of error log. For example, if the original apache error log line is
"[Mon Jan 21 10:21:28 2008] [notice] Apache/2.2 configured -- resuming normal operations"
the graphical parsed "Date" is "Mon Jan 21 10" and the "Time" is "21:28 2008"
For the example cited above the Date should be "21 Jan 2008" and the "Time" should be "10:21:28"
I think it is the general case for the console on Linux or any other OS, it is not specific to Windows or architecture.
Created attachment 292347 [details]
The screencap of the bug
The attachment shows the screencap with the described line and the bug.
Created attachment 326442 [details]
Created attachment 326443 [details]
Created attachment 326516 [details]
cvs commit log
Reviewed by: nkinder (Thanks!)
Fix Description: The error log date/time are together in one field. Just combine them into one column in the log viewer.
New screenshot - https://bugzilla.redhat.com/attachment.cgi?id=326443
Platforms tested: RHEL5
Flag Day: no
Doc impact: yes - will have to document the new log format
fix verified windows 2003 Enterprise IDM console (console framework 1.1.3) - DS 8.1 THEL 5
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.