389-ds-base

#50581 ns-slapd crashes during ldapi search
Closed: wontfix by tbordaz. Opened by tbordaz.

Closed: wontfix
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1748016

Description of problem:
After bz1715675 ns-slapd crashes, if the instance name is longer than 34
symbols and it is accessed over ldapi socket.
Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.3-5.module+el8.1.0+3776+ece1ae4c.x86_64
How reproducible:
always
Steps to Reproduce:
1. dscreate with instance name longer than 34 symbols, for example
12345678901234567890123456789012345
2. ldapsearch -D cn=directory\ manager -w password -H
ldapi://%2fvar%2frun%2fslapd-12345678901234567890123456789012345.socket -b
cn=config
Actual results:
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
Sep 02 10:48:22 server-f30.example.com ns-slapd[28472]:
[02/Sep/2019:10:48:22.202346892 +0000] - INFO - slapd_daemon - Listening on
/var/run/slapd-12345678901234567890123456789012345.socket >
Sep 02 10:48:22 server-f30.example.com systemd[1]: Started 389 Directory Server
12345678901234567890123456789012345..
Sep 02 10:48:26 server-f30.example.com ns-slapd[28472]: *** stack smashing
detected ***: <unknown> terminated
Sep 02 10:48:26 server-f30.example.com ldapsearch[28512]: DIGEST-MD5 common
mech free
Sep 02 10:48:26 server-f30.example.com systemd[1]:
dirsrv@12345678901234567890123456789012345.service: Main process exited,
code=killed, status=6/ABRT
Sep 02 10:48:26 server-f30.example.com systemd[1]:
dirsrv@12345678901234567890123456789012345.service: Failed with result
'signal'.
Expected results:
No crash
Additional info:

Metadata Update from @tbordaz:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1748016

https://pagure.io/389-ds-base/pull-request/50582

Metadata Update from @tbordaz:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @tbordaz:
- Issue assigned to tbordaz

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0 (was: 0.0 NEEDS_TRIAGE)

c403a39c8..4c5a4316b master
f710e6a52..776befc1d 389-ds-base-1.4.1
825f06e4f..6d2b1282d 389-ds-base-1.4.0

Metadata Update from @tbordaz:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3637

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)
Metadata
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.