#51035 Heavy StartTLS connection load can randomly fail with err=1
Closed: wontfix 4 years ago by tbordaz. Opened 4 years ago by tbordaz.

Issue Description

Under intensif starttls, some start-tls extop are failing.

Package Version and Platform

All version

Steps to reproduce

#install an instance with secure connection enabled
while [ 1 ]
do
    LDAPTLS_CACERTDIR=/etc/dirsrv/slapd-localhost ldapsearch -xLLL -ZZ -D cn=dm -w redhat123 -b "" -s base dn &
    LDAPTLS_CACERTDIR=/etc/dirsrv/slapd-localhost ldapsearch -xLLL -ZZ -D cn=dm -w redhat123 -b "" -s base dn &
    LDAPTLS_CACERTDIR=/etc/dirsrv/slapd-localhost ldapsearch -xLLL -ZZ -D cn=dm -w redhat123 -b "" -s base dn
done

Actual results

We can see some connection failing during start-tls

Expected results

All start-tls should succeed


Metadata Update from @tbordaz:
- Issue assigned to tbordaz

4 years ago

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

4 years ago

Metadata Update from @tbordaz:
- Issue set to the milestone: 1.4.3

4 years ago

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

4 years ago

8fbdf92..285fd0d 389-ds-base-1.4.3
3ce0896..731a5b5 389-ds-base-1.4.2
9038be2..11f1b55 389-ds-base-1.4.1

Metadata Update from @tbordaz:
- Issue set to the milestone: 1.4.1 (was: 1.4.3)

4 years ago

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/4088

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)

4 years ago

Log in to comment on this ticket.

Metadata