https://bugs.openldap.org/show_bug.cgi?id=9277
Issue ID: 9277
Summary: restart 3+ providers at once burns CPU forever
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
I have tiny VMs configured as Æ-DIR servers, 5 providers (multi-provider
replication) and 5 read-only consumers each syncing with all providers.
Restarting all consumers at once simply works, no matter how many of the
providers are up.
Restarting only two providers at once also works.
But when restarting more than two providers at once all of thems seem to hang
eating up CPU.
It could be the same issue like ITS#8650 / ITS#9210 but those only mention
GNUTLS being affected. But all my Æ-DIR test servers run slapd built against
OpenSSL (openSUSE, Debian buster, CentOS7).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9286
Issue ID: 9286
Summary: mdb_cursor_get MDB_GET_MULTIPLE key not populated
Product: LMDB
Version: 0.9.25
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: corey(a)kaylors.net
Target Milestone: ---
Reading the docs it says "Return key and up to a page of duplicate data items
from current cursor position." when MDB_GET_MULTIPLE is used. I don't see the
key being populated, but when I call MDB_GET_CURRENT after the use of
MDB_GET_MULTIPLE the key is the value I expect. Looking through the code I
don't see the key getting used in this path. Granted, I'm not proficient with C
so I may have overlooked something.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9268
Issue ID: 9268
Summary: Test065 fails due to invalid log level
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: andy(a)asjohnson.com
Target Milestone: ---
Line #109 of tests/scripts/test065-proxyauthz:
$SLAPD -f $CONF2 -h $URI2 -d $LVL -d pcache > $LOG2 2>&1 &
Results in this:
must compile with LDAP_DEBUG for debugging
unrecognized log level "pcache" (deferred)
After which the test fails.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9250
Bug ID: 9250
Summary: librewrite only supports up to 9 submatches
Product: OpenLDAP
Version: 2.4.49
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: ryan(a)openldap.org
Target Milestone: ---
libraries/librewrite$ cat nine.conf
rewriteEngine on
rewriteContext default
rewriteRule "(.)(.)(.)(.)(.)(.)(.)(.)(.)" "$9$8$7$6$5$4$3$2$1" :
libraries/librewrite$ ./rewrite -f nine.conf abcdefghijklmnop
abcdefghijklmnop -> ihgfedcba [0:ok]
libraries/librewrite$ cat eleven.conf
rewriteEngine on
rewriteContext default
rewriteRule "(.)(.)(.)(.)(.)(.)(.)(.)(.)(.)(.)" "$11$10$9$8$7$6$5$4$3$2$1" :
libraries/librewrite$ ./rewrite -f eleven.conf abcdefghijklmnop
abcdefghijklmnop -> a1a0ihgfedcba [0:ok]
I guess no one has needed that many yet... :)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9185
Bug ID: 9185
Summary: glue entry
Product: OpenLDAP
Version: 2.4.48
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: gnoe(a)symas.com
Target Milestone: ---
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
https://bugs.openldap.org/show_bug.cgi?id=9302
Issue ID: 9302
Summary: ppolicy pwdFailureTime race condition leaves acccount
unlocked, violating pwdLockout policy
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: requate(a)univention.de
Target Milestone: ---
Multiple concurrent ldap binds with invalid passwords against a user account
sometimes don't trigger account lockout, even though the number of failed
attempts exceeds the configured pwdLockout policy of the ppolicy overlay.
How to reproduce:
1. Configure ppolicy overlay with pwdLockout: TRUE
2. set pwdMaxFailure to some value, e.g. 5
3. Create a test user account and start just enough (or more) parallel
ldapsearch processes
to make the account get locked, e.g. like this in bash/sh (note the
backgrounding):
for i in $(seq 6); do
ldapsearch -x -D "uid=testuser1,$ldap_base" -w invalid >/dev/null 2>&1 &
done
4. Check relevant ppolicy attributes, like:
ldapsearch -x -H LDAPI:// -b "uid=testuser1,$ldap_base" + \
grep -E '^(pwdFailureTime|pwdAccountLockedTime):'
This often shows no pwdAccountLockedTime but enough (or more) pwdFailureTime
values to meet the lockout policy.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9249
Bug ID: 9249
Summary: A dollar sign ($) at the end of the 2nd argument of
olcAuthzRegexp crashes slapd
Product: OpenLDAP
Version: 2.4.47
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: kop(a)karlpinc.com
Target Milestone: ---
The following ldif, fed to ldapmodify, crashes slapd.
dn: cn=config
changetype: modify
replace: olcAuthzRegexp
olcAuthzRegexp: "^([^,]+),cn=PLAIN,cn=auth" "$1,ou=People,dc=example,dc=com$"
Happens on Debian 10 with openldap 2.4.47 and RHEL 8 with openldap 2.4.46.
Doing ldapmodify -d -1 seems to crash only 1 out of 3 times, but it always
crashes without the -d -1.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9304
Issue ID: 9304
Summary: Archived-At: -> 404
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
I appreciate this mailing list message header:
Archived-At:
<https://openldap.org/hyperkitty/list/openldap-technical@openldap.org/messag…>
But unfortunately the link returns 404.
--
You are receiving this mail because:
You are on the CC list for the issue.