https://bugs.openldap.org/show_bug.cgi?id=9194
Bug ID: 9194
Summary: slapd-ndb: Remove backend for the 2.5 release
Product: OpenLDAP
Version: 2.5
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: quanah(a)openldap.org
Target Milestone: ---
Remove the slapd-ndb backend for the 2.5 release, as it was never finished and
development on it has ceased.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9191
Bug ID: 9191
Summary: libraries\liblutil\meter.c have a bad function
lutil_meter_update, maybe divide 0
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: digpython(a)163.com
Target Milestone: ---
int
lutil_meter_update (
lutil_meter_t *meter,
size_t position,
int force)
{
static const double display_rate = 0.5;
double frac, cycle_length, speed, now;
time_t remaining_time, elapsed;
int rc;
assert( meter != NULL );
lutil_get_now( &now );
if ( !force && now - meter->last_update < display_rate ) return 0;
frac = ((double)position) / ((double) meter->goal_value);
elapsed = now - meter->start_time;
if (frac <= 0.0) return 0;
if (frac >= 1.0) {
rc = meter->display->display_update(
&meter->display_data,
1.0,
0,
(time_t) elapsed,
((double)position) / elapsed);
} else {
...
}
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=9277
Issue ID: 9277
Summary: restart 3+ providers at once burns CPU forever
Product: OpenLDAP
Version: 2.4.50
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: michael(a)stroeder.com
Target Milestone: ---
I have tiny VMs configured as Æ-DIR servers, 5 providers (multi-provider
replication) and 5 read-only consumers each syncing with all providers.
Restarting all consumers at once simply works, no matter how many of the
providers are up.
Restarting only two providers at once also works.
But when restarting more than two providers at once all of thems seem to hang
eating up CPU.
It could be the same issue like ITS#8650 / ITS#9210 but those only mention
GNUTLS being affected. But all my Æ-DIR test servers run slapd built against
OpenSSL (openSUSE, Debian buster, CentOS7).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9353
Issue ID: 9353
Summary: back-monitor confuses frontendDB with suffix ""
databases
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
If a database is configured with zero length suffix, supplemental monitoring
entries/attributes that are to be registered against that database show up on
the cn=FrontendDB,cn=Databases,cn=Monitor entry instead.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9359
Issue ID: 9359
Summary: syncrepl_op_modify can create invalid mods
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: replication
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
In Delta MPR, if a modify gets delayed in reaching another server and another
(later) modify has already changed that entry, its parts are checked by
syncrepl_op_modify.
Replaces will then be split into a delete+add pairs so they can be resolved
separately, but a bug in mods_dup happily creates an (illegal) empty add if the
replace didn't contain any values.
Fix coming.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9355
Issue ID: 9355
Summary: Delta-sync MPR can fail to recreate entries
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ondra(a)mistotebe.net
Target Milestone: ---
If an entry is missing on one host and a mod for that DN comes in from another,
it should attempt a fallback to retrieve the latest version.
That does not seem to happen in all cases. At least syncrepl_op_modify does not
seem to propagate the error from overlay_entry_get_ov correctly, instead it
ignores the mod and absorbs the CSN.
https://git.openldap.org/openldap/openldap/-/merge_requests/176
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9345
Issue ID: 9345
Summary: Restarted consumer with syncprov may have empty cookie
Product: OpenLDAP
Version: 2.4.52
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
On a relatively fresh node with both syncrepl and syncprov, after some writes
have occurred, if the consumer config is deleted and re-added, it's possible
the consumer won't see the current cookie. On startup it checks the local
database for contextCSN, but if syncprov has been caching cookie updates it may
not have been written to the DB yet. (And on an older server, the contextCSN
may be present in the DB, but stale relative to the state syncprov has cached.)
The consumer calls check_syncprov on subsequent iterations, but it ought to
also call it on startup, just in case.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9352
Issue ID: 9352
Summary: delta-sync SEGV modifying zero-length context entry
Product: OpenLDAP
Version: 2.4.53
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
With a zero-length suffix, the context entry is usually a glue entry. It gets
created without an entryCSN. If an incoming mod updates it, syncrepl will crash
trying to find its entryCSN.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9330
Issue ID: 9330
Summary: Need to fully serialize delta-syncrepl
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: ---
While using delta-syncrepl was supposed to fully serialize updates due to the
use of the accesslog DB, in extremely high write driven environments it became
clear this wasn't entirely the case. This would cause systems to constantly go
into mini REFRESH states as changes came in out of order.
--
You are receiving this mail because:
You are on the CC list for the issue.