Bug 1890118

Summary: SIGFPE crash in rhds disk monitoring routine
Product: Red Hat Enterprise Linux 8 Reporter: Renaud Marigny <rmarigny>
Component: 389-ds-baseAssignee: mreynolds
Status: CLOSED ERRATA QA Contact: RHDS QE <ds-qe-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 8.2CC: bsmejkal, jachapma, mreynolds, sgouvern, spichugi, tbordaz, vashirov
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 389-ds-1.4-8040020210107175838-866effaa Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 15:45:43 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:
Attachments:
Description Flags
Fix and debug patch none

Comment 5 mreynolds 2020-10-28 16:21:55 UTC
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

Comment 12 mreynolds 2020-10-29 14:14:50 UTC
Upstream ticket:
https://github.com/389ds/389-ds-base/issues/4414

Comment 14 mreynolds 2020-11-01 15:47:07 UTC
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.

Comment 15 mreynolds 2020-11-09 15:14:08 UTC
Has the customer tested this patch and gathered the debug info yet?

Comment 23 sgouvern 2020-12-18 10:52:25 UTC
ITM strip suspended during end of year break -> moving to ITM 10

Comment 25 bsmejkal 2021-01-11 11:20:46 UTC
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.

Comment 31 sgouvern 2021-01-18 14:13:06 UTC
wrong build attached to the errata -> moving to ITM12

Comment 32 sgouvern 2021-01-18 14:47:52 UTC
Correct build now attached to the errata : as per comment 25, marking as VERIFIED and moving back to ITM11

Comment 35 errata-xmlrpc 2021-05-18 15:45:43 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 (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 36 Red 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