https://bugs.openldap.org/show_bug.cgi?id=9882
Issue ID: 9882
Summary: slapd crashes when lastbind enabled w/ multi-provider
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: smckinney(a)symas.com
Target Milestone: ---
Created attachment 907
--> https://bugs.openldap.org/attachment.cgi?id=907&action=edit
slapd.conf
Description:
Crash during bind operation when lastbind's enabled in a multi-provider env.
Built from source:
commit 23ef018c6f321413141f26ed6e1909f85047ba76 (HEAD -> OPENLDAP_REL_ENG_2_6,
origin/OPENLDAP_REL_ENG_2_6)
Configuration: attached
System: AlmaLinux8
Backtrace:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00000000004dfe66 in over_op_func (op=0x7d6b1fffe690, rs=0x7d6b1fffe620,
which=op_modify) at backover.c:749
749 on = oi->oi_list;
[Current thread is 1 (Thread 0x7d6b1ffff700 (LWP 96272))]
Missing separate debuginfos, use: yum debuginfo-install
cyrus-sasl-lib-2.1.27-6.el8_5.x86_64 glibc-2.28-189.5.el8_6.x86_64
keyutils-libs-1.5.10-9.el8.x86_64 krb5-libs-1.18.2-14.el8.x86_64
libblkid-2.32.1-35.el8.x86_64 libcap-2.48-2.el8.x86_64
libcom_err-1.45.6-4.el8.x86_64 libdb-5.3.28-42.el8_4.x86_64
libgcc-8.5.0-10.1.el8_6.alma.x86_64 libmount-2.32.1-35.el8.x86_64
libselinux-2.9-5.el8.x86_64 libtool-ltdl-2.4.6-25.el8.x86_64
libuuid-2.32.1-35.el8.x86_64 libxcrypt-4.1.1-6.el8.x86_64
openssl-libs-1.1.1k-6.el8_5.x86_64 pcre2-10.32-2.el8.x86_64
systemd-libs-239-58.el8.x86_64 zlib-1.2.11-18.el8_5.x86_64
(gdb) bt
#0 0x00000000004dfe66 in over_op_func (op=0x7d6b1fffe690, rs=0x7d6b1fffe620,
which=op_modify) at backover.c:749
#1 0x00000000004e0135 in over_op_modify (op=0x7d6b1fffe690, rs=0x7d6b1fffe620)
at backover.c:808
#2 0x000000000046d785 in fe_op_lastbind (op=0x7d6b1010ed40) at bind.c:503
#3 0x000000000046da7f in fe_op_bind_success (op=0x7d6b1010ed40,
rs=0x7d6b1fffe960) at bind.c:548
#4 0x000000000046d1e1 in fe_op_bind (op=0x7d6b1010ed40, rs=0x7d6b1fffe960) at
bind.c:386
#5 0x000000000046c8cd in do_bind (op=0x7d6b1010ed40, rs=0x7d6b1fffe960) at
bind.c:206
#6 0x000000000044427d in connection_operation (ctx=0x7d6b1fffea90,
arg_v=0x7d6b1010ed40) at connection.c:1115
#7 0x000000000044488f in connection_read_thread (ctx=0x7d6b1fffea90,
argv=0x16) at connection.c:1267
#8 0x00007f5f2d60a470 in ldap_int_thread_pool_wrapper (xpool=0xc79d80) at
tpool.c:1053
#9 0x00007f5f2c1a51cf in start_thread () from /lib64/libpthread.so.0
#10 0x00007f5f2be11dd3 in clone () from /lib64/libc.so.6
--
You are receiving this mail because:
You are on the CC list for the issue.
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=9726
Issue ID: 9726
Summary: Admin guide and man pages need better documentation on
disabling syslog
Product: OpenLDAP
Version: 2.6.0
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: ---
2.6.0 added the new feature allowing using a logfile for all debug/loglevel
messages and bypassing syslog entirely. However, there is no documentation on
the new settings or examples of how to do this in the admin guide, and the man
page sections on the new parameters for the logfile side do not note at
when/how they enable bypassing syslog.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9782
Issue ID: 9782
Summary: regression test its8752 failure
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
If a contextCSN update (new cookie) goes from server A through server B to
server C, server C will use that CSN to update entryCSN as well (which neither
A nor B did). This fails the initial replication check.
The issue has likely existed since deltasync was made possible, a version of
this is confirmed at least in 2.4.60 onwards to current master. In principle,
it is related to concerns raised in ITS#9580.
--
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.