openldap-technical

openldap-technical@openldap.org

9 participants
9868 discussions

RE: SETTING UP MONITOR
by Quanah Gibson-Mount 14 Jan '14

14 Jan '14

--On Tuesday, January 14, 2014 11:51 AM -0500 "Borresen, John - 0442 - MITLL" <John.Borresen(a)ll.mit.edu> wrote: > Did I miss something? That link just showed me an ldif that isn't > telling me anything...that I haven't already seen in numerous google > searches. It is an example of a correctly configured monitor backend. Given that your attempt to add the monitor backend to your database is failing, I thought it might help you actually get it configured. --Quanah -- Quanah Gibson-Mount Architect - Server Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

2 1

Re: SETTING UP MONITOR
by Quanah Gibson-Mount 14 Jan '14

14 Jan '14

--On Tuesday, January 14, 2014 11:06 AM -0500 "Borresen, John - 0442 - MITLL" <John.Borresen(a)ll.mit.edu> wrote: > Trying to set up Monitor. I've created a Monitor directory in my ldap > directory: Why? The monitor backend has no database. > My ldif looks like this: I suggest you look at: <https://github.com/Zimbra-Community/zimbra-sources/blob/master/main/ZimbraS…> --Quanah -- Quanah Gibson-Mount Architect - Server Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

2 1

mdb expected growth
by Paul B. Henson 13 Jan '14

13 Jan '14

So after updating our dev ldap environment to use mdb, and slapadd'ing a fresh copy from our production environment into it, the database was using 828M: Environment Info Map address: (nil) Map size: 2147483648 Page size: 4096 Max pages: 524288 Number of pages used: 211612 Last transaction ID: 1333 Max readers: 126 Number of readers used: 6 Status of Main DB Tree depth: 1 Branch pages: 0 Leaf pages: 1 Overflow pages: 0 Entries: 29 I then proceeded to run a test load on it (basically, I had a script I put together when I added the memberof overlay that ripped through all of our groups, removing and then re-adding all members). After this test run, the use jumped to 1.9G: Environment Info Map address: (nil) Map size: 2147483648 Page size: 4096 Max pages: 524288 Number of pages used: 479536 Last transaction ID: 1075380 Max readers: 126 Number of readers used: 11 Status of Main DB Tree depth: 1 Branch pages: 0 Leaf pages: 1 Overflow pages: 0 Entries: 29 There is no new data in the database, all that happened was existing data was removed and then re-added. Is this drastic increase in space utilization expected in such a scenario? I bumped the max size from 2G to 4G and am rerunning the same script to see what happens. Is there any heuristic for how mdb will grow over time, based on the initial size from a fresh slapadd? I plan to set a fairly large maxsize, and also monitor it with munin to keep track of any unexpected growth, but I am curious if it is going to reach a steady-state size or continue growing over time. I would expect growth as additional entries were added, and possibly some growth from overhead when things were changed, but not necessarily such a big jump in size. Thanks.

5 8

Question regarding slapo-pcache
by Philippe 13 Jan '14

13 Jan '14

Hi everyone, I'm setting up an openldap server that proxies _and_ caches everything from other servers (OpenLDAP and AD, that's what the meta database is for). As for now proxying and caching data works fine but I'm unable to get credentials cached. How is pcacheBind supposed to work? This is my setup so far: --%snip%-- # slapd.conf include /some/schemas/.. sizelimit unlimited moduleload back_bdb moduleload back_ldap moduleload back_meta moduleload pcache database ldap suffix "dc=xyz,dc=de" rootdn "cn=sys,dc=xyz,dc=de" uri "ldap://10.0.0.1" # the ldap server I'm talking to chase-referrals yes rebind-as-user yes overlay pcache pcache bdb 999999 2 999 300 directory /var/lib/ldap-cache cachesize 1024 index objectClass eq,pres index uidNumber,gidNumber eq,pres index ou,cn,mail,surname,givenname eq,pres,sub index uid,memberUid eq,pres,sub index uniqueMember eq,pres pcacheMaxQueries 999999 pcacheOffline false pcachePersist true pcacheAttrset 0 cn uid objectclass userpassword sn mail memberof displayname pcacheTemplate (cn=) 0 3600 pcacheAttrset 1 cn uid pcacheTemplate (cn=) 1 3600 pcacheBind (cn=) 1 3600 sub dc=xyz,dc=de database meta suffix "dc=de" uri "ldap://localhost/dc=xyz,dc=de" idassert-bind bindmethod=simple binddn="cn=sys,dc=xyz,dc=de" credentials="somecredentials" chase-referrals yes rebind-as-user yes --%snip%-- Now I'm running some queries using ldapsearch and watching the traffic via tcpdump. As far as I can tell the requested attributes are cached, the remote ldap server is only asked once about the requested data. But even when the data is already cached the openldap server still tries to bind to the remote server. Which is unfortunate since I'm trying to catch network outages with the caching proxy. Example: >> $ ldapsearch -x -H ldap://localhost -D cn=me,ou=users,dc=xyz,dc=de -W -b dc=xyz,dc=de 'cn=foo' mail - first attempt tcpdump shows: bind, search of cn uid objectclass userpassword sn mail memberof, and the result - second attempt, same command tcpdump shows: bind and that's all. The result are delivered from cache. I tried other filter masks, too, which lead to different results: --%snip%-- pcacheAttrset 0 * pcacheTemplate (cn=) 0 3600 pcacheBind (cn=) 0 3600 sub dc=xyz,dc=de --%snip%-- In this case the remote server isn't queried anymore after the second attempt of the command above (which is good), but when trying to search for data that hasn't been cached yet, openldap tries to bind anonymously to the remote server (which is bad, because it won't work). Syslog tells me: >> ldap_back_dobind_int: DN="cn=me,ou=users,dc=xyz,dc=de" without creds, binding anonymously Any clues? Kind regards, Philippe

1 0

Re: MDB_BAD_RSLOT while executing slapacl
by Francesco Malvezzi 13 Jan '14

13 Jan '14

This is a follow-up of: https://www.openldap.org/lists/openldap-technical/201312/msg00119.html I have observed in the wild the "MDB_BAD_RSLOT while executing slapacl" error on two different servers: [...] 52d3c079 <= check a_group_pat: cn=agentsgroup,ou=groups,dc=example,dc=org 52d3c079 mdb_opinfo_get: err MDB_BAD_RSLOT: Invalid reuse of reader locktable slot(-30783) 52d3c079 <= check a_group_pat: cn=admins,ou=groups,dc=example,dc=org 52d3c079 mdb_opinfo_get: err MDB_BAD_RSLOT: Invalid reuse of reader locktable slot(-30783) [...] On the other hand, I am not able to reproduce the error with the example data given by Igor. The slapacl returns 'ALLOW'. Might be of interest my config yielding the error? thank you, Francesco /usr/local/openldap-2.4/libexec/slapd -V @(#) $OpenLDAP: slapd 2.4.38 (Dec 4 2013 11:26:00) $ francesco@c1:/usr/local/src/openldap-2.4.38/servers/slapd

2 1

syncrepl will update, and delete, but won't create entries
by Andrew LaPierre 10 Jan '14

10 Jan '14

Before I give too many details that you don't need, is there something that would cause this behavior? Both servers have: Ubuntu 10.04 OpenLDAP 2.4.21 I'm using RefreshAndPersist. I can make changes and delete entries, and the changes and deletions happen on the consumer, but if I create somebody on the provider, they never show up on the consumer. Please let me know what additional information I can give you guys to help. Thanks for the help! -- Andrew LaPierre

3 2

configuring mdb maxsize
by Paul B. Henson 09 Jan '14

09 Jan '14

I'd like to clarify the requirements for the mdb maxsize parameter. According to the current admin guide: "This should be the largest that the database is ever anticipated to grow" Which would seem to imply it cannot later be changed without completely rebuilding the database. According to the slapd-mdb manpage: "Note: It is important to set this to as large a value as possible, (relative to anticipated growth of the actual data over time) since growing the size later may not be practical when the system is under heavy load." It can possibly be changed later, but maybe not ;). Based on unauthoritative postings I've read, it seems that if you shut down openldap, you can change it to whatever you want, and when you restart openldap, the additional size will immediately be available with no problems. It also seems that if you're using cn=config, you can change it live and it will immediately take effect. I haven't seen any postings indicating a problem that occurred while changing it live. Are there any restrictions for changing it while the server is down? What restrictions, or problems, if any, are involved when changing it while the server is up? Thanks much.

3 4

optimal mdb flags
by Paul B. Henson 09 Jan '14

09 Jan '14

So if it's not obvious, we're working on migrating our openldap deployment to mdb from hdb :), I apologize for the flurry of questions, this will be the last, at least for today ;). I'm trying to evaluate the optimal configuration for mdb; it seems like for the most part you can just set maxsize and move on if you don't have performance issues, but one flag I've seen frequently mentioned for improving performance is writemap. This seems like a win all around, unless there is some bug that results in erroneous writes into the mapped region, in which case it could potentially cause major database corruption. For those that have been running mdb in the field for a while, are you using writemap? Have you ever run into any corruption because of it? The other flag that seems to be popular is nometasync. As opposed to nosync, which might cause loss of some number of transactions in case of a crash, nometasync only risks one? And the benefit is that it is "slightly faster"? Again, any recommendations from field experience on this? Also, if you do enable it, do you need a checkpoint directive, or is that only necessary for nosync? Thanks.

3 5

Port 636 and SLAPD(8)
by jumpgroup＠aol.com 09 Jan '14

09 Jan '14

Hello Experts, In need of a little guidance please. I'm installed OpenLdap 2.4.23 on RHEL in a sandbox and would like to enable SSL on port 636. All documentation references SLAPD(5), but since I'm using SLAPD(8), I do not know have the slapd.conf file. Looking for the current SLAPD(8) method of configuring this along with starting the service to support port 636. Thanks in advance! Jeff P.

5 5

mdb searchstack parameter
by Paul B. Henson 09 Jan '14

09 Jan '14

>From reading the documentation, it sounds like when configuring this parameter you need to strike a balance between potential performance impact if it is too low, and wasted memory if it is too high. While running, is there any way to tell whether or not a search exceeded your configured value and required additional allocation? Whether via the monitor backend, or a log entry, or? Ideally, it would be nice to be able to tell if your configured value was too low and adjust as necessary. Thanks.

2 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