openldap-software

openldap-software@openldap.org

2719 discussions

2.3 slapd_db_recover
by Craig 30 May '07

30 May '07

I had been using openldap 2.2.13 installed via yum. I installed 2.3.35 via src. But, I don't see slapd_db_recover (or any of the related apps; slapd_db_checkpoint, slapd_db_dump, etc.) I also did a search thru the 2.3.35 src files and I don't see any special configure/make flags that builds them. Am I missing something? Is there is "tools" package I need to install? TIA!

3 4

Mapping multiple object classes to one SQL table
by Néstor Boscán 29 May '07

29 May '07

Hi I'm trying to create a SQL data and metadata that manages employees that have inetOrgPerson, shadowAccount, posixAccount and sambaSamAccount. I have an LDAP_PERSON table with the columns for the attributes on those object classes. How do I populate the ldap_oc_mapping table? Regards, Néstor Boscán

2 1

OpenLDAP-OpenSSL association - reg.
by Aviator LDap 28 May '07

28 May '07

Hi Friends, I am really struk with this issue. Could you help me? In the makefile generated by the configure scipt, the TLS_LIBS value has been assigned as -lssl.a -lcrypto.a. From which location, the system finds the corresponding libssl.a and libcrypto.a? Thanks in advance!!! regards, dinesh.

4 3

Re: backend relay with empty suffix
by Nikos Voutsinas 28 May '07

28 May '07

> Please keep replies on the list. > > Nikos Voutsinas wrote: >> Indeed, a plain command line ldapseach with objectclass=*, works for me >> too. > >> Only with LDAP_Studio (an ldap browser written in java) I get this type >> of >> behavior, and I would normally ignore it, but it still troubles me >> because >> of the segfaults I am getting when ever I am trying to browse the real >> naming context with this client. This makes me think that sth goes wrong >> either with my config or slapd. > > > If the problem only appears with a specific client, I suggest you try to > single out what that client is doing differently from command-line > tools, starting from the server logs at "stats" level to check the > sequence of operations (if they're meaningless to you, you can post them > to the list). Please restrict logs to what's strictly required. Only > if nothing relevant appears, you might need to make the logs more > verbose, e.g. by adding "args" and "trace". > Please note, that it is the slapd which segfaults and not the client. This shouldn't have happened no matter what the client is doing. With the relay,massage combination, slapd ends up looking for a non-existent db key (only when searching is done through the real naming context) and with the overlay,suffixmassage combination slapd seagfaults. So, if the usage of "overlay,suffixmassage", instead of the "relay <> massage", is "legal" and if there isnt anything obviously wrong in the rest of the configuration, I might even start with debugging the segmentation fault on slapd Thanks, Nikos

3 14

Clarifications needed rearding Makefile
by Aviator LDap 28 May '07

28 May '07

Hi Friends, Kindly look at the following snippet of the Makefile. ....... ....... KRB4_LIBS = KRB5_LIBS = KRB_LIBS = SASL_LIBS = *TLS_LIBS = -lssl -lcrypto* AUTH_LIBS = *SECURITY_LIBS = $(SASL_LIBS) $(KRB_LIBS) $(TLS_LIBS) $(AUTH_LIBS)* ..... .... After this, nowhere the SECURITY_LIBS or TLS_LIBS is used in the make file. Then how the libraries -lssl and -lcrypto are linked with openLDAP build procedure? Any kind of clarification is hugely appreciated. Thanks and regards, dinesh.

1 0

diferences with openldap2.3
by Chechu Ironman 28 May '07

28 May '07

hey¡ There is some diferences betwen the version 2.3 and 2.2, when we configured the clients files, cause i have noticed that now when i do ldapsearch -x, slapd dont showme information about users, machines...anything...and before i could see all database, and now Im doing id user...and it give me backan error saying that the user dont exists...and it's in teh database... the conf is the same that i had when i had openldap 2.2.x installed some idea thanks

2 1

RE: diferences with openldap2.3
by Mark Mcdonald 27 May '07

27 May '07

How did you upgrade to 2.3? The backend databases are not compatible between minor versions (i.e. 2.2 -> 2.3) so if you did a 'slapcat' before the upgrade, deleted the DB and used 'slapadd' after the upgrade you should be OK; however if you just upgraded without exporting/importing the data you could be in trouble... _____ From: Chechu Ironman [mailto:chechuironman@gmail.com] Sent: Monday, May 28, 2007 6:18 AM To: openldap-software(a)openldap.org Subject: diferences with openldap2.3 hey¡ There is some diferences betwen the version 2.3 and 2.2, when we configured the clients files, cause i have noticed that now when i do ldapsearch -x, slapd dont showme information about users, machines...anything...and before i could see all database, and now Im doing id user...and it give me backan error saying that the user dont exists...and it's in teh database... the conf is the same that i had when i had openldap 2.2.x installed some idea thanks

1 0

server startup overhead
by Eric Irrgang 26 May '07

26 May '07

I continue to have trouble with getting a freshly started server to be responsive. One problem in particular is one that I thought had been resolved some time ago but is apparently biting me right now... With the hdb backend (at least in OL 2.3.34 and OL 2.3.35) if you perform a search with a search base deeper than the root suffix, the search takes a very long time to complete if the cache hasn't been established. In my case the difference is less than a second versus several hours. I'm not sure yet which bit of cache needs to be primed. I can switch back and forth searching with the same filter in the root and then a child search base with the same results. Is this a bug recursion or something that I just hadn't been noticing? What would be the best search to perform to prepare whatever cache is getting hit to make searches outside of the root DN faster? -- Eric Irrgang - UT Austin ITS Unix Systems - (512)475-9342

4 7

Re: LDAP and MySQL - No database selected
by Ace 25 May '07

25 May '07

I could get LDAP started with mysql. One query - ======================================================= *[root@demo libexec]# ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts* # extended LDIF # # LDAPv3 # base <> with scope baseObject # filter: (objectclass=*) # requesting: namingContexts # # dn: namingContexts: o=sql,c=RU # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 *[root@demo libexec]# ldapsearch -LLL -s sub -b "o=sql,c=RU" "(objectClass=*)" *SASL/DIGEST-MD5 authentication started Please enter your password: ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: SASL(-13): user not found: no secret in database ====================================================== Why is my second LDAP search not working? Anyone has samples on inserting/searching records from LDAP with MySQL backend? On 5/24/07, Ace <rajan.halade(a)gmail.com> wrote: > > I got it working now after I restrted my Linux....Its weird...but its > true! > > Thanks for you help! > > > On 5/23/07, Ace <rajan.halade(a)gmail.com> wrote: > > > > The funny part here, my odbc test result - > > > > ====================================================== > > 1: SQLDriverConnect = [MySQL][ODBC 3.51 Driver]Could not determine the > > driver name; could not lookup setup library. DSN=(test) > > (0) SQLSTATE=HY000 > > 1: ODBC_Connect = [MySQL][ODBC 3.51 Driver]Could not determine the > > driver name; could not lookup setup library. DSN=(test) > > (0) SQLSTATE=HY000 > > ====================================================== > > > > Where as LDAP is able to connect to MySQL. I am using "test" database > > from MySQL and DSN name is "test". > > > > One more thing, why was slapd looking for /tmp/mysql.sock? I had > > specified Socket = /var/lib/mysql/mysql.sock > > > > Here is my odbc.ini - > > > > > > ; begin odbc.ini > > [ODBC Data Sources] > > test = Connector/ODBC 3.51 Driver DSN > > > > [test] > > Driver = /usr/lib/libmyodbc3.so > > Description = Connector/ODBC 3.51 Driver DSN > > Server = localhost > > DSN = test > > Port = 3306 > > Socket = /var/lib/mysql/mysql.sock > > User = root > > Password = mysql > > Database = test > > ServerType = MySQL > > Option = > > TraceFile = /var/log/mysql_test_trace.log > > Trace = 0 > > > > [Default] > > Driver = /usr/lib/libmyodbc3.so > > Description = Connector/ODBC 3.51 Driver DSN > > Server = localhost > > DSN = test > > Port = 3306 > > Socket = /var/lib/mysql/mysql.sock > > User = root > > Password = mysql > > Database = test > > ServerType = MySQL > > Option = > > TraceFile = /var/log/mysql_test_trace.log > > Trace = 0 > > ;end odbc.ini > > > > > > > > On 5/23/07, Gabriel Stein <gabrielstein(a)gmail.com > wrote: > > > > > > What´s your result for odbctest ou iodbctest? This command shows your > > > ODBC connection? > > > > > > And more: you set your slapd.conf with your ODBC Connection Name, not > > > your MySQL dbname. > > > > > > For example, if you have a database with name ldap and setup a ODBC > > > connection with name test, you need set test on your slapd.conf > > > > > > An ODBC Connection for example, in your /etc/odbc.ini > > > > > > [ODBC Data Sources] > > > test = MySQL ODBC 2.50 Driver DSN > > > > > > [test] > > > Driver = /usr/local/lib/libmyodbc.so > > > Description = MySQL ODBC 2.50 > > > Driver DSN > > > DSN = test > > > Server = localhost > > > PORT = 3306 > > > SOCKET = /var/lib/mysql/mysql.sock > > > User = *valid_user* > > > Password = *valid_passwd* > > > Database = ldap > > > ReadOnly = no > > > ServerType = MySQL > > > > > > FetchBufferSize = 99 > > > ServerOptions = > > > ConnectOptions = > > > OPTION = 3 > > > TraceFile = /var/log/mysql_test_trace.log > > > Trace = 0 > > > > > > > > > Cheers, > > > > > > On 5/23/07, Ace <rajan.halade(a)gmail.com > wrote: > > > > > > > > Hi Friends, > > > > > > > > I am trying to configure LDAP with MySQL 5.0 as backend. I am > > > > using Connector/ODBC 3.51 and LDAP 2.3.32 built from sources. > > > > While starting slapd I get following error - > > > > > > > > =============================================== > > > > backsql_load_schema_map(): oc_query "SELECT > > > > id,name,keytbl,keycol,create_proc,delete_proc,expect_return FROM > > > > ldap_oc_mappings" > > > > backsql_load_schema_map(): error executing oc_query: > > > > Return code: -1 > > > > nativeErrCode=1046 SQLengineState=3D000 msg="[MySQL][ODBC 3.51Driver][ > > > > mysqld-5.0.27-standard]No database selected" > > > > ==>backsql_free_db_conn() > > > > =============================================== > > > > > > > > My odbc.ini file has all the details and I can see in slapd log that > > > > its getting dbname before connective to MySQL server. slapd.conf has > > > > dbname = test. > > > > > > > > Thanks in advance! > > > > -- > > > > Cheers, > > > > Rajan > > > > > > > > > > > > > > > > -- > > > /\ > > > Gabriel Stein > > > gabrielstein(a)gmail.com > > > MSN: gabrielstein(a)hotmail.com > > > Administrador de Redes - > > > Network Administrador > > > Linux User #223750 > > > 51-92796310 > > > Porto Alegre - RS - Brasil > > > > > > > > > > > > > -- > I may be miles away... but I am just a mail away.... so keep mailing...!!! > > Cheers, > Rajan

3 2

Re: duplicate attributetype: 2.5.4.2
by Pedro Espinoza 25 May '07

25 May '07

On 5/25/07, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > > --On Friday, May 25, 2007 2:31 AM -0700 Howard Chu <hyc(a)symas.com> wrote: > > > Quanah Gibson-Mount wrote: > >> --On Thursday, May 24, 2007 8:03 PM -0400 Pedro Espinoza > >> <raindoctor(a)gmail.com> wrote: > >> > >>> Gurus: > >>> > >>> I am newbie to this ldap thing. I followed garytt's installation > guide. > >>> When I tried to start "slapd", I got the following error. I searched > on > >>> net, but in vain. Can you shed some light on it, and how to rectify > it. > >>> > >>> /usr/local/etc/openldap/schema/core.schema: line 77: Duplicate > >>> attributeType: "2.5.4.2" > >> > >> Ignore this warning, it is harmless. > > > > Actually it most likely indicates that you're using an older core.schema > > file with a newer slapd, and it's not just a warning, it's a fatal > error. > > Oh, I was thinking of those annoying schema warning messages that have > been > going on in 2.3 for a while. I have figured out: my slapd.conf contains two entries for core.schema. I removed the other one, it is working, Thanks, Pedro.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software