#47907 ldclt: assertion failure with -e "add,counteach" -e "object=<ldif file>,rdn=uid:test[A=INCRNNOLOOP(0;24999;5)]"
Closed: wontfix None Opened 9 years ago by nhosoi.

There is an issue when I run ldclt using counteach.

# ldclt -v -h localhost -p 389 -D "cn=directory manager" -w <PW> -b "cn=Users,dc=test,dc=com" -e "object=<file>,rdn=uid:test[A=INCRNNOLOOP(0;24999;5)]" -e "add,counteach" -n 100 -N 3600 -T 5000
ldclt version 4.23
Set file number to 4096
/usr/bin/ldclt-bin -v -h localhost -p 389 -D "cn=directory manager" -w <PW> -b cn=Users,dc=test,dc=com -e object=<file>,rdn=uid:test[A=INCRNNOLOOP(0;24999;5)] -e add,counteach -n 100 -N 3600 -T 5000
Process ID         = 17813
Host to connect    = localhost
Port number        = 389
Bind DN            = cn=directory manager
Passwd             = <PW>
Referral           = on
Base DN            = cn=Users,dc=test,dc=com
Filter             = NULL
Max times inactive = 3
Max allowed errors = 1000
Number of samples  = 3600
Number of threads  = 100
Total op. req.     = 5000
Running mode       = 0x04002001
Running mode       = verbose counteach add object=<file>
LDAP oper. timeout = 30 sec
Sampling interval  = 10 sec
ldclt[17813]: Starting at Mon Sep 15 16:25:51 2014

ldclt[17813]: T003: Cannot add (uid=test00000,cn=Users,dc=test,dc=com), error=32 (No such object)
ldclt[17813]: T003: Intermediate nodes created for uid=test00000,cn=Users,dc=test,dc=com
ldclt-bin: add.c:125: ldap_add_ext: Assertion `( (ld)->ldc->ldc_options.ldo_valid == 0x2 )' failed.
/usr/bin/ldclt: line 55: 17813 Aborted                 (core dumped) ${dir}/${COMMAND} "$@"

ack, but don't ifdef the code out, just remove it.

git patch file (master) -- Based on the comment from Rich (Thank you!!), removing the unbind call instead of commenting it out.
0001-Ticket-47907-ldclt-assertion-failure-with-e-add-coun.2.patch

Reviewed by Rich (Thank you!!)

Pushed to master:
5ae1307..685607f master -> master
commit 685607f

Pushed to 389-ds-base-1.3.3:
ef76678..906106b 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 906106b

Pushed to 389-ds-base-1.3.2:
1db611e..8c955b1 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 8c955b1

Pushed to 389-ds-base-1.2.11:
189eb8a..dd62c75 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit dd62c75

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.2.11.33

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

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)

3 years ago

Login to comment on this ticket.

Metadata