Bug 918711
| Summary: | [RFE] logconv.pl should handle microsecond timing | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Nathan Kinder <nkinder> |
| Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Sankar Ramalingam <sramling> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | CC: | jgalipea, mreynolds, nhosoi, srkrishn |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.3.1.2-1.el7 | Doc Type: | Enhancement |
| Doc Text: |
Cause: etimes were incorrectly processed by logconv.pl if microsecond access logging was being used.
Consequence: The reported statistics that used "etime" could be incorrect.
Change: The script properly reads and processes microsecond etimes.
Result: The generated report has correct results.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-13 12:32:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Nathan Kinder
2013-03-06 18:16:17 UTC
moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata). When the errata is created, the bugs should be automatically moved back to ON_QA. Hi Mark, request you to please add more details for this bugzilla. QE would like know what needs to be tested. (In reply to Sankar Ramalingam from comment #3) > Hi Mark, request you to please add more details for this bugzilla. QE would > like know what needs to be tested. The access log has long supported the option of using microsecond resolution for it's timestamps. You simply need to enable microsecond logging as described in the documentation: https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Configuration_Command_and_File_Reference/logs-reference.html#Access_Log_Content-Access_Logging_Levels As mentioned in the initial bug description, you should then make sure that logconv.pl is able to work against access logs that use microsecond resolution. hi, i added the following testcase for the microsecond timing using the following steps 1. added microsecond timing by changing the modifying the config file using ldapmodify command and changing the nsslapd-accesslog-level to 131328 2.added 10000 entries. 3.used a ldapsearch to get information from all 10000 entries. 4.using the logconv tool tried to get the etime information from them with the logconv -t option. 5.the output obtained from the temp logs is as follows ----- Top 20 Most Frequent etimes ----- 8461 etime=0 268 etime=1 1 etime=2 ----- Top 20 Longest etimes ----- etime=2 1 etime=1 268 etime=0 8461 is it possible to mention what should be tested? (In reply to srkrishn from comment #5) > hi, > i added the following testcase for the microsecond timing using the > following steps > 1. added microsecond timing by changing the modifying the config file using > ldapmodify command and changing the nsslapd-accesslog-level to 131328 > 2.added 10000 entries. > 3.used a ldapsearch to get information from all 10000 entries. > 4.using the logconv tool tried to get the etime information from them with > the logconv -t option. > 5.the output obtained from the temp logs is as follows > ----- Top 20 Most Frequent etimes ----- > > 8461 etime=0 > 268 etime=1 > 1 etime=2 > > > ----- Top 20 Longest etimes ----- > > etime=2 1 > etime=1 268 > etime=0 8461 > > is it possible to mention what should be tested? That is the correct log level, can you verify the access log actually has microsecond etimes? Maybe there was log buffering, and you ran the script too soon. Waiting 30 seconds will allow the logging to be flushed to disk. I just ran a test and logconv.pl is working for me: ----- Top 20 Most Frequent etimes ----- 2 etime=0.001000 1 etime=0.000000 1 etime=0.002000 1 etime=0.004000 ----- Top 20 Longest etimes ----- etime=0.004000 1 etime=0.002000 1 etime=0.001000 2 etime=0.000000 1 hi,
i added the following testcase and verified the microsecond timing issue which has been resolved in the logconv.pl script using the following steps
> 1. added microsecond timing by changing the modifying the config file using
> ldapmodify command and changing the nsslapd-accesslog-level to 131328
> 2.added 10000 entries.
> 3.used a ldapsearch to get information from all 10000 entries.
> 4.using the logconv tool tried to get the etime information from them with
> the logconv -t option.
microsecond timing has been successfully tracked by the logconv tool time1 =
2 etime=0.000000
1 etime=0.008000
1 etime=9.148000
1 etime=0.001000
1 etime=0.230000
etime=9.148000 1
etime=0.230000 1
etime=0.008000 1
etime=0.001000 1
etime=0.000000 2
[root@hp-dl380pgen8-02-vm-1 logfile]#
Based on Sriram's comment #7, marking the bug as Verified. Build tested - 389-ds-base-1.3.1.6-15 Test cases automated in ./logfile/logconv.sh This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |