openldap-technical

openldap-technical@openldap.org

5 participants
9899 discussions

[openLDAP 2.5] slapd silently stops
by BECOT Jérôme 13 Jun '24

13 Jun '24

Hello, We have to servers configured as Proxy with back_ldap. They stop almost everyday with a SIGABRT in the service log. Nothing in the standard logs when they stop. I'd like to increase the log level to args, but I'm not sure if it would help me. Any help appreciated. Regards Jerome

2 1

GSSAPI Support from 2.4.x to 2.5.x
by bowen.wang＠cohesity.com 05 Jun '24

05 Jun '24

In 2.4.x, openldap have gssapi.c and several apis on GSSAPI while that is not there anymore after 2.5.x. So what API should use if I want to achieve the same logic such as api ldap_gssapi_bind_s/ldap_gssapi_bind in 2.4.x?

2 1

[OpenLDAP 2.5] Accesslog size and performance issues
by BECOT Jérôme 27 May '24

27 May '24

Hello, Here is our setup: 2 master in mirrormode with accesslog replication and several slaves with lastbind and chain overlay. Everything works, but the accesslog db is quite large and filled with authtimestamp updates from client hosts running sssd. We also have a disk performance issue when the cleanup process is launched every 4h. We plan to reduce the accesslog history by setting 12h retention and increase cleanup . It should reduce the number of entries and therefore lighten the cleanup process but: I wonder if increasing the frequency will also have a positive effects (as the though here is that there will be less entries to delete). I think that allocated pages in the mdb database won't change. Is there a safe way to reduce the db size ? Finally, we considered not logging the sssd auth timestamp updates, but lastbind doesn't have any option to filter which branch is allowed to update, the only option is to set the precision to a higher value. Is there a way to achieve this ? Any suggestion will be warmly appreciated. Thank you Jerome

4 7

its8752 failure
by patrick+openldap.org＠laimbock.com 26 May '24

26 May '24

Hi all, Almalinux 9.4 x86_64. When building 2.6.8 with gcc 11.4.1 20231218 (Red Hat 11.4.1-3) or gcc 13.2.1 20231205 (Red Hat 13.2.1-6) I get a failure in 'make -j1 its' in its8752: >>>>> Starting its8752 ... running defines.sh This test tracks a case where slapd deadlocks during a significant write load See https://bugs.openldap.org/show_bug.cgi?id=8752 for more information. Starting slapd on TCP/IP port 9011... Using ldapsearch to check that slapd is running... Populating database on first provider... Stopping slapd and reworking configuration for MPR... Starting provider slapd on TCP/IP URI ldap://localhost:9011/ Using ldapsearch to check that provider slapd is running... Starting provider slapd on TCP/IP URI ldap://localhost:9012/ Using ldapsearch to check that provider slapd is running... Starting provider slapd on TCP/IP URI ldap://localhost:9013/ Using ldapsearch to check that provider slapd is running... Starting provider slapd on TCP/IP URI ldap://localhost:9014/ Using ldapsearch to check that provider slapd is running... Setting up accesslog on each provider... Modifying dn: cn=Elmer_Fudd,ou=People,dc=example,dc=com on provider 1 Modifying dn: cn=Elmer_Fudd,ou=People,dc=example,dc=com on provider 2 Modifying dn: cn=Elmer_Fudd,ou=People,dc=example,dc=com on provider 3 Modifying dn: cn=Elmer_Fudd,ou=People,dc=example,dc=com on provider 4 Waiting 7 seconds for servers to catch up... Waiting 7 seconds for servers to catch up... Waiting 7 seconds for servers to catch up... Waiting 7 seconds for servers to catch up... Waiting 7 seconds for servers to catch up... Waiting 7 seconds for servers to catch up... Servers did not replicate in time >>>>> ./data/regressions/its8752/its8752 failed (exit 1) make[1]: Leaving directory '/builddir/build/BUILD/openldap-2.6.8/tests' make[1]: *** [Makefile:364: mdb-its-yes] Error 1 make: *** [Makefile:355: regressions] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.cKP3aW (%check) Looking at its8752 in bugzilla there is a target of 2.7.0 and there are a number of other ITSs mentioned: https://bugs.openldap.org/show_bug.cgi?id=9782 (confirmed) https://bugs.openldap.org/show_bug.cgi?id=9580 (in progress) https://bugs.openldap.org/show_bug.cgi?id=9341 (unconfirmed) Is this test supposed to pass successfully on 2.6.8? Thanks, Patrick

1 0

el9 bind ip address
by Marc 24 May '24

24 May '24

Anyone know if this file is still working in el9? Looks like if I put SLAPD_URLS it is not read. /etc/sysconfig/slapd

4 7

Unable to enable auditlog in openldap 2.4
by kalybox2020＠gmail.com 20 May '24

20 May '24

We are using cn=config file for configuration. Using ldapmodify dn: olcOverlay={8}auditlog,olcDatabase={1}hdb,cnc=config objectclass: olcOverlayConfig objectClass: olcAuditlogConfig olcAuditLogFile: /var/log/ldapauditlog.ldif restarted slapd, Gave permissions to this file, and restarted slapd, still not able to generate logs. Thanks -Kaly

1 0

How to setup replication in openldap 2.6.7
by kalybox2020＠gmail.com 20 May '24

20 May '24

How to setup replication in openldap 2.6.7 Please let me know Thanks -Kaly

3 2

Facing issues with Symas LDAP upgrade from 2.4 to 2.5
by anilkumar.pathuri7＠gmail.com 16 May '24

16 May '24

Hi Team, GM Successful while trying to upgrade from openLDAP 2.4.44 to SymasLDAP2.4.57 Facing issues while trying to upgrade to 2.5.x and 2.6.x from SymasLDAP2.4.57 https://repo.symas.com/soldap2.5/upgrading/ Issues while trying to upgrade from SymasLDAP2.4.57 to SymasLDAP 2.5.17. 1. config error processing olcDatabase={2}mdb,cn=config UNKNOWN attributeDescription "OLCDBINDEX" inserted if I comment "OLCDBINDEX" 2. ldif_read_file: checksum error on "/opt/symas/etc/openldap/slapd.d/cn=config/olcDatabase={2}mdb.ldif config error processing olcDatabase={2}mdb,cn=config: Can you please guide by looking into this issue. Regards, Anil P ************************************************************* cat olcDatabase={2}mdb.ldif # AUTO-GENERATED FILE - DO NOT EDIT!! Use ldapmodify. # CRC32 f21f2837 dn: olcDatabase={2}mdb objectClass: olcDatabaseConfig objectClass: olcMdbConfig olcDatabase: {2}mdb olcDbDirectory: /var/lib/ldap olcSuffix: dc=hadoop,dc=com olcRootDN: cn=ldapadm,dc=hadoop,dc=com olcRootPW:: ************ olcDbIndex: objectClass eq,pres structuralObjectClass: olcMdbConfig entryUUID: ba4f359a-a605-103e-9085-7fcb0f4ffaf5 creatorsName: cn=config createTimestamp: 20240514061956Z entryCSN: 20240514062200.341950Z#000000#000#000000 modifiersName: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth modifyTimestamp: 20240514062200Z

2 1

[openldap 2.4]olcdbcheckpoint parameter is not working
by norihisa.kimura＠ctc-g.co.jp 15 May '24

15 May '24

To whom it may concern, Could you confirm if the following understanding is correct? Regarding the olcDbCheckpoint parameter in openldap-2.4.46-18, it is mentioned in the 2.4 manual but it does not seem to work even when the setting is enabled and tested. Upon investigating the source code, it appears that the parameter is deactivated. Based on these results, it is speculated that it will not work as expected because it is an unimplemented item, Is this hypothesis right? * 2.4 manual https://www.openldap.org/doc/admin24/slapdconf2.html 5.2.6.3. olcDbCheckpoint: <kbyte> <min> I am looking forward to your response. regards

2 1

ldapauditlog is too big
by kalybox2020＠gmail.com 15 May '24

15 May '24

Hi Team, We are running openldap 2.4. and I see ldapauditlog is too big about 14GB, never rotated for more than a year. What is the best way to rotate it? I am thinking. 1. Stop the ldap instance mv ldapauditlog file to ldapauditlog.bak touch ldapauditlog start the isntance Is there any better way? Please confirm Thanks -Kaly

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical