#50080 Random number generate for internal access logs without the sequence.
Closed: wontfix 2 years ago by mreynolds. Opened 3 years ago by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1657635

Created attachment 1512958
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"

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

3 years ago

Looks like the sequence then corrects itself, perhaps slapi_td_init() needs to be moved up/earlier in main()?

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

3 years ago

This is a not a bug, That random number was from before the server was restarted. Closing ticket...

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

2 years ago

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/3139

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: invalid)

2 years ago

Login to comment on this ticket.

Metadata