openldap-technical

openldap-technical@openldap.org

7 participants
9901 discussions

OpenLDAP reader-only users , and removing anonymous user reading ?
by rey sebastien 12 Dec '11

12 Dec '11

Hello, I search some information to make reader-only users on my openLDAP .. I have already cn=reader-only, and my dn equal "dc=parisgeo,dc=cnrs,dc=fr" How can i create a .ldif with specific configuration to remove anonymous user reading, and authorize the read of my ldap only with the cn=reader-only authentification ? Thanks a lot, Best regards, SR

3 3

French tutorial
by reyman 12 Dec '11

12 Dec '11

Hello, I work on a tutorial (based on the many tutorial existing) to make TLS/SSL connexion possible with debian and the new cn=config mode (no slapd.conf) At this moment, you can see my work here (in french only) : http://www.services.parisgeo.cnrs.fr/2011/12/ldap-securise/ Thanks Best regards, Sr -- <http://stackoverflow.com/users/385881/reyman64>

1 0

I have no name!
by Jayavant Patil 12 Dec '11

12 Dec '11

Hi, I am using openldap-2.4.19-4.x86_64 on fedora 12 machine. I am facing the 'I have no name !' while I do ssh on client machine(All user info is getting propagated to client machines properly (checked with getent passwd,getent passwd and getent shadow)), and this is because I specify no access to anonymous. But, when I specify read access to anonymous this problem is getting resolved but my security is getting compromised since anonymous is reading everything. How do I write ACL rule to achieve both each user to see his data only i.e. security and getting user-name while doing ssh on client.? -- Thanks & Regards, Jayavant Ningoji Patil Engineer: System Software Computational Research Laboratories Ltd. Pune-411 004. Maharashtra, India. +91 9923536030.

2 1

Re: slapd hanging - meta backend - Solaris 10
by Lincoln Souzek 12 Dec '11

12 Dec '11

Hello, I compiled 2.4.28 and I'm trying to recreate the issue with that version but I've run into two other issues that are causing slapd to crash in the meantime. I compiled with the following options: ./configure --enable-ldap --enable-meta --prefix="/opt/local/openldap-2.4.28" --enable-dynlist --enable-memberof --enable-rwm --enable-mdb=no The first issue is that slapd has crashed twice with a SIGBUS and dumped a core file. I haven't been able to regularly reproduce it but both times it happened on the initial query after a bind. The stack of the thread where that signal originates wasn't identical both times but the two instances look similar: ----------------- lwp# 6 / thread# 6 -------------------- fedd446c _malloc_unlocked (28, 0, 1a40cb8, 1646c0, 0, 0) + 22c fedd4224 malloc (28, 1, 940a8, 59550, fee68288, fee709b0) + 4c 001646c0 ber_memalloc_x (28, 0, 0, 0, 0, 2fcfc8) + 58 00059550 ch_malloc (28, 427390, 0, fbfff428, 8000, 4551c8) + 8 00047910 ???????? (7864d4, 7866e4, 0, 0, 0, 2fcfc8) 00047b20 attrs_dup (7866e4, 427390, 0, fbfff428, 8000, 63) + 48 0004a980 entry_dup2 (4273d4, 427384, 0, 0, 0, 2fcfc8) + ac 0011f1d4 ???????? (fffffff6, fbfffcb8, 2932d0, fbfff428, 8000, 63) 0011f938 ???????? (1a3cfe0, fbfffcb8, 0, 0, 1, 0) 000a2fe4 ???????? (8000, fbfffcb8, 1b5b298, 2627c8, 8000, a2f70) 0004e978 ???????? (1a3cfe0, fbfffcb8, 2, 41a10, ffffffff, ffffffff) 00050d88 slap_send_search_entry (0, fbfffcb8, 1b5b298, 2627c8, 262750, 1ee000) + 3d4 00041de8 fe_op_search (1a3cfe0, fbfffcb8, 2, 41a10, 1, 0) + 3d8 000a39cc overlay_op_walk (8000, fbfffcb8, 8000, 1ee5f8, 8000, 200) + c8 000a3ae4 ???????? (1a3cfe0, fbfffcb8, 2, 0, 2b9d88, 1ee6f0) 00041528 do_search (1a3cfe0, fbfffcb8, fee6cbc0, fe020c00, 40f98, fbfffa38) + 590 0003f8e4 ???????? (fbfffe08, 1a3cfe0, fee6cbc0, fe020c00, 2fcfe8, 0) 00040270 ???????? (0, 20, fee6cbc0, fe020c00, 268328, 0) 0013ca30 ???????? (268318, fc000000, 0, 0, 13c8d4, 1) fee40368 _lwp_start (0, 0, 0, 0, 0, 0) ----------------- lwp# 5 / thread# 5 -------------------- fedd446c _malloc_unlocked (800, 1, 420780, fedd4224, 0, 0) + 22c fedd416c _smalloc (18, 0, 9415c, 16cbc8, fffffff9, fee6fa48) + 4c fedd4224 malloc (17, 1, 940a8, 16cf38, fee68288, fee709b0) + 4c 0016cbc8 ber_memalloc_x (17, 0, 0, 0, 0, 30dc98) + 58 0016cf38 ber_dupbv_x (8dea98, 12f6ab0, 0, fc3ff4c8, 8000, 8de950) + 3c 0004990c ???????? (750174, 750024, 0, 0, 0, 30dc98) 00049a20 attrs_dup (750024, 3fbc50, 0, fc3ff4c8, 8000, 63) + 48 0004c7b0 entry_dup2 (3fbc6c, 3fbc44, 0, 0, 0, 30dc98) + ac 0012556c ???????? (fffffff6, fc3ffd58, 2c7208, fc3ff4c8, 8000, 63) 00125d68 ???????? (423350, fc3ffd58, 0, 0, 0, 0) 000a71c0 ???????? (8000, fc3ffd58, 9e1f38, 275fb8, 8000, a714c) 00050818 ???????? (423350, fc3ffd58, ffffffff, ffffffff, 0, 0) 00052cb8 slap_send_search_entry (0, fc3ffd58, 9e1f38, 275fb8, 3, 1f9400) + 3e0 00043c94 fe_op_search (423350, fc3ffd58, 2, 43894, 1, 0) + 400 000a7b98 overlay_op_walk (8000, fc3ffd58, 8000, 1f9b90, 8000, 200) + c8 000a7cb0 ???????? (423350, fc3ffd58, 2, fc3ffad8, 2a0bd8, 1f9c88) 00043364 do_search (423350, fc3ffd58, fee6cbc0, 1edc00, 177400, fc3ffad8) + 618 00041698 ???????? (fc3ffe08, 423350, fee6cbc0, fdcf0800, 27bb18, 0) The second issue, which I can reproduce, is that slapd is crashing with a SIGSEGV when it encounters the following entry in a Sun Directory Server configured as a meta backend: c=undef,dc=company Is undef a reserved word that's causing an issue here? In earlier versions (2.4.23, at least), it seems like that entry was just discarded and not returned as a search result. Thanks, Lincoln On Mon, Dec 5, 2011 at 10:32 PM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Monday, December 05, 2011 6:09 PM +0100 Lincoln Souzek < > lsouzek(a)gmail.com> wrote: > > Hello, >> >> I've seen a couple of instances where slapd becomes unresponsive, >> apparently because the threads are waiting on a backend meta DB. We're >> running slapd 2.4.23 on Solaris 10 (update 11/06). We have 128 threads >> configured and when I attach with truss, I see 130 allocated, most of >> which look like this: >> > > I would note there have been some re-entry fixes for back-meta since > 2.4.23 was released. I would suggest you re-try with the latest OpenLDAP > version as a first step. > > --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 >

1 0

Re: Solaris 10 Native Client connecting to OpenLdap How to needed
by adam＠spoontech.biz 11 Dec '11

11 Dec '11

Hi, I have scripted the following which is what we use when joining a new client to ldap: setup_ldap.sh #!/bin/sh if [ ! -d /var/ldap ] ; then mkdir /var/ldap chown root:sys /var/ldap chmod 755 /var/ldap fi cd /var/ldap rm -rf /var/ldap/* >/dev/null 2>&1 /usr/sfw/bin/sparcv9/certutil -N -d /var/ldap if [ -f /etc/ssl/our_CA_cert.pem ] ; then /usr/sfw/bin/sparcv9/certutil -A -n "ca-cert1" -i /etc/ssl/our_CA_cert.pem -a -t CT -d . else echo 'Could not find /etc/ssl/our_CA_cert.pem' fi if [ -f /etc/ssl/our_CA_cert2.pem ] ; then /usr/sfw/bin/sparcv9/certutil -A -n "ca-cert2" -i /etc/ssl/our_CA_cert2.pem -a -t CT -d . else echo 'Could not find /etc/ssl/our_CA_cert2.pem' fi if [ -f /etc/ssl/our_root_CA.pem ] ; then /usr/sfw/bin/sparcv9/certutil -A -n "ca-cert-root" -i /etc/ssl/our_root_CA.pem -a -t CT -d . else echo 'Could not find /etc/ssl/our_root_CA.pem' fi ldapclient init -v -a profileName=ldapprofilename -a domainName=example.com -a proxyDN=cn=proxyagent,ou=profile,dc=example,dc=com -a proxyPassword=examplepasswd ldapserver1 svcadm enable svc:/network/ldap/client:default svcadm restart svc:/network/ldap/client:default svcadm enable svc:/system/name-service-cache:default svcadm restart svc:/system/name-service-cache:default Obviously from the script above you can see that we have created profiles in ldap storing settings like uri etc. We did this so that machines authenticate to our local ldap server first, then connect to remote servers if unable to get a response from the local server. Let me know if you need anything else. Cheers, > Adam, > > What is the ldapclient init command you are using? > > > > On Sun, Dec 11, 2011 at 5:14 AM, <adam(a)spoontech.biz> wrote: > >> Hi, I manage an OpenLDAP environment consisting of Linux, Solaris and >> AIX. >> >> Here is the Schema I use for Solaris 10. >> >> Hope this helps. >> >> # Sun nisMapEntry attributes >> attributetype ( 1.3.6.1.1.1.1.28 >> NAME 'nisPublickey' >> DESC 'nisPublickey' >> EQUALITY caseIgnoreIA5Match >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) >> >> attributetype ( 1.3.6.1.1.1.1.29 >> NAME 'nisSecretkey' >> DESC 'nisSecretkey' >> EQUALITY caseIgnoreIA5Match >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) >> >> attributetype ( 1.3.6.1.4.1.1.1.1.12 SUP name >> NAME 'nisDomain' ) >> >> # Sun additional attributes to RFC2307 attributes (NIS) >> attributetype ( 2.16.840.1.113730.3.1.30 >> NAME 'mgrpRFC822MailMember' >> DESC 'mgrpRFC822MailMember' >> EQUALITY caseIgnoreIA5Match >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) >> >> #attributetype ( 1.3.6.1.4.1.42.2.27.2.1.15 >> # NAME 'rfc822MailMember' >> # DESC 'rfc822MailMember' >> # EQUALITY caseIgnoreIA5Match >> # SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.1.1.12 >> NAME 'nisNetIdUser' >> DESC 'nisNetIdUser' >> EQUALITY caseExactIA5Match >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.1.1.13 >> NAME 'nisNetIdGroup' >> DESC 'nisNetIdGroup' >> EQUALITY caseExactIA5Match >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.1.1.14 >> NAME 'nisNetIdHost' >> DESC 'nisNetIdHost' >> EQUALITY caseExactIA5Match >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) >> >> # Sun NIS publickey objectclass >> objectclass ( 1.3.6.1.1.1.2.14 >> NAME 'NisKeyObject' >> DESC 'NisKeyObject' >> SUP top >> MUST ( cn $ nisPublickey $ nisSecretkey ) >> MAY ( uidNumber $ description ) ) >> >> # Sun NIS domain objectclass >> objectclass ( 1.3.1.6.1.1.1.2.15 >> NAME 'nisDomainObject' >> DESC 'nisDomainObject' >> SUP top AUXILIARY >> MUST ( nisDomain ) ) >> >> # Sun NIS mailGroup objectclass >> objectclass ( 2.16.840.1.113730.3.2.4 >> NAME 'mailGroup' >> DESC 'mailGroup' >> SUP top >> MUST ( mail ) >> MAY ( cn $ mgrpRFC822MailMember ) ) >> >> # Sun NIS nisMailAlias objectclass >> #objectclass ( 1.3.6.1.4.1.42.2.27.1.2.5 >> # NAME 'nisMailAlias' >> # DESC 'nisMailAlias' >> # SUP top >> # MUST ( cn ) >> # MAY ( rfc822mailMember ) ) >> >> # Sun NIS nisNetId objectclass >> objectclass ( 1.3.6.1.4.1.42.2.27.1.2.6 >> NAME 'nisNetId' >> DESC 'nisNetId' >> SUP top >> MUST ( cn ) >> MAY ( nisNetIdUser $ nisNetIdGroup $ nisNetIdHost ) ) >> >> # Below is optional unless you want to use ldap_gen_profile >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.15 SUP name >> NAME 'SolarisLDAPServers' >> DESC 'SolarisLDAPServers' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.16 SUP name >> NAME 'SolarisSearchBaseDN' >> DESC 'SolarisSearchBaseDN' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.17 >> NAME 'SolarisCacheTTL' >> DESC 'SolarisCacheTTL' >> EQUALITY integerMatch >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.18 SUP name >> NAME 'SolarisBindDN' >> DESC 'SolarisBindDN' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.19 SUP name >> NAME 'SolarisBindPassword' >> DESC 'SolarisBindPassword' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.20 SUP name >> NAME 'SolarisAuthMethod' >> DESC 'SolarisAuthMethod' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.21 SUP name >> NAME 'SolarisTransportSecurity' >> DESC 'SolarisTransportSecurity' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.24 SUP name >> NAME 'SolarisDataSearchDN' >> DESC 'SolarisDataSearchDN' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.25 SUP name >> NAME 'SolarisSearchScope' >> DESC 'SolarisSearchScope' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.26 >> NAME 'SolarisSearchTimeLimit' >> DESC 'SolarisSearchTimeLimit' >> EQUALITY integerMatch >> SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.27 SUP name >> NAME 'SolarisPreferedServer' >> DESC 'SolarisPreferedServer' ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.28 SUP name >> NAME 'SolarisPreferedServerOnly' >> DESC 'SolarisPreferedServerOnly' >> SINGLE-VALUE ) >> >> attributetype ( 1.3.6.1.4.1.42.2.27.5.1.29 SUP name >> NAME 'SolarisSearchReferral' >> DESC 'SolarisSearchReferral' >> SINGLE-VALUE ) >> >> objectclass ( 1.3.6.1.4.1.42.2.27.5.2.7 >> NAME 'SolarisNamingProfile' >> DESC 'Solaris LDAP NSS Profile' >> SUP top STRUCTURAL >> MUST ( cn $ SolarisLDAPServers ) >> MAY ( SolarisBindDN $ SolarisBindPassword $ >> SolarisSearchBaseDN $ SolarisAuthMethod $ >> SolarisTransportSecurity $ SolarisSearchReferral $ >> SolarisDataSearchDN $ SolarisSearchScope $ >> SolarisSearchTimeLimit $ SolarisCacheTTL ) ) >> >> # End of solaris.schema >> > I am working on getting a bunch of Solaris 10 hosts connected to >> OpenLdap. >> > I am not Ldap expert by far however I must get this working. >> > >> > I have 0 issues getting Linux clients to connect but Solaris 10 how >> to's >> > docs are very evasive. >> > >> > I have searched everywhere the best I can find is a few online docs >> that >> > say you need to load a custom schema. >> > >> > I just need user / passwd authentication to a directory nothing more. >> Will >> > not be using TLS.. >> > >>

1 0

Solaris 10 Native Client connecting to OpenLdap How to needed
by Jeremy Loukinas 11 Dec '11

11 Dec '11

I am working on getting a bunch of Solaris 10 hosts connected to OpenLdap. I am not Ldap expert by far however I must get this working. I have 0 issues getting Linux clients to connect but Solaris 10 how to's docs are very evasive. I have searched everywhere the best I can find is a few online docs that say you need to load a custom schema. I just need user / passwd authentication to a directory nothing more. Will not be using TLS..

3 3

Debugging OpenLDAP client: Where are the log files?
by daisy.wu＠emc.com 10 Dec '11

10 Dec '11

Hi, OpenLDAP developers, I've been able to successfully built OpenLDAP client libraries liblber and libldap for Window 64 bit OS. I wrote a test program to connect to Microsoft AD (hosted on Win 2008 R2, a 64 bit OS) over SSL. I made sure the root certificate file is converted to X509 base 64 PEM format. And the certificate file name is named using the hash value returned from "openssl" command. I made sure I can telnet to the AD host at port 636 from my test machine (where I run my test program). This is to make sure there's not network connectivity problem between my client test machine and the LDAP server host. Here's snippet of my source code: int debug_flag = -1; // debug all rc = ldap_set_option( ld, LDAP_OPT_DEBUG_LEVEL, &debug_flag); rc = ldap_sasl_bind_s( ld, dn, LDAP_SASL_SIMPLE, &passwd, NULL, NULL, NULL); if (rc != LDAP_SUCCESS) { trace("%15s: %s (%s: %d = %s)", "FAILED", "ldap_sasl_bind_s() failed!", "Return value is", rc, ldap_err2string(rc)); } However, my OpenLDAP client test program fails with the following error: 0011-12-10 16:08:59 [5296]: FAILED: ldap_sasl_bind_s() failed! (Return value is: -1 = Can't contact LDAP server) My question is: I need to troubleshoot this problem. I will need to examine the OpenLDAP log files to find the root cause. Where are the OpenLDAP log files located? I read that the log file location is configured in slapd.conf. But where is slapd.conf file on Windows? Considering I am not running OpenLDAP server on this test machine. Any input or feedback will be much appreciated. Thanks. Daisy

1 0

Syncrepl SSL fail
by Hugo Deprez 10 Dec '11

10 Dec '11

Dear community, I setup a syncrepl between my master openldap server and a consumer. I am trying to use SSL for this syncrepl I got the following error in the log when I start slapd on the consumer : Oct 13 17:04:59 server slapd[16905]: slapd starting Oct 13 17:04:59 server slapd[16905]: slap_client_connect: URI=ldaps://ldap.mydomain.fr:1024/ DN="cn=syncrepluser,o=others,dc=mydomain,dc=fr" ldap_sasl_bind_s failed (-1) Oct 13 17:04:59 server slapd[16905]: do_syncrepl: rid=003 rc -1 retrying (9 retries left) I don't understand why it is failing as a single ldapsearch from the same server with the syncrepl user is working. here is my syncrepl configuration : Syncrepl rid=003 provider=ldaps://ldap.mydomain.fr:1024/ type=refreshOnly retry="60 10 600 +" interval=00:00:00:10 searchbase="dc=mydomain,dc=fr" scope=sub schemachecking=on bindmethod=simple binddn="cn=syncrepluser,o=others,dc=mydomain,dc=fr" credentials=my_password Any idea ? Regards, Hugo

8 14

Starting out with NSS overlay - Guidance required
by ptw 09 Dec '11

09 Dec '11

Hi gang! I'm looking for some guidance in what is most probably a very common objective. Which is to manage all authentication to network hosts from slapd. To begin, my goal is to have: 1. one machine (generically-configured LDAP client) running sshd (10.153.107.100) 2. multiple LDAP users 3. specify, from slapd, that only one user (tony) can log in over ssh to the machine Surprisingly, I have not found much documentation on this stuff beyond the slapo-nssov man page. Anyway, I have some LDIF entries ready to go but I'm feeling very uneasy about dumping them in and hoping for the best. I would rather learn more about how this all works together and hopefully get some pointers/gotchas from others who have done this before. That's why I'm writing this email. In particular, at this point I only want the bare necessities to achieve my simple goad specified above. My slapd server has the nis and ldapns schemas configured and the client machine has libnss-ldapd (applied to group and passwd services) and libpam-ldapd. All systems are running Ubuntu 11.10. I have manually disabled nslcd on the Ubuntu client machine (sudo update-rc.d nslcd disable). These are the entries I have so far: for slapd-config: # NSSOV dn: olcOverlay=nssov,ocDatabase={1}hdb,cn=config objectClass: olcOverlayConfig objectClass: olcNssOvConfig olcOverlay: nssov olcNssSsd: passwd ldap:///ou=People,dc=example,dc=com??one olcNssSsd: group ldap:///ou=People,dc=example,dc=com??one olcNssSsd: hosts ldap:///ou=People,dc=example,dc=com??one olcNssPam: hostservice uid2dn olcNssPamSession: sshd # ACL dn: olcDatabase={1}hdb,cn=config olcAccess: to attrs=userPassword by anonymous auth by self write by * none olcAccess: to attrs=shadowLastChange by self write by * none olcAccess: to * by self write by * read olcAccess: to dn.exact=cn=host1.example.com,ou=Hosts,dc=example,dc=com attrs=authorizedservice by dn.exact=cn=ssh,ou=host1,ou=server_access,ou=Groups,dc=example,dc=com compare by * read ================== The sshd host, user & group entries from my regular hdb-based DIT: # NSSOV HOST and USER dn: cn=host1.example.com,ou=Hosts,dc=example,dc=com objectClass: device objectClass: top objectClass: ipHost objectClass: authorizedServiceObject cn=host1.example.com ipHostNumber: 10.153.107.100 authorizedService: sshd dn: cn=ssh,ou=host1,ou=server_access,ou=Groups,dc=example,dc=com objectClass: posixGroup cn: ssh-host1-server_access gidNumber: 6000 dn: uid=tony,ou=People,dc=example,dc=com objectClass: inetOrgPerson objectClass: posixAccount objectClass: shadowAccount uid: tony cn: Tony Doe uidNumber: 11000 gidNumber: 6000 userPassword: tonyldap loginShell: /bin/bash homeDirectory: /home/tony =================== Anyone? Thanks in advance, Peter

2 1

Seemingly broken database
by Peter Mogensen 09 Dec '11

09 Dec '11

Hi, I have a large database with several million entries, which for a few specific entries takes very long (several minutes) to search. Looking at the debug output the search suddenly goes into a mode where it tests a lot of completely irrelevant entries and outputs a lot of "bdb_search: <number> scope not okay" messages - which takes very long time before the query ends. I've tried deleting all indexes and re-indexing with slapdindex, but the problem persists - also with 2.4.28. It's BDB 4.8.26 with back_bdb. However... loading the entire database with slapadd made the problem go away. So I suspect the id2entry or dn2id database is broken. So now I'm wondering... how do these situations occur and is there anyway to fix the database without reloading. It takes several hourse to reload, so it's not an ideal situation to have to do that every time such an event occurs. They are rather rare compared to the total number of entries, but they pop up once in a while, so it'll be a rutine job to start the database over from ldif, if that's the solution. Is there any tool to inspect the BDB database, find the problem, fix it and re-index? /Peter

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical