https://bugs.openldap.org/show_bug.cgi?id=9599
Issue ID: 9599
Summary: Additional balancing strategies for lloadd
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: lloadd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
At the moment, lloadd picks a backend on a round-robin basis, taking the first
one that can deal with the request. This has several disadvantages:
- there is no way to implement a failover set up where certain (e.g. local)
servers should be contacted as a priority
- all balancing is implicit on the limits imposed on servers - a
connection/server is a candidate until we've reached those limits
Allowing a priority and/or a different strategy to be set should address these.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9598
Issue ID: 9598
Summary: Restricted operation routing in lloadd
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: lloadd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
Lloadd is not supposed to understand the LDAP protocol and is happy to route
operations to whichever connection is available, but this can backfire in
certain ways:
- there are controls and extended operations that establish an shared context
on the connection (paged results, TXN, ...)
- it might take a measurable amount of time before a write operation is
propagated to other servers
There should be a way to force some of these to a chosen backend/upstream
connection temporarily or even permanently based on the OID of the
extop/control in question.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9597
Issue ID: 9597
Summary: Send a Notice of Disconnection to clients
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: lloadd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
When closing client connections, lloadd should try and send a NoD response
first.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9633
Issue ID: 9633
Summary: Intermittent test030 failure caused by referral
chasing
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Not 100% reproducible but occurs frequently using ldif or wt backends. The test
hits an assert failure in libldap.
>>>>> Starting test030-relay for wt...
running defines.sh
Testing virtual naming context mapping with relay ldap meta backend(s)...
Using relay backend...
Starting slapd on TCP/IP port 9051...
Using ldapsearch to check that slapd is running...
Using ldapadd to populate the database...
Searching base="dc=example,dc=com"...
Searching base="o=Example,c=US"...
Searching base="o=Esempio,c=IT"...
Searching base="o=Beispiel,c=DE"...
Modifying database "o=Beispiel,c=DE"...
Modifying database "o=Example,c=US"...
Searching base="o=Example,c=US"...
Searching base="o=Esempio,c=IT"...
Searching filter="(objectClass=referral)"
attrs="'*' ref"
base="dc=example,dc=com"...
base="o=Example,c=US"...
base="o=Esempio,c=IT"...
Searching filter="(seeAlso=cn=all staff,ou=Groups,o=Example,c=US)"
attrs="seeAlso"
base="o=Example,c=US"...
Searching filter="(uid=example)"
attrs="uid"
base="o=Example,c=US"...
Searching filter="(member=cn=Another Added Group,ou=Groups,o=Example,c=US)"
attrs="member"
base="o=Example,c=US"...
Filtering ldapsearch results...
Filtering original ldif used to create database...
Comparing filter output...
Changing password to database "o=Example,c=US"...
Binding with newly changed password to database "o=Beispiel,c=DE"...
Comparing to database "o=Esempio,c=IT"...
>>>>> waiting for things to exit
Using ldap backend...
Starting slapd on TCP/IP port 9051...
Using ldapsearch to check that slapd is running...
Using ldapadd to populate the database...
Searching base="dc=example,dc=com"...
Searching base="o=Example,c=US"...
Searching base="o=Esempio,c=IT"...
Searching base="o=Beispiel,c=DE"...
Modifying database "o=Beispiel,c=DE"...
Modifying database "o=Example,c=US"...
Searching base="o=Example,c=US"...
Search failed (255)!
../../head/tests/scripts/test030-relay: 240: kill: No such process
>>>>> Failed test030-relay for wt after 3 seconds
(exit 255)
make[1]: Leaving directory '/home/hyc/OD/hobj/tests'
backtrace:
gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1 0x00007fb9119bd864 in __GI_abort () at abort.c:79
#2 0x00007fb9119bd749 in __assert_fail_base (
fmt=0x7fb911b46f78 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=0x7fb9123efc93 "lr->lr_refcnt == 0",
file=0x7fb9123ef5c0 "../../../head/libraries/libldap/request.c",
line=1671, function=<optimized out>) at assert.c:92
#3 0x00007fb9119cf3d6 in __GI___assert_fail (
assertion=0x7fb9123efc93 "lr->lr_refcnt == 0",
file=0x7fb9123ef5c0 "../../../head/libraries/libldap/request.c",
line=1671,
function=0x7fb9123efe70 <__PRETTY_FUNCTION__.1>
"ldap_find_request_by_msgid") at assert.c:101
#4 0x00007fb9121d671c in ldap_find_request_by_msgid (ld=0x7fb8fc124d70,
msgid=3) at ../../../head/libraries/libldap/request.c:1671
#5 0x00007fb9121b882d in try_read1msg (ld=0x7fb8fc124d70, msgid=5, all=1,
lc=0x7fb8fc128180, result=0x7fb90511bf48)
at ../../../head/libraries/libldap/result.c:575
#6 0x00007fb9121b8135 in wait4msg (ld=0x7fb8fc124d70, msgid=5, all=1,
timeout=0x7fb90511bf90, result=0x7fb90511bf48)
at ../../../head/libraries/libldap/result.c:369
#7 0x00007fb9121b77cb in ldap_result (ld=0x7fb8fc124d70, msgid=5, all=1,
timeout=0x7fb90511bf90, result=0x7fb90511bf48)
--Type <RET> for more, q to quit, c to continue without paging--
at ../../../head/libraries/libldap/result.c:120
#8 0x00007fb9121d3b8c in ldap_new_connection (ld=0x7fb8fc124d70,
srvlist=0x7fb90511c160, use_ldsb=0, connect=1, bind=0x7fb90511c1a0,
m_req=1, m_res=1) at ../../../head/libraries/libldap/request.c:627
#9 0x00007fb9121d2ba0 in ldap_send_server_request (ld=0x7fb8fc124d70,
ber=0x7fb8f0137ea0, msgid=4, parentreq=0x7fb8f0000fd0,
srvlist=0x7fb90511c160, lc=0x0, bind=0x7fb90511c1a0, m_noconn=0, m_res=1)
at ../../../head/libraries/libldap/request.c:253
#10 0x00007fb9121d56e5 in ldap_chase_v3referrals (ld=0x7fb8fc124d70,
lr=0x7fb8f0000fd0, refs=0x0, sref=1, errstrp=0x7fb8f0001000,
hadrefp=0x7fb90511c208) at ../../../head/libraries/libldap/request.c:1283
#11 0x00007fb9121b8b40 in try_read1msg (ld=0x7fb8fc124d70, msgid=3, all=0,
lc=0x7fb8fc128180, result=0x7fb90511c4e8)
at ../../../head/libraries/libldap/result.c:680
#12 0x00007fb9121b8135 in wait4msg (ld=0x7fb8fc124d70, msgid=3, all=0,
timeout=0x7fb90511c520, result=0x7fb90511c4e8)
at ../../../head/libraries/libldap/result.c:369
#13 0x00007fb9121b77cb in ldap_result (ld=0x7fb8fc124d70, msgid=3, all=0,
timeout=0x7fb90511c520, result=0x7fb90511c4e8)
at ../../../head/libraries/libldap/result.c:120
#14 0x000055a093724e35 in ldap_back_search (op=0x7fb8f0000be0,
rs=0x7fb90511d990) at ../../../../head/servers/slapd/back-ldap/search.c:317
#15 0x000055a0936ff157 in overlay_op_walk (op=0x7fb8f0000be0,
--Type <RET> for more, q to quit, c to continue without paging--
rs=0x7fb90511d990, which=op_search, oi=0x55a0943711d0, on=0x0)
at ../../../head/servers/slapd/backover.c:706
#16 0x000055a0936ff417 in over_op_func (op=0x7fb8f0000be0, rs=0x7fb90511d990,
which=op_search) at ../../../head/servers/slapd/backover.c:766
#17 0x000055a0936ff59b in over_op_search (op=0x7fb8f0000be0, rs=0x7fb90511d990)
at ../../../head/servers/slapd/backover.c:796
#18 0x000055a09365d201 in fe_op_search (op=0x7fb8f0000be0, rs=0x7fb90511d990)
at ../../../head/servers/slapd/search.c:426
#19 0x000055a09365c9fa in do_search (op=0x7fb8f0000be0, rs=0x7fb90511d990)
at ../../../head/servers/slapd/search.c:267
#20 0x000055a093658e0c in connection_operation (ctx=0x7fb90511daf0,
arg_v=0x7fb8f0000be0) at ../../../head/servers/slapd/connection.c:1113
#21 0x000055a09365956b in connection_read_thread (ctx=0x7fb90511daf0,
argv=0x10) at ../../../head/servers/slapd/connection.c:1265
#22 0x00007fb9121feea3 in ldap_int_thread_pool_wrapper (xpool=0x55a094357ac0)
at ../../../head/libraries/libldap/tpool.c:1053
#23 0x00007fb911b8c450 in start_thread (arg=0x7fb90511e640)
at pthread_create.c:481
#24 0x00007fb911aaed53 in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) frame 11
#11 0x00007fb9121b8b40 in try_read1msg (ld=0x7fb8fc124d70, msgid=3, all=0,
lc=0x7fb8fc128180, result=0x7fb90511c4e8)
at ../../../head/libraries/libldap/result.c:680
680 refer_cnt =
ldap_chase_v3referrals( ld, lr, refs,
(gdb) l
675 if ( ber_scanf( &tmpber, "{v}", &refs )
== LBER_ERROR ) {
676 rc = LDAP_DECODING_ERROR;
677
678 } else {
679 /* Note: refs array is freed by
ldap_chase_v3referrals */
680 refer_cnt =
ldap_chase_v3referrals( ld, lr, refs,
681 1, &lr->lr_res_error,
&hadref );
682 if ( refer_cnt > 0 ) {
683 /* successfully chased
reference */
684 /* If haven't got end
search, set chasing referrals */
(gdb) p *lr
$7 = {lr_msgid = 3, lr_status = 1, lr_refcnt = 1, lr_outrefcnt = 1,
lr_abandoned = 0, lr_origid = 3, lr_parentcnt = 0, lr_res_msgtype = 115,
lr_res_errno = 0, lr_res_error = 0x0, lr_res_matched = 0x0,
lr_ber = 0x7fb8f0139eb0, lr_conn = 0x7fb8fc128180, lr_dn = {bv_len = 17,
bv_val = 0x7fb8f0128b79 "dc=example,dc=com\n\001\002\n\001"},
lr_parent = 0x0, lr_child = 0x0, lr_refnext = 0x0, lr_prev = 0x0,
lr_next = 0x0}
(gdb)
The problem appears to be due to recursion in try_read1msg() when chasing a
referral. In this case it's processing msgid 3 and then while looking for
response to msgid 5 it sees another response to msgid 3. It looks up the
corresponding request and sees it already has a non-zero lr_refcnt and assert
fails there.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9716
Issue ID: 9716
Summary: Fix default guide versions for head and 2.6
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The preamble file needs to be fixed in openldap head and the 2.6 release branch
to be correct.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9653
Issue ID: 9653
Summary: typo in access-control.sdf
Product: OpenLDAP
Version: 2.5.4
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
https://git.openldap.org/openldap/openldap/-/blob/master/doc/guide/admin/ac…
says:
“““
This directive allows users to modify their own entries if security protections
have of strength 128 or better have been established, allows authentication
access to anonymous users, and read access when 64 or better security
protections have been established.
”””
The first “have” must be deleted.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9649
Issue ID: 9649
Summary: servers/slapd/schema/README missing schema
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The servers/slapd/schema/README file is supposed to contain information about
the schema files found in this directory. However it is missing any entry for:
dsee.schema
msuser.schema
namedobject.schema
pmi.schema
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9638
Issue ID: 9638
Summary: ldapsearch.1 documents default value of -T
inaccurately
Product: OpenLDAP
Version: 2.5.6
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: ryan(a)openldap.org
Target Milestone: ---
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992130
The ldapsearch.1 man page says the default value for tmpdir (-T) is /var/tmp.
The actual default value can come from a number of sources: environment
variables (TMPDIR, TMP, TEMP), preprocessor macros (_P_tmpdir, P_tmpdir,
_PATH_TMPDIR), or a hard-coded fallback (/tmp).
The ldapsearch --help output correctly reflects the default value.
It would be nice if the ldapsearch man page would reflect the actual
compile-time default (LDAP_TMPDIR) and mention that it consults some
environment variables.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9589
Issue ID: 9589
Summary: slapd.access.5 incorrect man page references
Product: OpenLDAP
Version: 2.5.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The slapd.access(5) man page references:
.BR back\-mdb (5).
.BR back\-sql (5),
Neither of these are valid man pages, as they are slapd-mdb(5) and
slapd-sql(5).
However, we reference back-<backend> throughout our documentation.
Should we perhaps create links for the backend manpages so they can be found
either way?
I.e.:
slapd-mdb.5.links -> back-mdb.5
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9586
Issue ID: 9586
Summary: Admin guide: Need example fractional replication
configuration
Product: OpenLDAP
Version: 2.5.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The admin guide states:
Syncrepl supports partial, sparse, and fractional replications
but there are no example configurations for partial replication to draw from.
This needs to be added to the guide.
--
You are receiving this mail because:
You are on the CC list for the issue.