https://bugs.openldap.org/show_bug.cgi?id=9667
Issue ID: 9667
Summary: 2.6 to 2.7 upgrade documentation
Product: OpenLDAP
Version: unspecified
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: ---
Need to document any upgrade information for going from 2.6 to 2.7
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9665
Issue ID: 9665
Summary: wrong indentation in ldap_int_bisect_find
Product: OpenLDAP
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: libraries
Assignee: bugs(a)openldap.org
Reporter: roland.illig(a)gmx.de
Target Milestone: ---
In abandon.c, ldap_int_bisect_find has an incorrectly indented if statement.
I stumbled upon this due to a lint warning and immediately wondered who forgot
to format the code again, probably after removing a redundant outer if
statement or loop.
The wrong indentation was introduced by
https://git.openldap.org/openldap/openldap/-/commit/2660518c5d924b2b6377a87…
in 2008.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9663
Issue ID: 9663
Summary: Compilation problems: Perl backend
Product: OpenLDAP
Version: 2.5.6
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: jb00356987(a)techmahindra.com
Target Milestone: ---
Dears,
I try to compile 2.5.6 version with --enable-perl module but I get issue as
following :
first I get :
In file included from init.c:18:
perl_back.h:21:10: fatal error: EXTERN.h: No such file or directory
#include <EXTERN.h>
^~~~~~~~~~
compilation terminated.
make[3]: *** [Makefile:334: init.lo] Error 1
I had to install a missing rehl package (perl-devel.x86_64) and set the
CPPFLAGS of the "configure utility" to the path of these header files.
I did run "make clean" and restart the full comilation process then "make" goes
futher but now I get a lot of entries as below then it stopped :
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:50:
undefined reference to `Perl_pop_scope'
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:48:
undefined reference to `Perl_sv_2iv_flags'
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:50:
undefined reference to `Perl_free_tmps'
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:36:
undefined reference to `Perl_stack_grow'
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:34:
undefined reference to `Perl_markstack_grow'
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:35:
undefined reference to `Perl_stack_grow'
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:45:
undefined reference to `Perl_croak_nocontext'
/usr/app/LDAP/binaries/openldap-2.5.6/servers/slapd/back-perl/delete.c:28:
undefined reference to `Perl_croak_nocontext'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:527: slapd] Error 1
Any idea of what's the issue ?
Configure used : ./configure --enable-modules --enable-ldap --enable-dynlist
--enable-ppolicy --enable-unique --with-gnu-ld --enable-refint --with-tls
--enable-dynamic --enable-valsort --enable-perl --enable-rwm
Thx,
Jean-Luc.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9662
Issue ID: 9662
Summary: Error while adding user/group in openldap
Product: OpenLDAP
Version: 2.4.56
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: is3871(a)att.com
Target Milestone: ---
Created attachment 837
--> https://bugs.openldap.org/attachment.cgi?id=837&action=edit
Error details
Error while adding user/group in openldap
adding new entry "dc=ajp,dc=att,dc=com"
ldap_add: Server is unwilling to perform (53)
additional info: no global superior knowledge
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8375
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs_review |
Target Milestone|2.7.0 |2.6.1
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8255
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.7.0 |2.6.1
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9651
Issue ID: 9651
Summary: Add some kind of rate limiting option to ldapmodify
Product: OpenLDAP
Version: 2.5.6
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: hyc(a)openldap.org
Target Milestone: ---
When using ldapmodify to replay a testing workload it would be useful to be
able to specify a request rate, instead of just performing multiple operations
in immediate succession. As a simpler alternative, just being able to specify a
time interval between operations would be helpful.
As an even greater future enhancement, it would be nice to have an option to
replay an accesslog.ldif directly, using its embedded timestamps to control the
time interval between operations. Currently this isn't feasible since reqstart
timestamps only have 1-second granularity, the fraction part is a linear
counter and not a microsecond value. The reqStart fraction would need to be
extended to 9 decimal places with full nanosecond resolution in order to be
usable as actual fractional time. We already know that microsecond resolution
is insufficient to avoid frequent collisions.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9661
Issue ID: 9661
Summary: How to monitor an LDMB file for being pretty full
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
https://ltb-project.org/documentation/nagios-plugins/check_lmdb_usage provides
a Nagios plugin, to check how full/free a LMDB database is. It calls mbd_stat
-ef, and parses from the output the numbers in the “Max pages:”, “Number of
pages used:”, and “Free pages:” lines.
With these numbers it calculates “the percent of used pages” or “the percent of
free pages” and signals the status with return values 0 -OK, 1 - warning, or 2
- critical . The disadvantage of check_lmdb_usage is, that it requires perl.
Do you recommend to monitor the absolute number of free pages, the relative
number of free pages, the absolute number of used pager, or the relative number
of used pages?
Please extend mdb_stat to be suitable for monitoring the fullness of a LMDB
directory - accept parameters of for a warning and critical threshold, and a
parameter on how to calculate the criterion (A - based on absolute number of
free pages, B - relative number of free pages, C - absolute number of used
pages, or D - relative number of used pages).
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8375
--- Comment #7 from geert.hendrickx(a)telenetgroup.be <geert.hendrickx(a)telenetgroup.be> ---
I can reproduce it on any sufficiently large db, both tree-structured or flat,
given the right search scope.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8375
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs_review
--- Comment #6 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
I'll put needs review on it though so we can discuss. ;)
--
You are receiving this mail because:
You are on the CC list for the issue.