Bug 1296310

Summary: ldclt - segmentation fault error while binding
Product: Red Hat Enterprise Linux 7 Reporter: Simon Pichugin <spichugi>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: low Docs Contact:
Priority: medium    
Version: 7.2CC: nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://faf-report.itos.redhat.com/reports/bthash/5ed0abae7c6b452f1d9a1101e76441d1ab278003/
Fixed In Version: 389-ds-base- Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 20:38:46 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:

Description Simon Pichugin 2016-01-06 21:11:56 UTC
Description of problem:
ldclt binding query crashes with a certain set of parameters.

Version-Release number:
ldclt version 4.23

How reproducible:

Steps to Reproduce:
1. Install instance with setup-ds.pl
2. Run ldclt binding query with following set of parameters:
ldclt -h localhost -p 389 -e bindeach,bindonly -D uid=XXXX,dc=example,dc=com -w testXXXX -e randombinddn,randombinddnlow=0,randombinddnhigh=9999

Actual results:
ldclt version 4.23
ldclt[14001]: Starting at Wed Jan  6 22:06:10 2016

/usr/bin/ldclt: line 55: 14001 Segmentation fault      (core dumped) ${dir}/${COMMAND} "$@"

Expected results:
Successfully perform requested operation:
ldclt version 4.23
ldclt[14001]: Starting at Wed Jan  6 22:06:10 2016

ldclt[14001]: Ending at Wed Jan  6 22:06:00 2016
ldclt[14001]: Exit status 0 - No problem during execution.

Comment 3 Noriko Hosoi 2016-01-06 22:30:10 UTC
Upstream ticket:

Comment 4 Mike McCune 2016-03-28 23:13:32 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Comment 6 Simon Pichugin 2016-05-16 12:06:07 UTC
Build tested:

Verification steps:
1. Install Directory Server instance
2. Create ldclt user entry template
[spichugi@machine ~]$ cat /tmp/ldclt_template_lib389.ldif
objectClass: top
objectclass: person
objectClass: organizationalPerson
objectClass: inetorgperson
objectClass: posixAccount
objectClass: shadowAccount
sn: user[A]
cn: user[A]
givenName: user[A]
description: description [A]
userPassword: user[A]
mail: user[A]@example.com
uidNumber: 1[A]
gidNumber: 2[A]
shadowMin: 0
shadowMax: 99999
shadowInactive: 30
shadowWarning: 7
homeDirectory: /home/user[A]
loginShell: /bin/false

3. Create 1000 users with ldclt
[spichugi@machine ~]$ /bin/ldclt-bin -h localhost -p 54321 -D "cn=Directory Manager" -w Secret123 -b ou=People,dc=example,dc=com -e add,commoncounter -e "object=/tmp/ldclt_template_lib389.ldif,rdn=uid:user[A=INCRNNOLOOP(100
ldclt version 4.23
ldclt[29025]: Starting at Mon May 16 07:58:11 2016
ldclt[29025]: Ending at Mon May 16 07:58:31 2016
ldclt[29025]: Exit status 0 - No problem during execution.

4. Run bind ldclt operations
[spichugi@machine ~]$ /bin/ldclt-bin -h localhost -p 54321 -N 3 -D uid=userXXXX,ou=People,dc=example,dc=com -w userXXXX -e randombinddn,randombinddnlow=1000,randombinddnhigh=1999 -e bindonly
ldclt version 4.23
ldclt[29036]: Starting at Mon May 16 07:59:20 2016

ldclt[29036]: Average rate: 25386042.00/thr  (25386042.00/sec), total: 253860416
ldclt[29036]: Average rate: 25971052.00/thr  (25971052.00/sec), total: 259710514
ldclt[29036]: Average rate: 25273116.00/thr  (25273116.00/sec), total: 252731156
ldclt[29036]: T000: thread is dead.
ldclt[29036]: T006: thread is dead.
ldclt[29036]: Number of samples achieved. Bye-bye...
ldclt[29036]: All threads are dead - exit.
ldclt[29036]: Global average rate: 76630208.00/thr  (25543402.00/sec), total: 766302086
ldclt[29036]: Global number times "no activity" reports: never
ldclt[29036]: Global number of dead threads: 2
ldclt[29036]: Global no error occurs during this session.
ldclt[29036]: Ending at Mon May 16 07:59:50 2016
ldclt[29036]: Exit status 0 - No problem during execution.

No segmentation fault appears.

Marking as verified.

Comment 8 errata-xmlrpc 2016-11-03 20:38:46 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.