Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1749236

Summary:	etime displayed has an order of magnitude 10 times smaller than it should be
Product:	Red Hat Enterprise Linux 7	Reporter:	sgouvern
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	medium	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	high
Version:	7.7	CC:	lkrispen, mreynolds, msauton, nkinder, spichugi, tbordaz, tmihinto, vashirov
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	All
Whiteboard:
Fixed In Version:	389-ds-base-1.3.10.1-3.el7	Doc Type:	Bug Fix
Doc Text:	.Directory Server now logs the correct `etime` value in the access log Previously, Directory Server incorrectly formatted the `etime` field in the `/var/log/dirsrv/slapd-<instance_name>/access` log file. As a consequence, the time value in nanoseconds was 10 times lower than the actual value. This update fixes the problem. As a result, Directory Server now logs the correct nanosecond value in the `etime` field.	Story Points:	---
Clone Of:
Clones:	1801701 (view as bug list)		Environment:
Last Closed:	2020-03-31 19:46:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1801701

Description sgouvern 2019-09-05 08:03:05 UTC

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


Additional info:

Comment 2 mreynolds 2019-10-16 20:52:16 UTC

Upstream ticket:
https://pagure.io/389-ds-base/issue/50655

Comment 3 mreynolds 2019-10-16 23:36:29 UTC

Fixed upstream

Comment 12 errata-xmlrpc 2020-03-31 19:46:15 UTC

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.

https://access.redhat.com/errata/RHBA-2020:1064