openldap-technical

openldap-technical@openldap.org

9897 discussions

Re: OpenLDAP 2.6.0 testing call
by Nick Folino 30 Sep '21

30 Sep '21

Yes. I saw the update and tested it this morning. It's working now as I had previously assumed it would. Nick On Thu, Sep 30, 2021 at 11:38 AM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > > > --On Wednesday, September 29, 2021 7:36 PM -0400 Nick Folino > <nick(a)folino.us> wrote: > > > > > Yes. Logging now continues to work after changes to config. > > > > > > But - adding levels works on the fly, but removing them doesn't. > > For instance this works fine: > > olcLogLevel: stats > > > > > > If I change it to "stats ACL" then the ACL data starts getting added to > > the log. No restart required. > > If I change it back to "stats" I keep getting ACL data until the > > directory is restarted. > > This should now be 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: OpenLDAP 2.6.0 testing call
by Nick Folino 30 Sep '21

30 Sep '21

Yes. Logging now continues to work after changes to config. But - adding levels works on the fly, but removing them doesn't. For instance this works fine: olcLogLevel: stats If I change it to "stats ACL" then the ACL data starts getting added to the log. No restart required. If I change it back to "stats" I keep getting ACL data until the directory is restarted. Nick On Wed, Sep 29, 2021 at 5:49 PM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > > > --On Wednesday, September 29, 2021 9:17 AM -0400 Nick Folino > <nick(a)folino.us> wrote: > > > > > I don't know what the expected results should be, but changing > > olcLogLevel while running causes all logging to the specified file to > > stop. > > > > Logging starts with the new level upon restart. > > This should now be fixed. :) > > --Quanah > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

3 6

Re: OpenLDAP 2.6.0 testing call
by Nick Folino 29 Sep '21

29 Sep '21

Verified. New log options look good on Fedora 34. No issues with tests either. Thanks! Nick On Tue, Sep 28, 2021 at 3:10 PM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > > > --On Friday, September 17, 2021 10:13 AM -0700 Quanah Gibson-Mount > <quanah(a)symas.com> wrote: > > > > > > > --On Tuesday, September 7, 2021 7:07 PM -0400 Nick Folino > > <nick(a)folino.us> wrote: > > > >> > >> Thanks Quanah. olcLogFile and olcLogFileOnly seem to have no effect. > >> Using them I still get logs only to the journal on Fedora 34. > > > > Hi Nick, > > > > I was able to reproduce this and have reopened the issue report. > > This is now fixed for slapd, work pending to fix for lloadd. > > --Quanah > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

2 2

Re: OpenLDAP 2.6.0 testing call
by Nick Folino 28 Sep '21

28 Sep '21

Thanks Quanah. olcLogFile and olcLogFileOnly seem to have no effect. Using them I still get logs only to the journal on Fedora 34. Nick On Tue, Sep 7, 2021 at 5:19 PM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > > > --On Tuesday, September 7, 2021 4:15 PM -0400 Nick Folino <nick(a)folino.us> > > wrote: > > > > > No issues on Fedora 34. Any docs on how to work with the new logging > > options? > > See slapd.conf(5) or slapd-config(5). In slapd.conf(5), search for > "logfile", in slapd-config(5), search for olcLogFile > > > Regards, > Quanah > > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

2 2

RESULT etime vs. qtime
by Michael Ströder 28 Sep '21

28 Sep '21

HI! I'm adapting my mtail program for log-based slapd metrics for release 2.5. 2.5 introduces qtime= and etime= in RESULT lines. Great! I could easily grab histogram metrics for both but that doubles time-series data in Prometheus. So I wonder what's the difference? Is it worth to always look at both? Ciao, Michael.

3 3

delta-sync replication setup
by frederic.goudal＠bordeaux-inp.fr 28 Sep '21

28 Sep '21

Hello, I'm trying to setup delta-sync replication. One difficulty I encounter is that the documentation only refer to the old slapd.conf syntax and not the cn=config one. It is a bit tricky to guess the olc names, objectClass and so on. Is it posssible to update the documentation ? By the way while trying to add the accesslog overlay to my main suffix the slapd daemon stopped with the following syslog entry : slapd[219917]: ch_realloc of 18446744071562067968 bytes failed Slapd 2.5.7 -- Frédéric Goudal Administrateur Systèmes et Réseaux Bordeaux-INP

2 2

struggling with meta_backend, active directory and memberof
by Marco Baiguera 27 Sep '21

27 Sep '21

Hello everyone, I am struggling to make an openldap/meta configuration work: i have two active directory domain/servers: dc=mysite,cd=com and dc=other,dc=mysite,dc=com my goal is to integrate both domains with an application who can integrate with a SINGLE ldap source for user authentication. i'd like to build an openldap meta/proxy to build a virtual tree with mysite.com (empty) --- ou=virtual, dc= mysite,dc =com --- ou=other, dc= mysite,dc =com I'm working with these configuration: database meta suffix "dc=mysite,cd=com" .. uri "ldap://SRV-xxxxxx/ou=virtual, dc= mysite,dc =com" readonly yes lastmod off suffixmassage "ou=virtual, dc= mysite,dc =com" "dc= mysite,dc =com" uri "ldap://SRV-yyyy/ou=other, dc= mysite,dc =com" readonly yes lastmod off suffixmassage "ou=other, dc= mysite,dc =com" "dc=other,dc=mysite,dc=com" The ldap tree is accessible but the group membership is wrong: the value of memberof attributes for every user still has the original value, not the remapped value,for example: cn=user,ou=someou,dc=mysite,cd=com cn=somegroup,ou=groups,dc=mysite,cd=com are seen by the client as cn=user,ou=someou,ou=virtual,dc=mysite,cd=com cn=somegroup,ou=groups,ou=virtual,dc=mysite,cd=com but the membeof attribute of user.someou.mysite.com is cn=somegroup,ou=groups,dc=mysite,cd=com i expect it to be membeof=cn=somegroup,ou=groups,ou=virtual,dc=mysite,cd=com Can someone advice if this is the correct way to address this problem ? Can someone point me to the proper documentation ? Thank you Marco

1 1

Failing while Configuring the OpenLDAP
by Challa N Kumar Reddy 27 Sep '21

27 Sep '21

Hi There, I am new to OpenLDAP and followed the steps mentioned in this quick start guide as it is https://www.openldap.org/doc/admin25/quickstart.html but failing the configuration of OpenLDAP. I followed the below steps on CentOS 8 with 2.5.7 and successfully installed but while configuring facing issues, please correct me if I am doing this in the wrong way. 1. Created a Linux user dedicated to OpenLDAP with the name "nchalla" which has sudo permissions. 2. Login with Root user and created a folder /u01 3. change permissions on /u01 (for time being granted 777 ( 4. change ownership of /u01 to "nchalla" 5. downloaded the tarball and extracted the OpenLDAP 2.5.7 7. downloaded the required developer libraries 8. Logged in as nchalla and navigated to the OpenLDAP 2.5.7 extracted folder and start compiling and installing with the below commands ./configure --prefix=/u01/ldap make depend make make test (all tests were passed) make install 9. Started the configuration following the below steps a. created a folder /u01/ldap/etc/slapd.d b. updated the slapd.ldif with our domain name c. navigate to /u01/ldap and executed the command below, sbin/slapadd -n 0 -F /u01/ldap/etc/slapd.d -l /u01/ldap/etc/openldap/slapd.ldif But getting an error message issue the above command Also , the next step is to start the slapd service but It seems like I couldn't start the service as shown in the below screenshot Please help! Thanks in advance.

2 3

Re: 2.5.7 - help understanding syslog local4
by Dave Macias 23 Sep '21

23 Sep '21

Just to update: by adding to cn=config : olcLogLevel: Stats or loglevel 256 to slapd.conf and with -d 0 and no other change to rsyslog.conf nor to journal.conf I get all my connections, LDAP operations, results logged via syslog to /var/log/slapd/slapd.conf Thank you!!! On Thu, Sep 23, 2021 at 12:23 PM Quanah Gibson-Mount <quanah(a)symas.com> wrote: > --On Thursday, September 23, 2021 6:45 PM +0200 Michael Ströder > <michael(a)stroeder.com> wrote: > > > Personally I have on my systems: > > > > In file /etc/systemd/journald.conf: > > > > [Journal] > > Storage=none > > ForwardToSyslog=yes > > > > In /etc/rsyslog.conf: > > > > $AddUnixListenSocket /dev/log > > > > And I start slapd with -d 0 and loglevel set. > > As a side note, I've encountered deadlocks on RHEL7 on extremely busy > systems when journald is integrated with syslog like this. It also has a > strong negative effect on performance. Whether the deadlock is RHEL7 > specific or not is unknown. > > When OpenLDAP 2.6 releases, syslog (and journald) can be bypassed entirely > and a purely local log file can be used, resulting in a significant > performance increase. > > --Quanah > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

1 0

Uplift from 2.3.20 to 2.4.50
by Viggo Simonsen 23 Sep '21

23 Sep '21

Hi community, I am trying to uplift a very old adaptation of OpenLDAP from 2.3.20 to 2.4.50. I first tried a one-step approach, cherry-picking my delta, based on 2.3.20 into 2.4.50 - but that was a daunting task, given that there is 14 years between the two releases I am now trying again with a step-wise approach, merging one revision at a time from 2.3.20 .. 2.3.43 - and then through the 2.4 releases. So far up to 2.3.43, this has been simple - however now, merging the 2.4 releases, I am facing a huge number of conflicts on nearly all files. It is most certainly due to a lack of ancestry between the 2.4 and 2.3 branches I assume that 2.3 has been merged to master, and 2.4 branched of master at some point, possibly before the 2.3.43 release In short, there is a unclear, and possible collapsed merge path between the 2.3 and 2.4 branches that makes the leap between them difficult Can someone from the development team advise, how I can get about making this transition in a smooth manner? Thanks /Viggo

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical