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 1657635 - Random number generate for internal access logs without the sequence.
Summary: Random number generate for internal access logs without the sequence.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: 8.0
Assignee: mreynolds
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On: 1683259
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-10 08:08 UTC by Amita Sharma
Modified: 2020-11-14 09:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-31 17:14:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
internal server access logs (39.99 KB, text/plain)
2018-12-10 08:08 UTC, Amita Sharma 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 3139 0 None None None 2020-09-13 22:17:10 UTC

Description Amita Sharma 2018-12-10 08:08:59 UTC 
Created attachment 1512958 [details]
internal server access logs

Description of problem:
Random number generate for internal access logs without the sequence.

Version-Release number of selected component (if applicable):
389-ds-base-1.4.0.19-2.module+el8+1+36e60e1d.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure access log level to 260 (4 + 256)
dsconf -D "cn=Directory Manager" slapd-localhost config replace nsslapd-accesslog-level=260

2. Restart the server
dsctl slapd-localhost restart

3. Check the access logs - It has random number generated for the access log, look for "conn=Internal(0) op=0(174)(1)"

[10/Dec/2018:07:58:23.236168537 +0000] conn=1 op=0 RESULT err=0 tag=97 nentries=0 etime=0.0000228213 dn="cn=Directory Manager"
[10/Dec/2018:07:58:23.236497131 +0000] conn=1 op=1 MOD dn="cn=config"
[10/Dec/2018:07:58:23.242442496 +0000] conn=1 op=1 RESULT err=0 tag=103 nentries=0 etime=0.0006057640
[10/Dec/2018:07:58:23.242664859 +0000] conn=1 op=2 UNBIND
[10/Dec/2018:07:58:23.242675880 +0000] conn=1 op=2 fd=64 closed - U1
[10/Dec/2018:07:58:35.842422218 +0000] conn=Internal(0) op=0(174)(1) MOD dn="cn=uniqueid generator,cn=config"
[10/Dec/2018:07:58:35.844357335 +0000] conn=Internal(0) op=0(174)(1) RESULT err=0 tag=48 nentries=0 etime=0.0001955328
[10/Dec/2018:07:58:39.241484658 +0000] conn=Internal(0) op=0(1)(1) SRCH base="cn=mapping tree,cn=config" scope=1 filter="(&(objectclass=nsMappingTree)(!(nsslapd-parent-suffix=*)))" attrs=ALL
[10/Dec/2018:07:58:39.241605324 +0000] conn=Internal(0) op=0(1)(1) RESULT err=0 tag=48 nentries=0 etime=0.0000127719
[10/Dec/2018:07:58:39.241644087 +0000] conn=Internal(0) op=0(2)(1) ADD dn=""
[10/Dec/2018:07:58:39.241692963 +0000] conn=Internal(0) op=0(2)(1) RESULT err=68 tag=48 nentries=0 etime=0.0000051243

Please find attachment for the complete access logs.

NOTE - I observed every-time it is same operation which comes up with random number - "MOD dn="cn=uniqueid generator,cn=config"
Comment 1 mreynolds 2018-12-11 02:05:09 UTC 
Upstream ticket:
https://pagure.io/389-ds-base/issue/50080
Comment 2 mreynolds 2019-07-31 17:14:21 UTC 
Actually the server is working correctly.  What happens is that the "random" number was from before the server was restarted.  After the server starts up the last internal operation is:

[31/Jul/2019:13:10:09.005210233 -0400] conn=Internal(0) op=0(237)(1) MOD dn="cn=uniqueid generator,cn=config"
[31/Jul/2019:13:10:09.017457233 -0400] conn=Internal(0) op=0(237)(1) RESULT err=0 tag=48 nentries=0 etime=0.0017452450

It is NOT the first operation, but with log buffering it's easy to misinterpret the order of events.  Closing as not a bug
Note You need to log in before you can comment on or make changes to this bug.