https://bugs.openldap.org/show_bug.cgi?id=9868
Issue ID: 9868
Summary: backglue and syncprov must use same pending_csn_list
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
When replication is performed on a glued DB hierarchy the syncprov overlay must
only be configured on the top DB. But when writes occur on a subDB their CSNs
will be queued on the subDB's be_pending_csn_list. When syncprov sees these
writes it will try to graduate these CSNs from the top DB's
be_pending_csn_list, but never find them there. The CSN list will grow without
bound.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8752
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=9782
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9534
Issue ID: 9534
Summary: Persistent test043 failures
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
In testing current RE25 as of 4/23/2021
(73b2769d05529a7d474661023f2c4f3a931417b2)
test043 is sporadically failing. Examining the testrun log, it appears
replication never even initiated.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9877
Issue ID: 9877
Summary: Session Tracking failing to log IP addresses
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
From slapd log in master with session tracking enabled:
62c45cfe.3b59f358 0x7fa3b0aa8700 conn=1002 fd=15 ACCEPT from IP=127.0.0.1:58790
(IP=127.0.0.1:9012)
62c45cff.017af6f5 0x7fa3b0aa8700 conn=1002 op=1 [IP=[
USERNAME=cn=manager,dc=example,dc=com] modifications:
62c45cff.017b2c53 0x7fa3b0aa8700 conn=1002 op=1 [IP=[
USERNAME=cn=manager,dc=example,dc=com] MOD dn="cn=replicator,dc=example,dc=com"
62c45cff.017bb35e 0x7fa3b0aa8700 conn=1002 op=1 [IP=[
USERNAME=cn=manager,dc=example,dc=com] MOD attr=pwdLastSuccess
Note the missing IP address. This works correctly in current 2.6.2
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9874
Issue ID: 9874
Summary: slapadd is returning garbage error data
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
When slapadd encounters an error, instead of returning that error it is
returning garbage text.
Example:
slapadd: could not add entry dn="olcDatabase={1}mdb,cn=config" (line=1119): #]I
Note the: "#]I"
If run with -d -1, we see the actual error is:
mdb_db_init: Initializing mdb database
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: could not add entry dn="olcDatabase={1}mdb,cn=config" (line=1119):
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd shutdown: initiated
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9875
Issue ID: 9875
Summary: OpenLDAP 2.6 libldap_r.so is missing
Product: OpenLDAP
Version: 2.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: andysyam61(a)gmail.com
Target Milestone: ---
OpenLDAP 2.6 libldap_r.so is missing
https://github.com/python-ldap/python-ldap/issues/432
--
You are receiving this mail because:
You are on the CC list for the issue.