https://bugs.openldap.org/show_bug.cgi?id=9009
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |10274
Referenced Issues:
https://bugs.openldap.org/show_bug.cgi?id=10274
[Issue 10274] Replication issue on MMR configuration
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8890
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |TEST
--- Comment #20 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
• 8584c582
by Steve Langasek at 2026-04-05T19:30:39+00:00
ITS#8890 Handle sizeof(time_t) > sizeof(long) in format strings
64-bit time_t means that on some architectures, time_t is now larger
than a long, and making some references in format strings incorrect.
To avoid truncation or other size mismatch issues, always cast to a long
long and read using %lld.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10475
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |ondra(a)mistotebe.net
Keywords|needs_review |
Target Milestone|--- |2.6.14
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10476
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |ondra(a)mistotebe.net
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10476
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.6.14
Group|OpenLDAP-devs |
Keywords|needs_review |
--- Comment #2 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
Not a security issue, CVE unnecessary.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10475
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |---
Status|RESOLVED |UNCONFIRMED
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10477
Issue ID: 10477
Summary: Reopening LMDB environment clears MDB_MAP_FULL error
Product: LMDB
Version: 0.9.33
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: david.komarek(a)whalebone.io
Target Milestone: ---
Hello,
We are using LMDB from multiple processes. One process performs writes, while
several other processes (typically 4–12, depending on the number of CPUs) read
from the same environment. The environment contains multiple (6) databases, and
on average we write approximately 150 records per second.
After some time, we begin encountering MDB_MAP_FULL errors on every write
operation. Interestingly, after reopening the environment in the writer
process, the error disappears and writing resumes successfully.
Our configured map size is 4 GB, and we have not implemented any resizing
strategy. Based on our observations, this does not seem strictly necessary, as
there appears to be sufficient free space after reopening the environment.
Reader processes do not keep read transactions open for long periods. We reset
transactions using mdb_txn_reset after each read operation and reuse them via
mdb_txn_renew.
The environment is open with following flags for writing: MDB_WRITEMAP |
MDB_NOTLS | MDB_NORDAHEAD | MDB_NOSYNC and for reading: MDB_RDONLY | MDB_NOTLS
| MDB_NORDAHEAD.
Could you please help us understand what might be causing this behavior and how
we can prevent MDB_MAP_FULL errors without needing to reopen the environment?
Thank you in advance.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10475
--- Comment #3 from OndÅ™ej KuznÃk <ondra(a)mistotebe.net> ---
On Tue, Mar 31, 2026 at 02:15:26PM +0000, openldap-its(a)openldap.org wrote:
> slapo-constraint is not a security control mechanism, it is a value control
> mechanism. ACLs are used to control access.
>
> There is no issue here.
If as they report, the overlay mistakenly allows one to store values not
listed in the appropriate entry, it's still a valid issue.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10475
Howard Chu <hyc(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Group|OpenLDAP-devs |
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Howard Chu <hyc(a)openldap.org> ---
slapo-constraint is not a security control mechanism, it is a value control
mechanism. ACLs are used to control access.
There is no issue here.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=10394
Issue ID: 10394
Summary: remove stroeder.com from support page
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
HI!
for health reasons I gave up my business and I have retired . So it does no
longer make sense to be listed on the support page.
Ciao, Michael.
--
You are receiving this mail because:
You are on the CC list for the issue.