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.
Can the customer please run cl-dump.pl ? We see this type of error pop up now and then, and I want to confirm if the CSN is actually in the replication changelog or not.
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/configuration_command_and_file_reference/shell_scripts#cl_dump_Dump_and_decode_changelog
Then just grep the output file for that CSN.
Now if this problem happens again, what would be very useful is getting the RUV's as soon as possible, using something like this, but replacing the parameters values as needed:
# ldapsearch -xLLL -D "cn=directory manager" -W -b dc=example,dc=com \
'(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectclass=nstombstone))
And also running cl-dump.pl to confirm if that CSN is present or not.
(In reply to mreynolds from comment #4)
> Can the customer please run cl-dump.pl ? We see this type of error pop up
> now and then, and I want to confirm if the CSN is actually in the
> replication changelog or not.
>
> https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/
> html/configuration_command_and_file_reference/
> shell_scripts#cl_dump_Dump_and_decode_changelog
>
> Then just grep the output file for that CSN.
the link is no longer valid, but it seems we can find old DS 10 docs here as pdf (which also means we can't get a link to a specific section):
https://access.redhat.com/sites/default/files/attachments/red_hat_directory_server-10-configuration_command_and_file_reference-en-us.pdf
and under this section:
10.4.2. cl-dump.pl (Dumps and Decodes the Changelog)
however, cl-dump.pl has many options, what is an example syntax?
> Now if this problem happens again, what would be very useful is getting the
> RUV's as soon as possible, using something like this, but replacing the
> parameters values as needed:
>
> # ldapsearch -xLLL -D "cn=directory manager" -W -b dc=example,dc=com \
> '(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectclass=nstombstone))
is this the correct nsuniqueid or how do we derive the nsuniqueid to use?
(In reply to mreynolds from comment #4)
> however, cl-dump.pl has many options, what is an example syntax?
we simply tried:
# cl-dump.pl -w (hidden) | grep (our long CSN #)
is this OK?
>> # ldapsearch -xLLL -D "cn=directory manager" -W -b dc=example,dc=com \
>> '(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(objectclass=nstombstone))> is this the correct nsuniqueid or how do we derive the nsuniqueid to use?
I see we use nsuniqueid from the cl-dump.pl output..
(lol, answering my own questions..)