
OPERATIONAL DEFECT DATABASE
...

...
What were you trying to do that didn't work? Upgraded 389-ds-base to 1.3.11.1-3 and then encountered constant segfaults and general protection errors, which caused the directory server to crash. [ 9278.299907] traps: ns-slapd[12360] general protection ip:7f8f8eee8c7d sp:7f8f567f6de8 error:0 in libback-ldbm.so[7f8f8eec9000+a5000] [25630.522242] traps: ns-slapd[9971] general protection ip:7f5c542cac7d sp:7f5c167f6de8 error:0 in libback-ldbm.so[7f5c542ab000+a5000] [27374.232925] ns-slapd[16960]: segfault at 7efe006e7375 ip 00007eff43230c7d sp 00007eff099d4de8 error 4 in libback-ldbm.so[7eff43211000+a5000] [59820.302966] ns-slapd[1573]: segfault at c1 ip 00007f00b83ae25a sp 00007f0067ff1d90 error 4 in libslapd.so.0.1.0[7f00b833f000+12f000] The following backtrace was logged once: *** Error in `/usr/sbin/ns-slapd': free(): invalid pointer: 0x00007fd800444965 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x81329)[0x7fd8db37e329] /usr/lib64/dirsrv/libslapd.so.0(slapi_ch_free+0x11)[0x7fd8dc6d1ea1] /usr/lib64/dirsrv/libslapd.so.0(slapi_entry_free+0xe2)[0x7fd8dc6e0fc2] /usr/lib64/dirsrv/plugins/libback-ldbm.so(ldbm_back_next_search_entry_ext+0x6ce)[0x7fd8cdd4bfbe] /usr/lib64/dirsrv/libslapd.so.0(+0x9b816)[0x7fd8dc716816] /usr/lib64/dirsrv/libslapd.so.0(op_shared_search+0xbdd)[0x7fd8dc717ffd] /usr/sbin/ns-slapd(+0x2dece)[0x55e812c46ece] /usr/sbin/ns-slapd(+0x1bc13)[0x55e812c34c13] /lib64/libnspr4.so(+0x28f7b)[0x7fd8d97cef7b] /lib64/libpthread.so.0(+0x7ea5)[0x7fd8d916eea5] /lib64/libc.so.6(clone+0x6d)[0x7fd8db3fbb0d] Please provide the package NVR for which bug is seen: 389-ds-base-1.3.11.1-3.el7_9.x86_64 389-ds-base-libs-1.3.11.1-3.el7_9.x86_64 How reproducible: This wasn't observed in a dev environment initially, but in production with more hosts (about 300) reading from LDAP, the issue was encountered. Previous versions of 389-ds-base were able to handle this same amount of hosts without crashing. It takes a few hours for the segfault to occur, and it is not instant, despite serving many clients. Steps to reproduce Install 389-ds-base-1.3.11.1-3.el7_9.x86_64 Start up the directory service, in my case as a part of IPA Have many ipa clients use this server Observe that the directory service crashes after a few hours of operation Expected results Running 389-ds-base-1.3.11.1-3 will be reliable and not crash Actual results After a few hours, 389-ds-base-1.3.11.1-3 crashes and needs to be manually restarted. Downgrading to 389-ds-base-1.3.11.1-2 and 389-ds-base-libs-1.3.11.1-2 resolves the issue and is stable, without crashing.
Duplicate
Red Hat Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.