openldap-software

openldap-software@openldap.org

2719 discussions

RE: Ghosting Data
by Mark Mcdonald 12 Mar '07

12 Mar '07

This seems related: root # ldapsearch [blah] -b ou=623392770,ou=section1,o=base dn # extended LDIF # # LDAPv3 # base <ou=623392770,ou=section1,o=base> with scope subtree # filter: (objectclass=*) # requesting: dn # # 621588406, section2, base dn: cn=621588406,ou=section2,o=base # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 Note the completely different DNs. Searching with the base set to the DN returned above returns no results, but searching on one of the attributes (ie. cn=621588406, as below) returns 5 copies of the same entry. Any ideas? I'm about to take the offending server down and run slapindex but I fear the problem is in dn2id.bdb and id2entry.bdb, which I don't believe slapindex fixes. Mark Mcdonald <> laid ink upon scroll at Monday, March 12, 2007 2:57 PM: > I was wondering if anyone has seen anything like this before: > > root# ldapsearch [blah] 'cn=username' dn cn > > # extended LDIF > # > # LDAPv3 > # base <ou=people,o=base> with scope subtree > # filter: cn=username > # requesting: dn cn > # > > # username, people, base > dn: cn=username,ou=people,o=base > cn: username > > # username, people, base > dn: cn=username,ou=people,o=base > cn: username > > # username, people, base > dn: cn=username,ou=people,o=base > cn: username > > # username, people, base > dn: cn=username,ou=people,o=base > cn: username > > # search result > search: 2 > result: 0 Success > > # numResponses: 5 > # numEntries: 4 > > > Then when I try to delete the entry: > > root # ldapdelete > Enter LDAP Password: > cn=username,ou=people,o=base > ldap_delete: No such object (32) > matched DN: ou=people,o=base > > I haven't tried doing restarting slapd or the usual > db_recover stuff yet as it's not causing a problem (yet). Is > it symptomatic of a known issue? > > slapd 2.3.30 > back-hdb > Built against db 4.2.52 (standard Ubuntu Edgy package) > > Thanks > Mark

2 1

Re: slapd-sql with unixodbc - userCertificate retrieval problem
by Pierangelo Masarati 12 Mar '07

12 Mar '07

Kevin Vargo wrote: > I've uploaded: > openldap-2.3.32-kv1-patch_support-binary-attr-070312.tgz I insist: thanks for the contribution, but you need to go through the ITS (follow instructions at <http://www.openldap.org/its/> if you want your patch to be considered. Otherwise, there is no means to keep track of it. It looks interesting; without testing it I cannot say it is correct, and it appears that you do something nasty with data that is intended to be read-only (the cname of the attribute description you're mucking with). p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: LDAP/BDB log purging
by Tony Earnshaw 12 Mar '07

12 Mar '07

Jeff Saxton wrote, on 10. mar 2007 08:18: [...] >> Do try *not* to use source-compiled db4 (in your case 4.5.20) on >> RHAS/RHEL, as it installs to non-standard (non-FHS) directories and will >> get you into all kinds of a mess later. As a pointer, try never to >> install non-rpm software on RHAS/RHEL, this after 4-5 years as Red Hat >> administrator and having done it all myself, earlier ;) >> > > Wow! I've only been a sysadmin for > 205yrs and using RedHat since 6.2 > and I never have trouble compiling from source. It's not compiling from source that's the problem, its stuffing libs and includes/headers into different directories from other similar on the *Red Hat RHEL/RHAS* system. Further, it's ok compiling and installing from source on one machine, but as soon as one has to install on multiple systems of the same type, you are costing whoever it is that's paying you far too much and involving yourself in a lot of unnecessary hassle. > If you need help meby I could give you a couple of pointers ;) From a sysadmin who's been dead for more than 100 years and couldn't spell when he was alive? Installing from packages where details of all packages are kept in a database gives gives many huge advantages, this is recognized by most, if not all, major OS vendors. I, too, was once too lazy (or ignorant) to learn to build my own program packages where I couldn't beg, borrow or steal others'. Well, now I can. --Tonni -- Tony Earnshaw Email: tonni at hetnet dot nl

3 2

How to restrict user authentication in ldapsearch ?
by JOYDEEP 12 Mar '07

12 Mar '07

Dear list, I can even query about an user as a different user. plese see below ldapsearch -H ldaps:// -u "uid=anupam" -x -W -D "uid=aftab,ou=Users,dc=kolkatainfoservices,dc=in" Here I can query about anupam as aftab. How can I restrict this ? thanks

1 0

[ldapsearch -H ldaps:// -d 255] is not working
by JOYDEEP 11 Mar '07

11 Mar '07

Dear list, I am using openldap2-2.3.19-18 under suse 10.1 and it is wotking fine at port 389 ( ldap://) Now to secure it with ssl, I have first generated a certificate with Ca.sh script comes with linux. then I have modified my /etc/openldap/slapd.conf as ========================================= TLSCipherSuite HIGH:MEDIUM:+SSLv2 TLSCertificateFile /etc/openldap/myca/servercert.pem TLSCertificateKeyFile /etc/openldap/myca/serverkey.pem TLSCACertificateFile /etc/openldap/myca/cacert.pem TLSVerifyClient never ========================================= I also modified /etc/openldap/ldap.conf as ================================= HOST 127.0.0.1:636 BASE ou=Users,dc=kolkatainfoservices,dc=in TLS_CACERT /etc/openldap/myca/cacert.pem ================================= now when I execute *ldapsearch -H ldaps:// -d 255* it asks for ====================== ldap_msgfree sasl_client_step: 2 Please enter your password: ====================== after giving the manager password which is seceret it reports ========================== ldap_msgfree ldap_perror ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: SASL(-13): user not found: no secret in database ============================================ could any one suggest what am I missing here ? thanks.

5 9

Ghosting Data
by Mark Mcdonald 11 Mar '07

11 Mar '07

I was wondering if anyone has seen anything like this before: root# ldapsearch [blah] 'cn=username' dn cn # extended LDIF # # LDAPv3 # base <ou=people,o=base> with scope subtree # filter: cn=username # requesting: dn cn # # username, people, base dn: cn=username,ou=people,o=base cn: username # username, people, base dn: cn=username,ou=people,o=base cn: username # username, people, base dn: cn=username,ou=people,o=base cn: username # username, people, base dn: cn=username,ou=people,o=base cn: username # search result search: 2 result: 0 Success # numResponses: 5 # numEntries: 4 Then when I try to delete the entry: root # ldapdelete Enter LDAP Password: cn=username,ou=people,o=base ldap_delete: No such object (32) matched DN: ou=people,o=base I haven't tried doing restarting slapd or the usual db_recover stuff yet as it's not causing a problem (yet). Is it symptomatic of a known issue? slapd 2.3.30 back-hdb Built against db 4.2.52 (standard Ubuntu Edgy package) Thanks Mark

1 0

LDAP/BDB log purging
by Lesley Walker 11 Mar '07

11 Mar '07

Running openldap 2.3.32 with bdb 4.2 (and using syncrepl if that's relevant). I need to deal with the issue of how to safely delete old bdb log files on our many replicas. In a previous thread, Aaron Richton wrote: > I'd recommend DB_LOG_AUTOREMOVE. Barring that, you can run db_archive > manually. Check Sleepycat docs for details on either. Well, I just ran db_archive and caused widespread chaos because most (all?) of the replicas stopped responding to queries. (I have yet to perform a post-mortem) I know that there's a bug in bdb 4.2 that causes logs to be held open even though they're no longer required. Upgrading bdb is not on the cards right now so I need to work around that problem by stopping and starting openldap. So the question I have just at the moment is, when I run db_archive, should openldap be running or not running? I've seen nothing in any docs that suggest it should be stopped, and the bdb docs simply imply that applications are expected to be running (but I'm not a programmer so my I interpreted it wrongly). So I ran db_archive just after starting openldap. Was that the wrong thing to do, and is it an obvious cause for the meltdown? Cheers, Lesley W -- Lesley Walker Linux Systems Administrator Opus International Consultants Ltd Email lesley.walker(a)opus.co.nz Tel +64 4 471 7002, Fax +64 4 473 3017 http://www.opus.co.nz Level 9 Majestic Centre, 100 Willis Street, PO Box 12 343 Wellington, New Zealand

8 23

bdb error with 2.4.4alpha
by Dieter Kluenter 10 Mar '07

10 Mar '07

Hi, I have just updated 2.4.3alpha to 2.4.4alpha, when restarting slapd I get following error bdb_db_open: dbenv_open(/var/lib/ldap) bdb_db_open: Database cannot be opened, err 22. Restore from backup! ====> bdb_cache_release_all bdb(o=avci,c=de): DB_ENV->lock_id_free interface requires an environment configured for the locking subsyst em bdb(o=avci,c=de): txn_checkpoint interface requires an environment configured for the transaction subsystem bdb_db_close: txn_checkpoint failed: Invalid argument (22) backend_startup_one: bi_db_open failed! (22) slapd shutdown: initiated slapd has been compiled with db-4.4 ldd slapd linux-gate.so.1 => (0xffffe000) libldap_r-2.4.so.2 => /usr/local/lib/libldap_r-2.4.so.2 (0x40036000) liblber-2.4.so.2 => /usr/local/lib/liblber-2.4.so.2 (0x40080000) libltdl.so.3 => /usr/lib/libltdl.so.3 (0x4008d000) libdb-4.4.so => /usr/local/BerkeleyDB.4.4/lib/libdb-4.4.so (0x40094000) libodbc.so.1 => /usr/lib/libodbc.so.1 (0x40170000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x401d0000) libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x401e3000) libdl.so.2 => /lib/libdl.so.2 (0x401f8000) libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0x401fc000) libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x4022c000) libresolv.so.2 => /lib/libresolv.so.2 (0x4031f000) libc.so.6 => /lib/tls/libc.so.6 (0x40332000) /lib/ld-linux.so.2 (0x40000000) Any idea what went wrong? -Dieter -- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6

2 2

syncrepl failed issue - sorry for the re-post.
by louis gonzales 10 Mar '07

10 Mar '07

Hello Group, I'm new to this forum but have a very technical question. OS: FC4 2.6.11-1.1369_FC4smp (dual Pentium) OpenLDAP: 2.3.34 (compiled from source) ./configure --prefix=/usr --mandir=/usr/share/man --datadir=/usr/share/openldap --sysconfdir=/etc/ --localstatedir=/var/openldap --enable-backends=yes --enable-sql --without-cyrus-sasl --disable-bdb --enable-crypt --with-odbc=unixodbc unixODBC: 2.2.11-3.FC4.1 libiodbc-3.52.5-1 libiodbc-devl-3.52.5-1 The error I was returned was: >>>> ./scripts/sql-test901-syncrepl failed (exit 1) All the other test for sql succeeded. Can anyone shed any light on this matter? Thank you very much! -- Email: louis.gonzales(a)linuxlouis.net WebSite: http://www.linuxlouis.net "Open the pod bay doors HAL!" -2001: A Space Odyssey "Good morning starshine, the Earth says hello." -Willy Wonka

2 1

bdb error with 2.4.4alpha
by Dieter Kluenter 09 Mar '07

09 Mar '07

Hi, I have just updated 2.4.3alpha to 2.4.4alpha, when restarting slapd I get following error: bdb_db_open: dbenv_open(/var/lib/ldap) bdb_db_open: Database cannot be opened, err 22. Restore from backup! ====> bdb_cache_release_all bdb(o=avci,c=de): DB_ENV->lock_id_free interface requires an environment configured for the locking subsyst em bdb(o=avci,c=de): txn_checkpoint interface requires an environment configured for the transaction subsystem bdb_db_close: txn_checkpoint failed: Invalid argument (22) backend_startup_one: bi_db_open failed! (22) slapd shutdown: initiated -- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software