openldap-software

openldap-software@openldap.org

2719 discussions

bdb binary log files
by Piotr Wadas 19 Mar '09

19 Mar '09

Hello, I'm using openldap 2.4.11 on linux x86 system, with one database bdb backend, with the following options in slapd.conf file: database bdb [..] dbnosync cachesize 1000 checkpoint 0 0 [..] Is it possible to disable bdb log.00000[0..n] files completely? I can slapcat the database, then remove these, slapadd and reindex database, and there's no logs, but is it possible to avoid creating them? Or set up some limit of numer/size of them ? Let's assume I don't need logs. I hate logs. I don't wany any logs, whatever :) I reviewed bdb documentation, but there's no clear information how to control this. Additionally - when I have a "DB_CONFIG" file in /etc/ldap, and a DB_CONFIG file in database storage dir, e.g. /var/lib/ldap, which one is actually used? My guess'd be /var/lib/ldap/DB_CONFIG, but I'd like to know for sure :-) Regards, Piotr Wadas

3 3

tls_reqcert never
by alessio 19 Mar '09

19 Mar '09

In the ldap.conf man page I can read: ... TLS_REQCERT <level> ... never The client will not request or check any server certificate. ... In this case the ldaps:// connection will be encrypted anyway? Isn't it? Ciao A

2 1

upgade schema from 2.3 to 2.4
by Hegedus Gabor 19 Mar '09

19 Mar '09

Hi I have a working 2.3 openldap server with radius.schema, modified inetorgperson.schema. How can i move the all my schema to the 2.4 version? Can sb give me a manual or tell me how can I do it!? like convert and include or else cos I have schema problems on 2.4 thank you Gabor

2 1

Re: slapd syncrepl consumer having permanent high CPU load
by Rodrigo Costa 19 Mar '09

19 Mar '09

Folks, I was preparing openLDAP with GDB symbols but looks like the issue was identified and solved in HEAD. Just to identify this issue; was created any sort of ITS for verification in a new load? Sorry my late response but my baby daughter just born last week and I was having some work at home. I will give a try in the HEAD load. Best Regards, Rodrigo. PS-> Just some link from my daughter http://sites.google.com/site/lauramenina/laura_english --- On Wed, 3/18/09, Howard Chu <hyc(a)symas.com> wrote: > From: Howard Chu <hyc(a)symas.com> > Subject: Re: slapd syncrepl consumer having permanent high CPU load > To: "John Morrissey" <jwm(a)horde.net> > Cc: openldap-software(a)openldap.org > Date: Wednesday, March 18, 2009, 5:21 AM > John Morrissey wrote: > > After ~16h uptime, slapd with this BDB had increased > its DN cache to ~250k > > entries after it previously appeared stable at the > configured 20k entries, > > and its entry cache had ballooned to ~480k entries. > Its RSS was about 3.6GB > > at this point, with a BDB cache size of 2GB. > > I was finally able to reproduce this (took several hours of > searches. Fortunately I was at a St. Pat's party so I didn't > have to wait around, just got home in time to see it start > going bad...). A fix is now in HEAD. > > (And now we'll see if Guinness is Good For Your Code... ;) > -- -- 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

slapadd performance
by Pete Giesin 18 Mar '09

18 Mar '09

I am trying to perform some benchmarking against OpenLDAP. So far I have ran my tests against a 100K and 1Million entry database and I have had rather decent numbers. My final set of tests were to be ran against a 10Million entry database. Unfortunately, I am having difficult loading the database with this many entries. I have generated 10 1Million LDIF files. I am using "slapadd -c -q -v -l <file>" to import each file. The first 2 files took approximately 15 minutes each to load. The remaining 8 files are taking progressively longer and longer. So much longer that I anticipate the entire proceess to take well over 24 hours. My question is is there anything I can do to increase the performance of slapadd. I assume that since slapd is not running at this point that the normal DB_CONFIG and slapd.conf settings do not have much affect. I currently have a single database configured to hold all 10 Million entries. Is this an unrealtistic expectation? Should I instead be planning on having multiple databases and using chaining/referrals to link them together. What is the optimal configuration for handling this number of entries? Thanks, Pete

3 2

mirroring problem (unwilling to perform error)
by Hegedus Gabor 18 Mar '09

18 Mar '09

Hi all! I have a serious problem! I try to configure the ldap server mirroring mode, but something problem with this. Fist of all: I tested the mirroring on two openldap 2.4.11-0ubuntu6.1. and it worked fine. I just configured slapd.conf file like this: # Global section serverID 1 (another ldap is 2) moduleload syncprov overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100 syncrepl rid=001 provider=ldap://192.168.1.2 type=refreshAndPersist interval=00:00:00:10 searchbase="dc=test,dc=hu" filter="(objectClass=*)" attrs="*" scope=sub schemachecking=off bindmethod=simple binddn="cn=admin,dc=test,dc=hu" credentials="test" retry="60 +" mirrormode on It was okay, when I modified the db1, the db2 modified too. BUT! I try to set up on version 2.3.30, I use the same configuration, the ldap starts good, but when i try to modify the db, the phpldapadmin shows this error: Could not perform ldap_modify operation. LDAP said: Server is unwilling to perform Error number: 0x35 (LDAP_UNWILLING_TO_PERFORM) Description: The LDAP server refused to perform the operation. What is the problem, what is missconfigured? please help, thank you! br Gabor

2 2

The OpenLDAP Client and Multiple DNS Records
by Tim Gustafson 18 Mar '09

18 Mar '09

Hi, How does the OpenLDAP client library handle multiple A records being returned for a DNS query for an LDAP server? That is to say, if "host ldap" returns 1.1.1.1, 2.2.2.2 and 3.3.3.3, will the OpenLDAP client library only connect to 1.1.1.1? If a connection to 1.1.1.1 fails, will it try 2.2.2.2 and then 3.3.3.3? Basically we're trying to achieve redundant servers and load balancing using a round-robin-style DNS entry. Tim Gustafson BSOE Webmaster UC Santa Cruz tjg(a)soe.ucsc.edu 831-459-5354

6 8

Re: Mirror Mode, MMR and replicas
by Quanah Gibson-Mount 18 Mar '09

18 Mar '09

--On Wednesday, March 18, 2009 10:18 PM +0100 Rein Tollevik <rein(a)OpenLDAP.org> wrote: > Quanah Gibson-Mount wrote: >> --On Wednesday, March 18, 2009 3:01 AM -0700 Howard Chu <hyc(a)symas.com> > >>>> I'll start with replication under MMR. >>> >>>> As I understand it, the replicas can only point at a single master. >>> >>> False. >> >> Last I checked, the provider parameter in the syncrepl configuration >> block was single valued. Which means either it gets pointed at a load >> balancer, or it only talks to a single master. If that master goes >> down, it no longer talks to anything without reconfiguration. > > Each syncrepl engine (configuration block) can only refer to a single > master, but you may configure many engines within the same database, each > with its own master. If one master goes down the engine using that > master will obviously not receive any updates until its master is up > again, but the other will continue to receive updates from their master. Ok, this was the point I didn't realize -- That syncrepl on a replica will correctly handle looking at two masters providing the same changes to it. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: Mirror Mode, MMR and replicas
by Quanah Gibson-Mount 18 Mar '09

18 Mar '09

--On Wednesday, March 18, 2009 3:01 AM -0700 Howard Chu <hyc(a)symas.com> wrote: > Quanah Gibson-Mount wrote: >> A number of our clients have requested "fail-over"/redundancy >> capabilities for the LDAP master, and as I'm currently working on moving >> our product to use OpenLDAP 2.4, this becomes a distinct possibility. >> However, I have some questions about the >> viability/reliability/effectiveness of using multiple masters combined >> with replicas. I don't see these answered in the Admin Guide. > > You mean, setting up regular read-only replicas slaved to the masters? Yes. >> I'll start with replication under MMR. > >> As I understand it, the replicas can only point at a single master. > > False. Last I checked, the provider parameter in the syncrepl configuration block was single valued. Which means either it gets pointed at a load balancer, or it only talks to a single master. If that master goes down, it no longer talks to anything without reconfiguration. >> So, if >> I have a 2 master MMR setup, I assume I would want to point half my >> replicas at master A and the other half at master B for their updates. >> This leads to a problem in my mind, in that if master A goes down, then >> half of my replica pool is now going to remain completely out of sync >> with the remaining master until master A is recovered. Throwing a Load >> balancer in front of the two masters, and pointing the replicas at that >> instead, is not a viable option because the two masters may be getting >> updates in a different sequence, so if a replica disconnects from the LB >> and then reconnects, the updates it could get fed from whatever master >> the LB is pointing at could lead to inconsistencies. > > What inconsistencies? Each master's changes are stamped with its own sid. > Any consumer is going to know about the contextCSNs of each master it > talks to. The consumer can only talk to a single master, unless it is pointed at a load balancer. See notes above. In the load balancer case then, I'm assuming based on what you say, that if the replica gets disconnected because master A went down, then when it gets reconnected to master B, that its CSN will be completely different because of the SID values being different, and do a full refresh. Is that correct? >> Neither of these seem like a >> good option. I don't see a good solution here to resolve this issue, >> either, unless the replica could somehow know which master it had been >> talking to, > > The replica always knows which master it's talking to... > >> and drop into refresh mode if it found itself talking to a new >> master? > > Drop into refresh mode? Obviously in persist mode the consumer keeps a > connection open to a specific master; a load balancer can't move an open > connection. So obviously, if a particular master disappears, all of its > clients are going to lose their connections and any consumers set up to > retry are going to have to initiate new sessions. And every new > replication session starts with a refresh phase. So this recovery is > already automatic, it always has been. Based off of the CSN value. See question above about CSN & SID. >> I'm also not clear on what happens if your replicas are >> delta-syncrepl based, rather than normal syncrepl, in the LB setup. > > Not possible. Current delta-sync requires all updates to be logged in > order; in an MMR setup you can't guarantee order so *nobody* can use > delta-sync in this scenario. > >> For Mirror Mode, I would assume you could point the replicas at the LB >> fronting the two masters, since only one master is ever receiving >> changes. I also assume delta-syncrepl would be a completely valid option >> for replication to the replicas, again because only one master is >> getting the updates, so all updates would be logged in the same sequence >> on both servers. However, I don't know if this is correct or not, or if >> there are limitations here I haven't considered. When I was first >> pondering this on the #openldap-devel channel in IRC, Matt Backes made a >> comment about delta-syncrepl not working with Mirror Mode. > > For MirrorMode, delta-sync should work since there is only ever one > source of changes, and they will be logged in order. There is a window of > vulnerability where a server crashes after committing changes to its > accesslog, before it replicates them to the mirror. Those changes will be > temporarily lost, and create a gap in the mirror's log. When the original > server comes back up, the mirror will receive those lost changes, but the > strict ordering of its log will be broken. In this case though, the > delta-sync consumer will be fine - if the lost changes caused no > conflicts, they will simply be committed. If they do cause a conflict, > the consumer will just fallback to refresh mode and the conflicts will be > erased. Ok, good. Mirror Mode sounds like the way to go. >> So, basically, I'm at a loss if my understanding things is correct, on >> how I provide a consistent replicated environment for my customers, >> while also providing master/master failover. > > This appears to have been a -software question, not a -devel question. > Perhaps you should summarize back to the -software list and end this > thread here. Done. -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

2 1

Re: root-only configuration
by Peter Mogensen 18 Mar '09

18 Mar '09

Mike Malsman wrote: > On 11.Mar.2009, at 9:32 AM, Peter Mogensen wrote: >> But limiting cn=config access to ldapi:/// ... no luck. >> >> Do someone have a working example of this? >> >> /Peter > > What does your 'access' directive look like? access to dn.exact="cn=config" by peername.path="/var/run/slapd/ldapi" auth by * none I've used this method before in "normal" databases, to control who can become rootdn, but it just won't work for cn=config. Of course, I have to add a "userPassword" attribute to cn=config.ldif, but it seems to be ignored. I've also tried to create a cn=root,cn=config object, but I have a problem finding a schema which is loaded which allows me to set userPassword. If people on this list hadn't said that it was possible, I would probably have concluded by now that it is simply not possible to limit rootdn access to cn=config to ldapi:///. /Peter

3 8

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software