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.
Since this is crashing often can the debuginfo package for 389-ds-base be installed so we can get a better stack trace? This stack is not very useful:
#0 0x000055c19b7fd48f in monitor_disk_info ()
#1 0x00007f863211c387 in dse_call_callback.isra () at /usr/lib64/dirsrv/libslapd.so.0
#2 0x00007f863211e11d in dse_search () at /usr/lib64/dirsrv/libslapd.so.0
#3 0x00007f863215b3eb in op_shared_search () at /usr/lib64/dirsrv/libslapd.so.0
#4 0x000055c19b8051b3 in do_search ()
#5 0x000055c19b7f2fbd in connection_threadmain ()
#6 0x00007f862fa935a8 in _pt_root () at /lib64/libnspr4.so
#7 0x00007f862f42e2de in start_thread () at /lib64/libpthread.so.0
#8 0x00007f862ebc2e83 in clone () at /lib64/libc.so.6
If these steps below could be done it would be very helpful:
# debuginfo-install 389-ds-base
# gdb -ex 'set confirm off' -ex 'set pagination off' -ex 'thread apply all bt full' -ex 'quit' /usr/sbin/ns-slapd <path to core dump> > stacktrace.out
Created attachment 1725567[details]
Fix and debug patch
The patch fixes the division by zero error/crash, and adds debug logging to the errors log that prints what Directory Server path is mapping to what disk mount.
Build tested:
389-ds-base-1.4.3.16-7.module+el8.4.0+9324+a82a8f71.x86_64
Fix is present in the package.
Automation steps are under investigation.
Marking as SanityOnly, Verified:Tested.
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 (389-ds:1.4 bug fix and enhancement update), 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-2021:1835
Comment 36Red Hat Bugzilla
2023-09-15 00:50:01 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days