openldap-devel

openldap-devel@openldap.org

1416 discussions

RE: RE24 testing call #1 (2.4.45) LMDB RE0.9 testing call #1 (0.9.20)
by Quanah Gibson-Mount 20 Jan '17

20 Jan '17

--On Friday, January 20, 2017 6:51 PM +0100 Dieter Klünter <dieter(a)dkluenter.de> wrote: > $ make its > Testing (available) ITS regressions > make[1]: Verzeichnis „/home/dieter/build/openldap/tests" wird betreten > run configure with --enable-bdb to run BDB tests > make[1]: Verzeichnis „/home/dieter/build/openldap/tests" wird > verlassen make[1]: Verzeichnis „/home/dieter/build/openldap/tests" > wird betreten run configure with --enable-hdb to run BDB tests > make[1]: Verzeichnis „/home/dieter/build/openldap/tests" wird > verlassen make[1]: Verzeichnis „/home/dieter/build/openldap/tests" > wird betreten run configure with --enable-mdb to run BDB tests > make[1]: Verzeichnis „/home/dieter/build/openldap/tests" wird > verlassen Thanks, fixed. :) --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

RE: RE24 testing call #1 (2.4.44) LMDB RE0.9 testing call #1 (0.9.20)
by Dieter Klünter 20 Jan '17

20 Jan '17

Datum: Thu, 19 Jan 2017 21:33:18 +0100 Von: Dieter Klünter <dieter(a)dkluenter.de> An: openldap-devel(a)openldap.org Betreff: Re: RE24 testing call #1 (2.4.44) LMDB RE0.9 testing call #1 (0.9.20) Am Wed, 18 Jan 2017 18:05:21 -0800 schrieb Quanah Gibson-Mount <quanah(a)symas.com>: > For this testing call, we particularly need folks to test OpenLDAP > with startTLS/LDAPS when compiled against OpenSSL (both pre 1.1 > series and with the 1.1 series). There is currenly nothing in the > test suite that covers encrypted connections (Although it's on my > todo list). To build against OpenSSL 1.1 may also require cyrus-sasl > HEAD out of the cyrus-sasl GIT repository, depending on your build > options as the current cyrus-sasl release does not support the > OpenSSL 1.1 series. It can be found at > <https://github.com/cyrusimap/cyrus-sasl>. If you build with GSSAPI > and use Heimdal, you will also need the Heimdal 7.1.0 or later > release (as that is where OpenSSL 1.1 support was added). It can be > obtained from <http://h5l.org/>. > > Also new with this release is the ability to run "make its" in the > tests/ directory. This will run a specific set of tests around past > bugs to ensure there are no regressions. While I've tested this with > modular openldap builds, it has not been tested with the modules and > backends built into slapd, so there could be some issues in that > scenario. my configure: --enable-bdb=no \ --enable-hdb=no \ --enable-mdb=yes \ these are the issues: $ make its Testing (available) ITS regressions make[1]: Verzeichnis „/home/dieter/build/openldap/tests“ wird betreten run configure with --enable-bdb to run BDB tests make[1]: Verzeichnis „/home/dieter/build/openldap/tests“ wird verlassen make[1]: Verzeichnis „/home/dieter/build/openldap/tests“ wird betreten run configure with --enable-hdb to run BDB tests make[1]: Verzeichnis „/home/dieter/build/openldap/tests“ wird verlassen make[1]: Verzeichnis „/home/dieter/build/openldap/tests“ wird betreten run configure with --enable-mdb to run BDB tests make[1]: Verzeichnis „/home/dieter/build/openldap/tests“ wird verlassen -Dieter -- Dieter Klünter | Systemberatung https://sys4.de GPG Key ID:DA147B05 53°37'09,95"N 10°08'02,42"E -- Dieter Klünter | Systemberatung http://dkluenter.de GPG Key ID:DA147B05 53°37'09,95"N 10°08'02,42"E

1 0

Re: OpenLDAP: syslog message not readability
by Quanah Gibson-Mount 04 Nov '16

04 Nov '16

--On Friday, October 21, 2016 8:24 PM +0300 Karatas Ozgur <mueddib(a)openldap.org> wrote: > This style a very primitive coding method, I know, sorry. > I'm waiting for help on how to Git. Hi Ozgur, That is a tag for the "what" command. It will not be removed. See <https://en.wikipedia.org/wiki/Source_Code_Control_System> for more information. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

OpenLDAP: syslog message not readability
by Karatas Ozgur 21 Oct '16

21 Oct '16

Hello all, How are you? We have installed to OpenLDAP server a few days ago and referred server logs to logserver. But couldn't not read to OpenLDAP log on the logserver. Logserver record all log to database and send e-mailing. Example: Oct 21 10:54:23 ldapserver slapd[1595]: @(#) $OpenLDAP: slapd 2.4.44 (Oct 21 2016 10:49:33) $#012#011mueddib@ldapserver:/home/mueddib/openldap-2.4.44/servers/slapd Oct 21 10:54:23 ldapserver slapd[1596]: mdb_monitor_db_open: monitoring disabled; configure monitor database to enable Oct 21 10:54:23 ldapserver slapd[1596]: slapd starting For example unnecessary rows: "@(#)" " $#012#011" I fixed it but I couldn't commit to git :) # git status On branch master Your branch is up-to-date with 'origin/master'. Changes to be committed: (use "git reset HEAD <file>..." to unstage) modified: build/mkvers.bat modified: build/mkversion # git push origin master fatal: remote error: access denied or repository not exported: /openldap.git # git push origin origin fatal: remote error: access denied or repository not exported: /openldap.git I don't know why don't have access to OpenLDAP Git Server (I would like your help). Please can you fix the below code? File: /build/mkvers.bat from: (echo "@(#) $" OPENLDAP_PACKAGE ": %3 " OPENLDAP_VERSION) >> %2 (echo " (" __DATE__ " " __TIME__ ") $\n") >> %2 (echo "\t%USERNAME%@%COMPUTERNAME% %CD:\=/%\n";) >> %2 to (please): (echo OPENLDAP_PACKAGE ": %3 " OPENLDAP_VERSION) >> %2 (echo " (" __DATE__ " " __TIME__ ") \n") >> %2 (echo "%USERNAME%@%COMPUTERNAME% %CD:\=/%\n";) >> %2 File: /build/mkversion from: $static $const char $SYMBOL[] = "@(#) \$$PACKAGE: $APPLICATION $VERSION (" __DATE__ " " __TIME__ ") \$\n" "\t$WHOWHERE\n"; to (please): $static $const char $SYMBOL[] = "$PACKAGE: $APPLICATION $VERSION (" __DATE__ " " __TIME__ ") \n" "$WHOWHERE\n"; This style a very primitive coding method, I know, sorry. I'm waiting for help on how to Git. Regards, -- Ozgur Karatas E: mueddib(a)openldap.org T: https://twitter.com/openldaporg F: http://facebook.com/openldap D: https://hub.docker.com/r/openldap/ G: https://github.com/openldap/

1 0

ITS8511 feedback
by Quanah Gibson-Mount 11 Oct '16

11 Oct '16

I've prepared a patch for ITS8511, that deprecates mirrormode/olcMirrorMode. I'd like to include it as part of the 2.5 release. What it does is rename the configuration parameter to be "multimaster" or olcMultiMaster. This changes makes the configuration reflect what is actually being done when this mode is enabled (set to TRUE). Mirrormode itself is a concept completely external to the openldap configuration (i.e., it's based off of some sort of load balancing configuration), and the current usage of the term mirrormode is misleading and leads to significant confusion. While we can update the docs in various ways, I believe the configuration term should accurately reflect what's is occurring when it is enabled. The current method simply leads to unnecessary confusion and is misleading. One potential issue is that it does change the cn=config schema. However, we've done this before when deprecating keywords. pcache.c is an example of where this has been done in the past. I've validated that my change is 100% backwards compatible, so that existing configurations continue to work. Thoughts welcome. Regards, Quanah -- Quanah Gibson-Mount Product Engineer Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: back-llog
by Howard Chu 09 Aug '16

09 Aug '16

Michael Ströder wrote: > Howard Chu wrote: >> Michael Ströder wrote: >>> Howard Chu wrote: >>>> Was just thinking we could do a quite simple backend for use with the accesslog >>>> overlay and delta-syncrepl. It would write into flat files and do typical >>>> logfile rotation on its own. The backing store would have a minimum of two files >>>> - one for the suffix entry, one for the current chunk of logs. There would be a >>>> configurable number of logfiles, with the oldest simply being deleted when it's >>>> time to purge. >>> >>> Two things I'd consider helpful for long-time archiving/auditing: >>> >>> 1. filenames to allow of "merging" different log flat files into one big file >>> store on a different slapd instance. >> >> Not sure what you mean by this. As sequential logs you could just cat them if >> you want to combine files into one, what does the filename have to do with it? > > Sorry for unclear wording. > I'd like to move archived files of all MMR replicas into another single > filesystem directory and let a special auditing slapd with back-llog search in > them without having to muck with file names. Then you would have to merge them entry-by-entry to preserve chronological order. >> If we just use datestamps for filenames YYYYMMDD it should be no problem for you >> to cat them in proper order. > > There could be conflicting timestamps from different MMR replicas. Maybe > appending the serverID could be a solution? Just keep them all in their own separate filesystem directories. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 1

Re: back-llog
by Howard Chu 09 Aug '16

09 Aug '16

Michael Ströder wrote: > Howard Chu wrote: >> Was just thinking we could do a quite simple backend for use with the accesslog >> overlay and delta-syncrepl. It would write into flat files and do typical >> logfile rotation on its own. The backing store would have a minimum of two files >> - one for the suffix entry, one for the current chunk of logs. There would be a >> configurable number of logfiles, with the oldest simply being deleted when it's >> time to purge. > > Two things I'd consider helpful for long-time archiving/auditing: > > 1. filenames to allow of "merging" different log flat files into one big file > store on a different slapd instance. Not sure what you mean by this. As sequential logs you could just cat them if you want to combine files into one, what does the filename have to do with it? If we just use datestamps for filenames YYYYMMDD it should be no problem for you to cat them in proper order. > 2. instead of deleting moving files to an archive directory. Sounds fine as an option. > I know it's a different use-case but quite handy. > > Ciao, Michael. > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 1

back-llog
by Howard Chu 09 Aug '16

09 Aug '16

Was just thinking we could do a quite simple backend for use with the accesslog overlay and delta-syncrepl. It would write into flat files and do typical logfile rotation on its own. The backing store would have a minimum of two files - one for the suffix entry, one for the current chunk of logs. There would be a configurable number of logfiles, with the oldest simply being deleted when it's time to purge. It would only support Add/Search in general, and Modify on the suffix entry. A rolling append-only format like this would allow much higher throughput for accesslog recording. Using a binary entry format would of course also help. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 1

Any update on LMDB support for OpenBSD?
by Tinker 12 Jun '16

12 Jun '16

Hi Howard, Any plan on making LMDB work on OpenBSD? OpenBSD should deliver LMDB in the MDB_WRITEMAP mode. (http://lmdb.tech/doc/group__mdb.html) (At least some effort has been done e.g. https://gitlab.com/mdb/sqlightning/issues/6 ) Thanks, Tinker

2 2

When must slap_callback.sc_writewait be set?
by Hallvard Breien Furuseth 09 Jun '16

09 Jun '16

When is it safe to leave sc_writewait uninitialized? The field seems to have emerged in the middle of RE24, and I don't see any flags which say it should/should not be used. Since not setting it crashed back-relay in ITS#8428, does that mean everything which creates a slap_callback should set it? Seems unfortunate for third-party modules... Also, I think this should be documented. -- Hallvard

3 12

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel