https://bugs.openldap.org/show_bug.cgi?id=8113
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8113
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.5.0 |---
Keywords|OL_2_5_REQ |
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8113
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Never mind, bug with the build of OpenLDAP I was using.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8113
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
In fact, for the ldap_get_dn.3.links file, only the first three links are
created, the rest are not:
Links file has:
ldap_explode_dn.3
ldap_explode_rdn.3
ldap_dn2ufn.3
ldap_str2dn.3
ldap_dnfree.3
ldap_dn2str.3
ldap_dn2dcedn.3
ldap_dcedn2dn.3
ldap_dn2ad_canonical.3
on an installation:
[root@tx02 man3]# ls ldap_explode*
ldap_explode_dn.3 ldap_explode_rdn.3
[root@tx02 man3]# ls ldap_dn2ufn*
ldap_dn2ufn.3
[root@tx02 man3]# ls ldap_str2dn.3
ls: cannot access ldap_str2dn.3: No such file or directory
[root@tx02 man3]# ls ldap_dnfree.3
ls: cannot access ldap_dnfree.3: No such file or directory
[root@tx02 man3]# ls ldap_dn2dcedn.3
ls: cannot access ldap_dn2dcedn.3: No such file or directory
(etc)
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8113
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Howard Chu <hyc(a)openldap.org> ---
(In reply to Quanah Gibson-Mount from comment #3)
> It's definitely not fixed.
>
> While it is a part of the ldap_get_dn.3 man page, the installation piece
> that's supposed to create a link to that man page for the ldap_str2dn
> function is not working.
According to commits, this has been in place since 2001. This bug report is
invalid.
Note:
make install DESTDIR=/tmp/xman
...
installing ldap_get_dn.3 in /tmp/xman/usr/local/share/man/man3
installing ldap_explode_dn.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_explode_rdn.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_dn2ufn.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_str2dn.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_dnfree.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_dn2str.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_dn2dcedn.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_dcedn2dn.3 in /tmp/xman/usr/local/share/man/man3 as link to
ldap_get_dn.3
installing ldap_dn2ad_canonical.3 in /tmp/xman/usr/local/share/man/man3 as link
to ldap_get_dn.3
...
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8113
--- Comment #3 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
It's definitely not fixed.
While it is a part of the ldap_get_dn.3 man page, the installation piece that's
supposed to create a link to that man page for the ldap_str2dn function is not
working.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8113
--- Comment #2 from jscott(a)posteo.net ---
This has been fixed. It's in my manpage on Debian Bullseye:
ldap_str2dn() parses a string representation of a distinguished name contained
in str into its components, which are stored in as ldap_ava structures,
arranged in LDAPAVA, LDAPRDN, and LDAPDN terms. Space for dn will be obtained
dynamically and should be freed by the caller using ldap_dnfree(3). The LDAPDN
is defined as:
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9015
--- Comment #10 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• afc970b1
by Howard Chu at 2020-09-15T12:08:22+01:00
ITS#9015 syncprov: fix for zero-length suffix
If the "" glue entry exists and lacks a contextCSN, must perform
an additional search to be sure the DB is otherwise empty. If so,
skip creating the contextCSN.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9338
Issue ID: 9338
Summary: slapd write waiter doesn't resume pending ops
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
If a socket output buffer fills up (e.g. because the client is not reading
responses fast enough) slapd will queue up any newly received operations on
that connection and defer their execution till later. In the new write waiter
code in master/2.5, after the socket becomes writable again the pending ops
are not getting rescheduled for execution because of a missing call to
connection_write(). As a result, a client waiting for these ops on that
connection to finish will be hung forever.
This bug impacts the syncrepl consumer in delta-sync mode if it loses sync and
has to fallback to Refresh mode, and its connection was backlogged on the
provider side. In the fallback case the consumer sends an Abandon for the
current search and issues a new Refresh search, but if the socket was blocked
on the provider side the new search won't execute.
A fix for the write waiter is ready, and also the consumer will be patched to
simply close the connection and open a new one on its fallback, to avoid
running into this problem.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8055
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
Keywords|replication |
Target Milestone|2.5.0 |---
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8055
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Unable to reproduce in current RE24 or master. Seems as though this was fixed
long ago.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7790
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |ryan(a)openldap.org
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8102
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|replication |
Resolution|TEST |FIXED
--- Comment #7 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
RE24:
• 178ca23e
by Howard Chu at 2020-09-09T16:39:15+00:00
ITS#8102 serialize plain syncrepl
Using cs_pmutex. Reverts the addition of cs_modmutex in ITS#9330,
use cs_pmutex for both delta and plain writes.
Note that plain syncrepl already used cs_pmutex when a cookie CSN
was present in the op. Now it is used for all writes, regardless
of presence of cookie.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9323
Issue ID: 9323
Summary: For 2.5, only support OpenSSL 1.0 or later
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Need to abort configure at the least if the OpenSSL release is less than the
1.0.x series when compiling against OpenSSL
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9043
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8102
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Commits:
• e02b1d94
by Howard Chu at 2020-09-09T15:35:59+00:00
ITS#8102 serialize plain syncrepl
Using cs_pmutex. Reverts the addition of cs_modmutex in ITS#9330,
use cs_pmutex for both delta and plain writes.
Note that plain syncrepl already used cs_pmutex when a cookie CSN
was present in the op. Now it is used for all writes, regardless
of presence of cookie.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8102
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.4.54
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8768
--- Comment #7 from OndÅ™ej KuznÃk <ondra(a)mistotebe.net> ---
There is another element to this issue, the consumer that is receiving these
deletes might also be a provider with active persist sessions. It needs to be
able to pass the right information onwards so that its own consumers do not
risk diverging either. I better add some kind of regression test to make sure
this is handled, it might already be fine.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8102
--- Comment #5 from Howard Chu <hyc(a)openldap.org> ---
(In reply to tpretz(a)gmail.com from comment #3)
> When a cookie is not sent with an entry the cs_pmutex is not acquired.
> Without having some protection, non-cookie modifications will race
> each other between syncrepl threads.
>
> So, i am testing surrounding the syncrepl_entry "if" block (line 1036)
> with a cs_pmutex lock/release (when punlock < 0) to serialize
> non_cookie mods just like the cookie ones.
> So far this is running tests and i haven't seen the null_callback
> issue, either when catching up from the session log, or running with
> ongoing out of order writes being replicated (running alongside
> unmodified 2.4.44 to compare differences).
>
> When acquiring the cs_pmutex i have used the same logic as at line 958
> (using trylock, with a shutdown check). I wonder if it is safe to
> acquire the mutex with a standard ldap_pvt_thread_mutex_lock at this
> point without spinning.
Sounds like you've done things correctly. It's not safe to do a normal
mutex_lock here because the wait time could be quite long, and interfere
with other the pool pause or shutdown operations.
We'll be adding the same code now.
>
> line numbers from RELENG_2_4 (721a038b7bc9732f52eeef5324c180c4f137cd75)
>
> Thanks
>
> Tom
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7330
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7330
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|replication |
Target Milestone|2.5.0 |---
Resolution|--- |DUPLICATE
Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
*** This issue has been marked as a duplicate of issue 8427 ***
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8427
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |openldap(a)stormcloud9.net
--- Comment #30 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
*** Issue 7330 has been marked as a duplicate of this issue. ***
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7321
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|replication |
Status|UNCONFIRMED |RESOLVED
Resolution|--- |TEST
--- Comment #1 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Should be fixed (possibly in 2.4 as well at this point). Please test.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6136
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|OL_2_5_REQ, replication |
Resolution|--- |TEST
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Should be fixed with recent changes
--
You are receiving this mail because:
You are on the CC list for the issue.