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 1433996 - ns-slapd crash during shutdown
Summary: ns-slapd crash during shutdown
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
URL:
Whiteboard:
: 1444959 (view as bug list)
Depends On:
Blocks: 1444959 1445177
TreeView+ depends on / blocked
 
Reported: 2017-03-20 14:01 UTC by Scott Poore
Modified: 2020-09-13 21:58 UTC (History)
6 users (show)

Fixed In Version: 389-ds-base-1.3.6.1-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1444959 1445177 (view as bug list)
Environment:
Last Closed: 2017-08-01 21:14:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
stacktrace.txt (18.66 KB, text/plain)
2017-03-20 14:19 UTC, Viktor Ashirov 		no flags Details
dse.ldif file from a different host with same crash (233.67 KB, text/plain)
2017-03-21 20:50 UTC, Scott Poore 		no flags Details
abrt dir from same host as dse.ldif file (24.88 KB, application/x-gzip)
2017-03-21 20:58 UTC, Scott Poore 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 2240 0 None None None 2020-09-13 21:57:56 UTC
Github 389ds 389-ds-base issues 2247 0 None None None 2020-09-13 21:58:07 UTC
Red Hat Product Errata RHBA-2017:2086 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2017-08-01 18:37:38 UTC

Description Scott Poore 2017-03-20 14:01:43 UTC 
Description of problem:

During IPA tests, we're seeing ns-slapd crash during ipactl stop.  Closer look does reproduce the crash during normal dirsrv stop as well.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.6.1-3.el7.x86_64

How reproducible:
unknown.  happening on IPA servers built from copr repo.

Steps to Reproduce:
1.  install ipa server
2.  systemctl stop dirsrv


Actual results:
coredump


Expected results:
no crash

Additional info:

Hgh level abrt report that was recieved for this crash:

reason:         ns-slapd killed by SIGABRT
crash_function: tcmalloc::Log
cmdline:        /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-EXAMPLE-TEST -i /var/run/dirsrv/slapd-EXAMPLE-TEST.pid
executable:     /usr/sbin/ns-slapd
package:        389-ds-base-1.3.6.1-3.el7
component:      389-ds-base
pid:            1495
pwd:            /var/log/dirsrv/slapd-EXAMPLE-TEST
hostname:       vm-idm-010.example.fqdn.domain
count:          1
abrt_version:   2.1.11
analyzer:       CCpp
architecture:   x86_64
backtrace_rating: 4
duphash:        e69acf929f834614a7aae48d9172ef50a6fed6ef
event_log:
global_pid:     1495
kernel:         3.10.0-613.el7.x86_64
last_occurrence: 1490017895
os_release:     Red Hat Enterprise Linux Server release 7.4 Beta (Maipo)
pkg_arch:       x86_64
pkg_epoch:      0
pkg_name:       389-ds-base
pkg_release:    3.el7
pkg_vendor:     Fedora Project COPR (pvomacka/ipa)
pkg_version:    1.3.6.1
runlevel:       N 3
time:           Mon 20 Mar 2017 07:21:35 PM IST
type:           CCpp
uid:            389
username:       dirsrv
uuid:           ea037332c2f687eaf4e5bc863c7486a52d28d05d
Comment 2 Scott Poore 2017-03-20 14:16:20 UTC 
Note, the dirsrv errors log shows a huge number of the following messages:

WARN - ns_handle_pr_read_ready - Received idletime out with c->c_idletimeout as 0. Ignoring.
Comment 3 Viktor Ashirov 2017-03-20 14:19:07 UTC 
Created attachment 1264768 [details]
stacktrace.txt

Attaching stacktrace from crash report
Comment 4 Viktor Ashirov 2017-03-20 14:25:16 UTC 
(In reply to Scott Poore from comment #2)
> Note, the dirsrv errors log shows a huge number of the following messages:
> 
> WARN - ns_handle_pr_read_ready - Received idletime out with c->c_idletimeout
> as 0. Ignoring.
This is probably unrelated, see 
https://bugzilla.redhat.com/show_bug.cgi?id=1432917
Upstream: https://pagure.io/389-ds-base/issue/49174
Comment 7 mreynolds 2017-03-21 20:11:48 UTC 
Upstream ticket:
https://pagure.io/389-ds-base/issue/49181
Comment 8 mreynolds 2017-03-21 20:37:42 UTC 
Can we get the dse.ldif?  I need to see how the retro changelog plugin is configured.  I guess it could come from any IPA install as I'm assuming the setup would be the same.
Comment 9 Scott Poore 2017-03-21 20:50:36 UTC 
Created attachment 1265199 [details]
dse.ldif file from a different host with same crash

Unfortunately, the host I originally gathered info from is not available.  However, This file is from a different server with the same crash.  If needed, I can send the relevant abrt reports for this one too.
Comment 10 Scott Poore 2017-03-21 20:58:10 UTC 
Created attachment 1265202 [details]
abrt dir from same host as dse.ldif file
Comment 11 mreynolds 2017-03-21 21:57:44 UTC 
I can't reproduce the crash with the same retro changelog configuration.  Something else is going on.  Would it be possible to rerun the test with DS under valgrind?

targetUniqueID is that a real attribute?  Is it part of the IPA schema? 

Also the logs that are attached don't appear to be from the time of the crash.  I don't see the crash in the errors log, and  I don't see the mod operations on the retro changelog in the access log.  Can I get a fresh/full set of logs from the most recent crash?  Thanks!
Comment 12 wibrown@redhat.com 2017-03-21 22:38:37 UTC 
What if this is the dynamic plugin double free issue we have seen? Is IPA using dynamic plugins?
Comment 13 mreynolds 2017-03-22 02:04:31 UTC 
(In reply to wibrown from comment #12)
> What if this is the dynamic plugin double free issue we have seen? Is IPA
> using dynamic plugins?

They are not using dynamic plugins.


Scott, one more question...  Once it crashes, does it keep crashing every time you stop the server?
Comment 14 Scott Poore 2017-03-22 13:19:41 UTC 
Yes, it keeps crashing every time I stop the server.
Comment 15 mreynolds 2017-03-22 14:13:49 UTC 
Using this upstream ticket to track the fix:

https://pagure.io/389-ds-base/issue/49188
Comment 16 mreynolds 2017-03-23 15:27:16 UTC 
Fixed upstream
Comment 18 Scott Poore 2017-03-29 21:16:49 UTC 
Verified.

Version ::

389-ds-base-1.3.6.1-5.el7.x86_64


Results ::

No crashes seen by tests run with newer version (-4 or later).

Also, manually tested here immediately following a fresh IPA install:

[root@rhel7-1 ~]# kinit admin
Password for admin: 

[root@rhel7-1 ~]# ipactl stop
Stopping ipa-dnskeysyncd Service
Stopping ipa-otpd Service
Stopping pki-tomcatd Service
Stopping ntpd Service
Stopping ipa-custodia Service
Stopping httpd Service
Stopping named Service
Stopping kadmin Service
Stopping krb5kdc Service
Stopping Directory Service
ipa: INFO: The ipactl command was successful

[root@rhel7-1 ~]# systemctl start dirsrv@EXAMPLE-COM

[root@rhel7-1 ~]# ps -ef|grep slap
dirsrv    5106     1  9 16:05 ?        00:00:00 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-EXAMPLE-COM -i /var/run/dirsrv/slapd-EXAMPLE-COM.pid
root      5155  1164  0 16:05 pts/0    00:00:00 grep --color=auto slap

[root@rhel7-1 ~]# systemctl stop dirsrv@EXAMPLE-COM

[root@rhel7-1 ~]# ls /var/log/dirsrv/slapd-EXAMPLE-COM/
access  access.rotationinfo  audit  audit.rotationinfo  errors  errors.rotationinfo

[root@rhel7-1 ~]# ls /var/spool/abrt

[root@rhel7-1 ~]# grep -i segfault /var/log/messages

[root@rhel7-1 ~]# rpm -q 389-ds-base
389-ds-base-1.3.6.1-5.el7.x86_64
Comment 19 mreynolds 2017-04-24 16:57:56 UTC 
*** Bug 1444959 has been marked as a duplicate of this bug. ***
Comment 21 errata-xmlrpc 2017-08-01 21:14:10 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, 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-2017:2086
Note You need to log in before you can comment on or make changes to this bug.