| Summary: | logconv.pl -m time calculation is wrong | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Rich Megginson <rmeggins> |
| Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
| Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | jgalipea, nhosoi, nkinder, rmeggins, srkrishn |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.2.11.15-34.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 07:51:12 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1061410 | ||
|
Description
Rich Megginson
2013-09-27 22:01:07 UTC
Request you to add steps to verify bugzilla (In reply to Sankar Ramalingam from comment #3) > Request you to add steps to verify bugzilla Use logconv.pl with the -m or the -M option - verify that the timestamp field in the -m/-M report matches the access log timestamp. The timestamp field is the first column in the -m/-M report. It is in unix time_t format. You can convert to a "human readable" format like this: $ date --date='@1400000000' Tue May 13 10:53:20 MDT 2014 Replace 1400000000 with the timestamp field from the -m/-M report. this bug has been verified: logconv.pl -M /tmp/access /var/log/dirsrv/slapd-hp-ms-01-c04/access.20140717-022403 18/Jul/2014:01:28:00 -0400,1405661280,434,0,217,0,0, [root@hp-ms-01-c04 tmp]# [root@hp-ms-01-c04 tmp]# date --date='@1405661280' Fri Jul 18 01:28:00 EDT 2014 this was tested on the build : 1.2.11.15.38-289-ds-base Marking the bug as Verified, based on the previous comment from Sriram, Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1385.html |