#50655 etime displayed has an order of magnitude 10 times smaller than it should be
Closed: wontfix by mreynolds. Opened by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1749236

Description of problem:
In the access log, the etime displayed seems to always be 10 times smaller than
it should be.
This error can systematically be seen
Version-Release number of selected component (if applicable):
seen on both 389-ds-base 1.3.10.1-1.el7 and 389-ds-base-1.3.9.1-8.el7
How reproducible:
Always
Steps to Reproduce:
1.perform an ldap operation
2.open the access log
3.for example :
[03/Sep/2019:04:52:09.428566825 -0400] conn=24 op=1 SRCH
base="dc=example,dc=com" scope=2 filter="(objectClass=*)" attrs=ALL
[03/Sep/2019:04:52:09.626959338 -0400] conn=24 op=1 RESULT err=0 tag=101
nentries=11161 etime=0.0198511652 notes=A
Actual results:
etime=0.0198511652
Expected results:
should be 0.198511652

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1749236

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

https://pagure.io/389-ds-base/pull-request/50656

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.3.10 (was: 0.0 NEEDS_TRIAGE)

Commit 225f4e17 relates to this ticket

f3f99c43d..3b47e3f90 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

2d398a243..13340add2 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

b89df9021..3fbff0870 389-ds-base-1.3.10 -> 389-ds-base-1.3.10

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3710

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata
Related Pull Requests