https://bugs.openldap.org/show_bug.cgi?id=6097
--- Comment #4 from OndÅ™ej KuznÃk <ondra(a)mistotebe.net> ---
So testing confirms the systems converge right now, extremely noisily (the add
or delete fails, we go into refresh, etc.) but things settle in the right way
(the parent is removed (made into glue) and the child remains. There are
situation where is fails but those are bugs (to be) filed separately.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9628
Issue ID: 9628
Summary: Incorrect handling of c_n_ops_executing counter when
using an asynchronous backend (back-asyncmeta)
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: nivanova(a)symas.com
Target Milestone: ---
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9611
Issue ID: 9611
Summary: no structural objectclass in configuration table
Product: OpenLDAP
Version: 2.5.5
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: jb00356987(a)techmahindra.com
Target Milestone: ---
Dears,
When I tried to start sldap 2.5.5 I get following error :
60eff599.06749e9d 0x7fb62750f740 <<< dnNormalize: <cn=manager,cn=config>
60eff599.0674bad5 0x7fb62750f740 <= str2entry(cn=module{0}) -> 0x1193828
60eff599.06752650 0x7fb62750f740 : config_add_internal:
DN="cn=module{0},cn=config" no structural objectClass in configuration table
60eff599.06753c3c 0x7fb62750f740 config error processing
cn=module{0},cn=config:
60eff599.0675a8bc 0x7fb62750f740 send_ldap_result: conn=-1 op=0 p=0
60eff599.067611e4 0x7fb62750f740 build-corp-M1 destroy: freeing system
resources.
60eff599.06767673 0x7fb62750f740 slapd stopped.
60eff599.06770970 0x7fb62750f740 connections_destroy: nothing to destroy.
I don't understand why I get it as I'm able to run slapd 2.4.59 with same
config/DB.
Can you advice ?
Thx,
J-L.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9569
Issue ID: 9569
Summary: objectClass Violation with lastbind and delta-syncrepl
Product: OpenLDAP
Version: 2.4.58
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: gnoe(a)symas.com
Target Milestone: ---
If olcLastBind is set to true in a delta-syncrepl environment, slapd fails to
add auditModify entries for lastbind to the accesslog due to an objectClass
violation. The auditModify object lacks the required reqMod attributes. The
lastbind module is not in use. The ppolicy overlay is also in use. It shows in
the slapd log as:
Jun 03 13:05:34 l-02992-d5a slapd[18715]:
Entry(reqStart=20210603170529.000262Z,cn=accesslog): object class 'auditModify'
requires attribute 'reqMod'
Jun 03 13:05:34 l-02992-d5a slapd[18715]: accesslog_response: got result 0x41
adding log entry reqStart=20210603170529.000262Z,cn=accesslog
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9625
Issue ID: 9625
Summary: ppolicy: spamming log
Product: OpenLDAP
Version: 2.5.6
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: overlays
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Noticed on a few recent deployments that ppolicy is spamming the logs with:
ppolicy_bind: Setting warning for password expiry <DN> = 0 second
on every bind. Haven't noticed this in the past but the code has been like
this since 2004.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9624
Issue ID: 9624
Summary: Issues in client state tracking
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: ---
There are two places that don't track client state (BINDING/OPEN) correctly:
- handle_one_request() reads c_state/c_io_state without holding the appropriate
mutex
- operation_unlink_client() assumes that if state is BINDING, the operation
we're just unlinking is a bind request. However the client could have sent
another operation without waiting for the bind response, we shouldn't touch
state when disposing of those
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9549
Issue ID: 9549
Summary: ldapvc needs a man page
Product: OpenLDAP
Version: 2.5.4
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: ryan(a)openldap.org
Target Milestone: ---
The ldapvc tool was added in 2.5, but there is no man page for it yet.
I've opened this as a separate ITS, rather than append to ITS#9284, because
ldapvc is not in contrib and is always installed.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9443
Issue ID: 9443
Summary: Admin guide: Need section on lloadd and load balancer
as slapd module
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: blocker
Priority: ---
Component: documentation
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
The admin guide currently has no documentation on the new lloadd daemon or the
ability to set up the load balancer as a module inside of slapd. This is a
release requirement.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9637
Issue ID: 9637
Summary: back-mdb idlexp max is 30, not 31
Product: OpenLDAP
Version: 2.5.6
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
Even so, it's ridiculous to use 2 billion slot IDLs (16GB each) unless you have
hundreds of GB of RAM.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9630
Issue ID: 9630
Summary: back-sql leaves db transaction open after a bind or
search operation
Product: OpenLDAP
Version: 2.4.58
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: aapo.romu(a)eficode.com
Target Milestone: ---
Created attachment 833
--> https://bugs.openldap.org/attachment.cgi?id=833&action=edit
Close transactions after bind or search operation
back-sql leaves db transaction open after a bind or search operation. This
prevents ie. PostgreSQL to perform VACUUM operations and seems also contribute
to decreased performance.
--
You are receiving this mail because:
You are on the CC list for the issue.