openldap-technical

openldap-technical@openldap.org

21 participants
9802 discussions

memory leak
by Friedrich Locke 14 Jan '13

14 Jan '13

Hi! Is anybody aware of memory leaks in OpenLDAP 2.4.31 ? My server is consuming memory. I have only around 16 users on my oldap implementation. Every search performed increase memory consumption. Any ideia ?

2 1

OpenLDAP SSL
by Andy Carlson 14 Jan '13

14 Jan '13

I am running an OpenLDAP server and I am attempting to get it set up with SSL. The service config appears to already be configured with port 636. I have added the Cert, CACert, and Key into the cn=config context using the three corresponding attributes. When I attempt to restart the slapd service it will not start up. I have done this on three other servers whose configuration is exactly the same and it worked perfectly. Any thoughts? Thanks much!!!, Andy Carlson Moody Bible Institute Identity Administrator | Information Systems 312-329-4385 www.moody.edu<http://www.moody.edu>

3 2

Re: Memory usage with bdb
by Friedrich Locke 14 Jan '13

14 Jan '13

Some time ago, i send a message about slapd "eating" all my memory resource. Mr. Quanah asked me to provide more details. Here you have it: sioux@gustav$ uname -a OpenBSD gustav.cpd.ufv.br 5.2 GENERIC.MP#368 amd64 sioux@gustav$ sioux@gustav$ pkg_info | grep openldap openldap-client-2.4.31 Open source LDAP software (client) openldap-server-2.4.31p0 Open source LDAP software (server) sioux@gustav$ pkg_info | grep db cyrus-sasl-2.1.25p3-db4 RFC 2222 SASL (Simple Authentication and Security Layer) db-4.6.21v0 Berkeley DB package, revision 4 dbus-1.6.2p0v0 message bus system gdbm-1.8.3p0 GNU dbm iodbc-3.52.7 ODBC 3.x driver manager sioux@gustav$ So: Why is this happening ? On Thu, Nov 1, 2012 at 3:02 PM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Thursday, November 01, 2012 2:24 PM -0200 Friedrich Locke < > friedrich.locke(a)gmail.com> wrote: > > Is anyone aware of any buggy in openldap+bdb related to memory usage? >> Have anyone here using this type of backend ? Any problem to report? >> > > No. Yes. No. > > I would suggest you provide some more detailed information as to what, if > any, problem you feel you are experiencing. This email is quite vague. > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration >

2 1

openbsd+ldap+qmail: a nightmare
by Friedrich Locke 14 Jan '13

14 Jan '13

Hi folks, i have been walking around and now i need to get qmail+ldap+openbsd working. I could configure everything, as usual openbsd runs rock solid. But i believe openldap does not like openbsd somehow. That's what i want to figure it out. The point is: i have just setted up obsd+oldap+qmail. I am trying to send a message for the only user i have in the tree: somehow, i don't know why is "eating" all my system memory. I am really curious why it happens on OBSD. I am running amd64 5.2, but i remenber to have given up some time ago when the obsd version was not 5.2. When i issue ldapsearch not memory increase is realized. The problem remains even with the 5.2 version. Some information is provided below : sioux@gustav$ uname -a OpenBSD gustav.cpd.ufv.br 5.2 GENERIC.MP#368 amd64 sioux@gustav$ pkg_info | grep openldap openldap-client-2.4.31 Open source LDAP software (client) openldap-server-2.4.31p0 Open source LDAP software (server) sioux@gustav$ For the /etc/openldap/slapd.conf, here you have it: # # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/qmail.schema # Define global ACLs to disable default read access. # Do not enable referrals until AFTER you have a working directory # service AND an understanding of referrals. #referral ldap://root.openldap.org pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args # Load dynamic backend modules: # modulepath /usr/local/libexec/openldap # moduleload back_bdb.la # moduleload back_hdb.la # moduleload back_ldap.la # Sample security restrictions # Require integrity protection (prevent hijacking) # Require 112-bit (3DES or better) encryption for updates # Require 63-bit encryption for simple bind # security ssf=1 update_ssf=112 simple_bind=64 # Sample access control policy: # Root DSE: allow anyone to read it # Subschema (sub)entry DSE: allow anyone to read it # Other DSEs: # Allow self write access # Allow authenticated users read access # Allow anonymous users to authenticate # Directives needed to implement policy: # access to dn.base="" by * read # access to dn.base="cn=Subschema" by * read # access to * # by self write # by users read # by anonymous auth # # if no access controls are present, the default policy # allows anyone and everyone to read anything but restricts # updates to rootdn. (e.g., "access to * by * read") # # rootdn can always read and write EVERYTHING! ####################################################################### # BDB database definitions ####################################################################### database bdb #suffix "dc=my-domain,dc=com" suffix "dc=ufv,dc=br" #rootdn "cn=Manager,dc=my-domain,dc=com" rootdn "cn=oldap,dc=ufv,dc=br" # Cleartext passwords, especially for the rootdn, should # be avoid. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. #rootpw secret rootpw {SSHA}HBjSmSCbiE8J26EuDg3ULnSj2SmN1x5g # The database directory MUST exist prior to running slapd AND # should only be accessible by the slapd and slap tools. # Mode 700 recommended. directory /var/openldap-data # Indices to maintain index cn eq index objectClass eq index mail,mailalternateaddress,uid eq,sub index accountstatus,mailhost,deliverymode eq index default eq cachesize 4096 checkpoint 128 15 dbnosync dirtyread sasl-host gustav.cpd.ufv.br sasl-realm UFV.BR sasl-regexp uid=([^,]+),cn=UFV.BR,cn=gssapi,cn=auth uid=$1,ou=people,dc=ufv,dc=br limits dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" time=2048 size=16384 limits dn.base="cn=mail,ou=appsrv,dc=ufv,dc=br" time=2048 size=16384 limits dn.onelevel="ou=people,dc=ufv,dc=br" time=4 size=16384 ################################################################################ # access definition on ou=appsrv,dc=ufv,dc=br ################################################################################ access to dn.one="ou=appsrv,dc=ufv,dc=br" attrs=userPassword by self read by anonymous auth # by * none access to dn.one="ou=appsrv,dc=ufv,dc=br" by dn.one="ou=appsrv,dc=ufv,dc=br" read access to dn.base="ou=appsrv,dc=ufv,dc=br" attrs=entry by dn.one="ou=appsrv,dc=ufv,dc=br" read ################################################################################ # access definition on ou=group,dc=ufv,dc=br ################################################################################ access to dn.one="ou=group,dc=ufv,dc=br" by dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" read by dn.one="ou=people,dc=ufv,dc=br" read access to dn.base="ou=group,dc=ufv,dc=br" attrs=entry by dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" read by dn.one="ou=people,dc=ufv,dc=br" read ################################################################################ # access definition on ou=people,dc=ufv,dc=br ################################################################################ access to dn.one="ou=people,dc=ufv,dc=br" attrs=userPassword by self read by dn.base="cn=mail,ou=appsrv,dc=ufv,dc=br" read by anonymous auth by * none access to dn.one="ou=people,dc=ufv,dc=br" attrs=uid,homeDirectory by self read by dn.base="cn=mail,ou=appsrv,dc=ufv,dc=br" read by dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" read access to dn.one="ou=people,dc=ufv,dc=br" attrs=cn,uidNumber,gidNumber,loginShell,gecos,description by self read by dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" read access to dn.one="ou=people,dc=ufv,dc=br" attrs=mail,mailMessageStore,mailAlternateAddress,qmailUID,qmailGID,mailHost,mailForwardingAddress,deliveryProgramPath,qmailDotMode,deliveryMode,mailReplyText,accountStatus,qmailAccountPurge,mailQuotaSize,mailQuotaCount,mailSizeMax by self read by dn.base="cn=mail,ou=appsrv,dc=ufv,dc=br" read access to dn.one="ou=people,dc=ufv,dc=br" by self read by dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" read by dn.base="cn=mail,ou=appsrv,dc=ufv,dc=br" read access to dn.base="ou=people,dc=ufv,dc=br" attrs=entry by dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" read by dn.base="cn=mail,ou=appsrv,dc=ufv,dc=br" read ################################################################################ # access definition for the root (ufv.br) ################################################################################ access to dn.base="dc=ufv,dc=br" attrs=entry by dn.base="cn=ypldap,ou=appsrv,dc=ufv,dc=br" read by dn.base="cn=mail,ou=appsrv,dc=ufv,dc=br" read ####################################################################### # Monitor database definitions ####################################################################### database monitor access to dn.subtree="cn=monitor" by dn.base="cn=oldap,dc=ufv,dc=br" read # by * none

1 0

authentication problems
by Friedrich Locke 12 Jan '13

12 Jan '13

Dear list member, i am trying to retrieve data from a openldap server. When i issue ldapsearch from local machine itself, every thing works ok, but when i try from a remote host, i got problems related to GSSAPI authentication. Here you have: sioux@gustav$ ldapsearch -D cn=ypldap,ou=appsrv,dc=ufv,dc=br -b uid=vlobo,ou=people,dc=ufv,dc=br -W Enter LDAP Password: # extended LDIF # # LDAPv3 # base <uid=vlobo,ou=people,dc=ufv,dc=br> with scope subtree # filter: (objectclass=*) # requesting: ALL # # vlobo, people, ufv.br dn: uid=vlobo,ou=people,dc=ufv,dc=br uid: vlobo objectClass: organizationalRole objectClass: posixAccount objectClass: qmailUser cn: Valter Lobo uidNumber: 2001 gidNumber: 2000 homeDirectory: /home/vlobo loginShell: /bin/sh gecos: Valter Lobo,,, # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 sioux@gustav$ ############################################################################ But when i try from a remote host (the same command line with -h option, of course): sioux@lion$ ldapsearch -D cn=ypldap,ou=appsrv,dc=ufv,dc=br -b ou=people,dc=ufv,dc=br -h gustav.cpd.ufv.br -W Enter LDAP Password: SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic failure: GSSAPI Error: Miscellaneous failure (see text) (open(/tmp/krb5cc_1000): No such file or directory) sioux@lion$ What is it my mistaken ? Thanks in advance.

2 1

cluster
by Friedrich Locke 12 Jan '13

12 Jan '13

Hi! I am aware that openldap supports custering, but i have some doubts. Is this cluster based on a single write server/multiple read server ? Or i may have multiple read/write server ? Does an openldap cluster scales unlimited ? I mean: if I need more space or processing power, it is just to add a new server . I would like to use a configuration like: The space requirement would be spread over the number of servers; A client can connect to any node of the cluster for read/write operation; To increase space/processing power, just add a new node. Is that possible with openldap ? PS: keep in mind that there is a huge difference in allowing multiple write/read over a set of nodes that keep is own copy of the data and a set of nodes whose data is spread accross them all.

2 1

Re: ldap update ( 2.2 to 2.4)
by Dan White 11 Jan '13

11 Jan '13

>On Thu, Jan 10, 2013 at 12:34 PM, Dan White <dwhite(a)olp.net> wrote: > >> On 01/10/13 12:04 -0200, Bruno Furtado wrote: >> >>> Hi Folks! >>> >>> I'm newbie to LDAP and I received a mission to update the version. >>> >>> Today is running Openldap 2.2.23 and I need to update to OpenLDAP 2.4.28. >>> all update attempts failed. I observed that the new version have a >>> different method of configuration. >>> >>> What the best way to do this? >>> >> >> What error messages did you receive? >> >> You can use slaptest (with both -f and -F options) to convert your >> configuration to the newer configuration database format (see man >> slapd-config), although you can still use a slapd.conf based configuration. >> >> See chapters 10, 19, and appendix B of the OpenLDAP Administrator's Guide, >> and the man pages for slapcat/slapdd. You should dump the contents of your >> databases on the old system with slapcat, and slapadd them on the new >> installation. On 01/11/13 17:29 -0200, Bruno Furtado wrote: >Hi Dan, > >I tried both settings. > >This is the error message: > > 50f066f8 str2entry: invalid value for attributeType objectClass #1 >(syntax 1.3.6.1.4.1.1466.115.121.1.38) This error means that you have a value within your input, for an objectClass, which is invalid per rfc2252 and is not accepted by the newer version of slapd that you are using. Try to found out which entry in your input is causing the error. -- Dan White

1 0

Openldap Server Issue - ver-2.4.23 (Jun 22 2012 14:02:53)
by Arvind Navale 11 Jan '13

11 Jan '13

Hi There, Need help with resolving an configuration issue I am having with openldap server (OpenLDAP: slapd 2.4.23 (Jun 22 2012 14:02:53) ) running a CentOS-6.3 1. Have a openldap server setup with TLS running on CentOS-6.3 rpm -qa | grep ldap openldap-devel-2.4.23-26.el6.x86_64 python-ldap-2.3.10-1.el6.x86_64 apr-util-ldap-1.3.9-3.el6_0.1.x86_64 openldap-servers-2.4.23-26.el6.x86_64 openldap-2.4.23-26.el6.x86_64 openldap-clients-2.4.23-26.el6.x86_64 pam_ldap-185-11.el6.x86_64 ldapjdk-4.18-6.el6.x86_64 3. Have generated self signed server certificates using openssl command. openssl req -x509 -nodes -days 3650 -newkey rsa:1048 -keyout /etc/openldap/certs/server-key.pem -out /etc/openldap/certs/server-cert.pem 3. Have a CentOS-6.3 setup a openldap client and enable TLS. rpm -qa | grep ldap openldap-2.4.23-26.el6.x86_64 python-ldap-2.3.10-1.el6.x86_64 openldap-clients-2.4.23-26.el6.x86_64 apr-util-ldap-1.3.9-3.el6_0.1.x86_64 pam_ldap-185-11.el6.x86_64 4. When I try to login on a LDAP client, I am seeing following debugging messages in LDAP server side, >>> slap_listener(ldaps://:389/) daemon: listen=7, new connection on 14 daemon: activity on 1 descriptor daemon: activity on: daemon: epoll: listen=7 active_threads=0 tvp=NULL daemon: epoll: listen=8 active_threads=0 tvp=NULL daemon: epoll: listen=9 active_threads=0 tvp=NULL daemon: epoll: listen=10 active_threads=0 tvp=NULL daemon: added 14r (active) listener=(nil) conn=1000 fd=14 ACCEPT from IP=xxx.xxx.xxx.xxxx:55585 (IP=0.0.0.0:389) daemon: activity on 2 descriptors daemon: activity on: 14r daemon: read active on 14 daemon: epoll: listen=7 active_threads=0 tvp=NULL daemon: epoll: listen=8 active_threads=0 tvp=NULL daemon: epoll: listen=9 active_threads=0 tvp=NULL daemon: epoll: listen=10 active_threads=0 tvp=NULL connection_get(14) connection_get(14): got connid=1000 connection_read(14): checking for input on id=1000 TLS: file server-cert.pem does not end in [.0] - does not appear to be a CA certificate directory file with a properly hashed file name - skipping. TLS: file server-key.pem does not end in [.0] - does not appear to be a CA certificate directory file with a properly hashed file name - skipping. TLS: error: no server certificate: must specify a certificate for the server to use TLS: error: could not initialize moznss security context - error -5939:No more entries in the directory TLS: can't create ssl handle. connection_read(14): TLS accept failure error=-1 id=1000, closing connection_closing: readying conn=1000 sd=14 for close connection_close: conn=1000 sd=14 5. I generate the hash in the directory were the certs are and then try connecting again, see different slapd debugging messages conn=1001 fd=14 ACCEPT from IP=10.90.180.220:55586 (IP=0.0.0.0:389) daemon: activity on 1 descriptor daemon: activity on: 14r daemon: read active on 14 daemon: epoll: listen=7 active_threads=0 tvp=NULL daemon: epoll: listen=8 active_threads=0 tvp=NULL daemon: epoll: listen=9 active_threads=0 tvp=NULL daemon: epoll: listen=10 active_threads=0 tvp=NULL daemon: activity on 1 descriptor daemon: activity on: daemon: epoll: listen=7 active_threads=0 tvp=NULL daemon: epoll: listen=8 active_threads=0 tvp=NULL daemon: epoll: listen=9 active_threads=0 tvp=NULL daemon: epoll: listen=10 active_threads=0 tvp=NULL connection_get(14) connection_get(14): got connid=1001 connection_read(14): checking for input on id=1001 TLS: error: could not initialize moznss security context - error -5925:The one-time function was previously called and failed. Its error code is no longer available TLS: can't create ssl handle. connection_read(14): TLS accept failure error=-1 id=1001, closing connection_closing: readying conn=1001 sd=14 for close connection_close: conn=1001 sd=14 daemon: removing 14 daemon: activity on 1 descriptor daemon: activity on: conn=1001 fd=14 closed (TLS negotiation failure) Is there any bug with the version of openldap I am using? Appreciate any and every help from any of the group member to resolve the issue. Thank you, anlinux.

2 1

setting rootpw for cn=monitor
by Chris Card 11 Jan '13

11 Jan '13

Hi all, I'm seeing an issue with setting the rootpw for the cn=monitor database and syncrepl replication (multi-master syncrepl). I am seeing this problem with openldap 2.4.31 at the moment, but I intend to upgrade to 2.4.34 when that becomes available. When I just have one LDAP server (ldap1 say), I can set the olcrootdn to cn=monitor and set the olcrootpw without any error, so I have something like: dn: olcDatabase={2}monitor,cn=config objectClass: olcDatabaseConfig olcDatabase: {2}monitor olcAddContentAcl: FALSE olcLastMod: TRUE olcMaxDerefDepth: 15 olcReadOnly: FALSE olcSyncUseSubentry: FALSE olcMonitoring: FALSE olcRootPW: {SSHA}************** olcRootDN: cn=monitor When I create another LDAP server (ldap2 say) and set up multi-master syncrepl replication for cn=config between ldap1 and ldap2 I see an error in the slapd log on ldap2 like: olcRootPW: value #0: <olcRootPW> can only be set when rootdn is under suffix No olcSuffix is set for the cn=monitor database in the cn=config, but all the cn=monitor DNs are of the form cn=X,cn=Y,...,cn=monitor, so it seems that the suffix of the cn=monitor database is effectively cn=monitor. Any ideas? Chris

4 6

installing a new cacert - the transition
by Adam Wolfe 10 Jan '13

10 Jan '13

Greetings all. I am looking at having to install a new ca cert on our ldap server(s) and thus swapping out the client certs as well. This totals roughly 250 different machines. I am wondering as to the easiest way to go about this. Is there some grace period that can be set to allow me to relax and get to all the clients over a week's time? Or possibly the ability to use two certs? Then just slowly remove the old ones from the clients?

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