https://bugs.openldap.org/show_bug.cgi?id=8882
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|IN_PROGRESS |RESOLVED
--- Comment #16 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
head:
• d2057745
by Ondřej Kuzník at 2022-05-10T14:24:49+00:00
ITS#8882 Add slapo-emptyds to contrib
RE26:
• edc67c6d
by Ondřej Kuzník at 2022-05-12T15:45:18+00:00
ITS#8882 Add slapo-emptyds to contrib
RE25:
• 6c9cb00f
by Ondřej Kuzník at 2022-05-12T15:46:13+00:00
ITS#8882 Add slapo-emptyds to contrib
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9843
Issue ID: 9843
Summary: slapcat and slapadd have no -r option
Product: OpenLDAP
Version: 2.5.12
Hardware: All
OS: Linux
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
I run openldap in a chrooted environment, by calling
/usr/local/libexec/slapd -d0 -u openldap -r /home/openldap -F /etc/openldap/ -h
'ldap://zzz'
I want to migrate 2.5 → 2.6. The manual says first to call slapcat on the
databases. In the /home/openldap/etc/openldap directory are the configurations
of the databases. The path there:
olcDbDirectory: /var/openldap-data/yyy
obviously references the path within the chrooted environment, the path is
/home/openldap/var/openldap-data/yyy outside the chrooted environment.
Slapcat has no -r option. So there is no way to export the databases by using
slapcat -n 0 -F /home/openldap/etc/openldap/ . Strace(1) shows that the file
openat(AT_FDCWD, "/var/openldap-data/yyy/DUMMY"
is missing and the error message is
slapcat: bad configuration directory!
In fact there is a way: symlinking /var/openldap-data outside the chrooted
environment to /var/openldap-data inside the chrooted environment. This way
does work, but it requires expert magic like using strace.
Please add -r option to slapcat and slapadd, which performs chroot to the
directory, after opening the file specified by the -l parameter.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9702
Issue ID: 9702
Summary: slapadd is missing -r chroot option
Product: OpenLDAP
Version: 2.5.7
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: dpa-openldap(a)aegee.org
Target Milestone: ---
I want to run slapd under chroot with the -r option. In order to initialize
the setup, I want to use `slapadd -n0 configuration.ldif`. The configuration
file contains mdb databases and these databases have `olcDbDirectory: ` paths.
Since slapd will load the databases from the chroot environment, the directory
names must be submitted to slapadd to be correct in the chroot environment.
This means, that outside the chroot environment the directory paths are not
correct.
When I call `slapadd -n0 ` I get the error
olcDbDirectory: value #0: invalid path: No such file or directory
slapadd: could not add entry dn="olcDatabase={1}mdb,cn=config" (line=909):
Closing DB...
which means, that slapadd cannot open (outside the chrooted environment) the
olcDbDirectory path. Thus slapadd shall first enter the chrooted environment,
but it lacks option for this. Probably slapcat will also need this option to
dump the databases.
The chrooted environment is created specially for openldap, so it contains no
tools.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9845
Issue ID: 9845
Summary: slapd Deamon is Crashed on OpenVMS_x86
Product: OpenLDAP
Version: 2.5.7
Hardware: x86_64
OS: Other
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: client tools
Assignee: bugs(a)openldap.org
Reporter: jeetu.singh(a)aol.com
Target Milestone: ---
CH2105_SYSTEM> @SYS$COMMON:[SYS$STARTUP]LDAP$STARTUP.COM;
%RUN-S-PROC_ID, identification of created process is 20E0043A
CH2105_SYSTEM> sho time
11-MAY-2022 06:09:20
CH2105_SYSTEM> sho proc/id=20E0043A
%SYSTEM-W-NONEXPR, nonexistent process
CH2105_SYSTEM> ty ldap$varroot:[run]slapd.log;
$ runcmd = "$ldap$bin:slapd.exe"
$ dbglvl = f$trnlnm("LDAP$DEBUG")
$ if dbglvl .nes. "" then runcmd = "$ldap$bin:slapd.exe -d "
$ runcmd
%DEBUGBOOT-W-EXPGFLQUOTA, exceeded pagefile quota
%SYSTEM-W-EXIT_UNWIND, exit unwind currently in progress
SYSTEM job terminated at 11-MAY-2022 06:09:17.86
Accounting information:
Buffered I/O count: 778 Peak working set size: 44368
Direct I/O count: 117 Peak virtual size: 962112
Page faults: 3447 Mounted volumes: 0
Charged CPU time: 0 00:00:00.38 Elapsed time: 0 00:00:00.50
Please let me know if any further input needed.
Request to provide "How to configure OpenLDAP on OpenVMS_x86 Environment"
Manual.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9745
Issue ID: 9745
Summary: Local Logging - Timestamp Formatting
Product: OpenLDAP
Version: 2.6.0
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: gnoe(a)symas.com
Target Milestone: ---
Timestamps for log lines in the 2.6+ local logging feature are saved
unformatted (ex: "618ae741.0f6eb63a"). This has the potential to break any log
aggregation/analysis program like splunk that expect timestamps in syslog
format.
These timestamps should configurable in various syslog formats.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9403
Issue ID: 9403
Summary: add option to completely disable syslog logging
Product: OpenLDAP
Version: 2.4.45
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: cvuillemez(a)yahoo.fr
Target Milestone: ---
For auditing purpose, I need to enable "stats" loglevel.
So on heavy load, slapd send lots of events to local syslog socket /dev/log,
when compiled with LDAP_SYSLOG (on Debian / Ubuntu).
It worked fine on old systems with a simple syslog service.
But when upgrading on system with journald+syslog, CPU "overhead" becomes
totally crazy.
It would be great to have an option at run time to completely disable syslog
logging, or/and use a cutom socket, e.g. /run/systemd/journal/syslog to bypass
journald service.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=6949
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cvuillemez(a)yahoo.fr
--- Comment #23 from Quanah Gibson-Mount <quanah(a)openldap.org> ---
*** Issue 9403 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=9844
Issue ID: 9844
Summary: Monitoring your SEO strategy is essential
Product: website
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: website
Assignee: bugs(a)openldap.org
Reporter: guptaaaron29(a)gmail.com
Target Milestone: ---
Monitoring your SEO strategy is essential to measure the success of your
website. Fortunately, with the tools available today, it is possible to count
all the variables to formulate new tactics or improve existing plans. Whether
you need to analyze traffic, potential customers, keyword rankings, among other
indicators, by using metrics, you will be able to obtain all the important
information you need to know the actual performance of your strategy and
improve SEO ranking.
https://ghareluupcharinhindi.com/diabetes-ke-lakshan/
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9842
Issue ID: 9842
Summary: Page should not be spilled if MDB_RESERVE is used
Product: LMDB
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: needs_review
Severity: normal
Priority: ---
Component: liblmdb
Assignee: bugs(a)openldap.org
Reporter: stephan.j.bircher(a)gmail.com
Target Milestone: ---
The documentation for the function mdb_cursor_put states for MDB_RESERVE the
following: "return a pointer to the reserved space, which the caller can fill
in later".
However this seems only to be valid if no other operation is performed on the
cursor. Once the cursor is moved the page where the reserved data resides on
might become untracked and therefore eligible to be spilled at any time.
This problems occurrs however only for large transactions where lmdb starts to
spill and flush pages.
I'm using only lmdb and I'm a bit confused as the branches master
(https://git.openldap.org/openldap/openldap/-/tree/master/libraries/liblmdb)
and mdb.master
(https://git.openldap.org/openldap/openldap/-/tree/mdb.master/libraries/libl…)
are not the same.
For example the function mdb_pages_xkeep differs and master and mdb.master.
Will the branches be consolidated again?
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8882
Ondřej Kuzník <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Null Attribute Value |Empty Directory String
|Overlay |Overlay
--
You are receiving this mail because:
You are on the CC list for the issue.