Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Any -ve error code number reported as Illegal error by ldclt.
Version-Release number of selected component (if applicable):
389-ds-base-1.3.1.6-25.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Perform any OpenLDAP operation with ldclt which should give negative error for example
/usr/bin/ldclt-bin -h dhcp201-149.englab.pnq.redhat.com -p 34004 -e
esearch -e bindeach -e randomauthid -e randomauthidlow=1 -e
randomauthidhigh=9999 -o mech=DIGEST-MD5 -o authid=loginXXXX -w redhat
-s base -b o=saslstress.com -f uid=modify* -V -q -E 10004 -n 10 -N
20000 -T 1000 -W 2
2. It will give ldclt[12170]: Illegal error number -6 in SASL
Actual results:
ldclt[12170]: Illegal error number -6 in SASL
Expected results:
It should report better error message.
More Info::(By Nathan)
Negative LDAP errors are local (client-side) errors in OpenLDAP. Here
is how -6 is defined:
--------------------------------------------------------------
#define LDAP_AUTH_UNKNOWN (-6)
--------------------------------------------------------------
In mozldap, there were no negative error codes at all. It might be that
ldclt doesn't expect a negative code, and reports a poor error message
when it encounters it. This error code could be returned if an unknown
SASL mechanism was attempted (though I haven't confirmed this).
There is a minor ldclt bug in that it should expect that negative error
codes could be encountered. This code is the culprit:
----------------------------------------------------------------
/*
* Update the counters
*/
if ((err <= 0) || (err >= MAX_ERROR_NB))
{
fprintf (stderr, "ldclt[%d]: Illegal error number %d\n", mctx.pid, err);
fflush (stderr);
mctx.errorsBad++;
}
----------------------------------------------------------------
No more illegal error notification, I could see ::
=====================================================
dclt[10280]: Global average rate: 68.80/thr ( 3.82/sec), total: 344
ldclt[10280]: Global number times "no activity" reports: never
ldclt[10280]: Global number of dead threads: 1
ldclt[10280]: Global error -6 (Unknown authentication method) occurs 1 times
Catch SIGINT - exit...
ldclt[10280]: Ending at Tue Sep 1 14:52:11 2015
ldclt[10280]: Exit status 0 - No problem during execution.
[root@dhcp201-167 ~]# rpm -qa | grep 389
389-ds-base-devel-1.3.4.0-14.el7.x86_64
389-ds-base-libs-1.3.4.0-14.el7.x86_64
389-ds-base-debuginfo-1.3.4.0-14.el7.x86_64
389-ds-base-1.3.4.0-14.el7.x86_64
Hence marking bug as VERIFIED.
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.
https://rhn.redhat.com/errata/RHBA-2015-2351.html
Description of problem: Any -ve error code number reported as Illegal error by ldclt. Version-Release number of selected component (if applicable): 389-ds-base-1.3.1.6-25.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Perform any OpenLDAP operation with ldclt which should give negative error for example /usr/bin/ldclt-bin -h dhcp201-149.englab.pnq.redhat.com -p 34004 -e esearch -e bindeach -e randomauthid -e randomauthidlow=1 -e randomauthidhigh=9999 -o mech=DIGEST-MD5 -o authid=loginXXXX -w redhat -s base -b o=saslstress.com -f uid=modify* -V -q -E 10004 -n 10 -N 20000 -T 1000 -W 2 2. It will give ldclt[12170]: Illegal error number -6 in SASL Actual results: ldclt[12170]: Illegal error number -6 in SASL Expected results: It should report better error message. More Info::(By Nathan) Negative LDAP errors are local (client-side) errors in OpenLDAP. Here is how -6 is defined: -------------------------------------------------------------- #define LDAP_AUTH_UNKNOWN (-6) -------------------------------------------------------------- In mozldap, there were no negative error codes at all. It might be that ldclt doesn't expect a negative code, and reports a poor error message when it encounters it. This error code could be returned if an unknown SASL mechanism was attempted (though I haven't confirmed this). There is a minor ldclt bug in that it should expect that negative error codes could be encountered. This code is the culprit: ---------------------------------------------------------------- /* * Update the counters */ if ((err <= 0) || (err >= MAX_ERROR_NB)) { fprintf (stderr, "ldclt[%d]: Illegal error number %d\n", mctx.pid, err); fflush (stderr); mctx.errorsBad++; } ----------------------------------------------------------------