openldap-technical

openldap-technical@openldap.org

9 participants
9902 discussions

Question from a LMDB user
by Tao Chen 04 Nov '15

04 Nov '15

Hi Sir/Madam, Recently I'm trying to use LMDB to store and randomly acess large amount of features. Each feature blob is 16kB. Before trying LMDB, I just stack all the features together into one huge binay file, and use seek function in C++ to access each feature. Since the feature size is fixed, I can easily compute the address of each feature in the file. Then I tried LMDB. The value is the feature as it is. The key is "1", "2", "3", .... Since 16kB is exactly 4 x page_size, adding the key and header, each feature will occupy 5 x page_size, so the db file on disk is about 1.25 times of the previous binary file, this is already a disadvantage for LMDB, but I still hope there can be some efficiency trade-off. I use LDMB++ C++ wrapper to access features. Next, I compared two approach by accessing the same random 1% features from about 300k features. Before the test, I use vmtouch to evict both files from memory cache. The result is surprising. The one use LMDB is 1.5 times slower than the raw binary file (30s vs 20s). Is this because the size of feature (exactly 4 pages)? Do I understand the use of LMDB incorrectly? Thank your for your time! Best Regards, Tao Chen

2 1

Developing modules
by dev 04 Nov '15

04 Nov '15

Hi, I'd like to take a stab at porting the radius contrib module to FreeRadius. Can someone point me in the direction of documentation for the openldap module format? I see there is init_module() and term_module() defined in the source for the modules I've looked at but the rest is guesswork. I've poked around Google a bit but only so far ran across a post in 2011 asking the same question. Thanks

2 1

ldapsearch over SSL can not bind
by Matthias Apitz 02 Nov '15

02 Nov '15

Hello, I'm trying to make from FreeBSD a LDAPsearch in some Novell eDirectory with the following command: $ ldapsearch -Z -H ldaps://romega:1027 -b 'ou=person,o=uni' -D 'cn=XXXXXXXXXX,ou=service,o=uni' -w XXXXXXXXXX ldap_start_tls: Can't contact LDAP server (-1) additional info: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed (self signed certificate in certificate chain) ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) The credentials are fine and are working without any problem, for example from Windos clients (JXplore) or from a Java written client running on my laptop. Openssl can connect fine too. Any ideas what could be wrong? Btw: Someone here who managed to work JXplore in FreeBSD? There is an installer for it which can not find libstdc++.so.4 on my system (I have libstdc++.so.6). Vy 73 matthias -- Matthias Apitz, ✉ guru(a)unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045

4 3

retrieving information about deleted objects
by Matthias Apitz 02 Nov '15

02 Nov '15

Hello, We produce for production environments an IDMsystem which is able to publish/dublicate changes in OpenLDAP/LDAP directories to other management databases and vice versa. This works fine in most of the cases of changes in LDAP. The only problem we see, is get information about deletion of objects (users) which were done while the IDMsystem was either down or network not available. What is the correct way to search for deleted objects. We have read about a filter search, based on 'isDeleted=*' or 'isDeleted=TRUE. But we can not get any result with this. Thanks for some hints about this. matthias -- Matthias Apitz, ✉ guru(a)unixarea.de, 🌐 http://www.unixarea.de/ ☎ +49-176-38902045

4 3

Consumer not Sync'ing
by Kartik Vashishta 02 Nov '15

02 Nov '15

Team, Consumer is connecting to master but not sync'ing. I am a newbie so any ideas will be appreciated. "test3" is the consumer "elasticsearch1" is the master [root@test3 tmp]# netstat -anlp | grep 389 tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 6745/slapd tcp 0 0 192.168.1.51:53121 192.168.1.196:389 TIME_WAIT - tcp 0 0 192.168.1.51:53120 192.168.1.196:389 TIME_WAIT - tcp 0 0 192.168.1.51:53113 192.168.1.196:389 TIME_WAIT - tcp 0 0 192.168.1.51:53118 192.168.1.196:389 TIME_WAIT - tcp 0 0 192.168.1.51:53119 192.168.1.196:389 TIME_WAIT - tcp 0 0 192.168.1.51:53122 192.168.1.196:389 TIME_WAIT - tcp 0 0 192.168.1.51:53124 192.168.1.196:389 TIME_WAIT - tcp 0 0 192.168.1.51:53123 192.168.1.196:389 TIME_WAIT - tcp6 0 0 :::389 :::* LISTEN 6745/slapd [root@test3 tmp]# I am following this document: http://www.server-world.info/en/note?os=CentOS_7&p=openldap&f=5 Regards, Kartik Vashishta

2 1

"memberof" function for memberUid attribute.
by Andi Zulfadli 01 Nov '15

01 Nov '15

Dear Master. Please help, What is the format for filter the member of group? we know that "memberof" format works in member attribute in openldap group entry format. example attribute : dn: cn=Admins,ou=Users,o=<org-id>,dc=jumpcloud,dc=com *member: uid=john,ou=Users,o=<org-id>,dc=jumpcloud,dc=commember: uid=mary,ou=Users,o=<org-id>,dc=jumpcloud,dc=com*objectClass: top objectClass: groupOfNames description: tagGroup cn: Admins ou: Admins example filter : example: (&(objectClass=person)(memberOf=CN=name-of-the-group,OU=xample,DC=com)) But how about if my openldap group member attribute using memberUid as attibute member's group. dn: cn=Admins,ou=Users,o=<org-id>,dc=jumpcloud,dc=com *memberUid: johnmemberUid: mary*objectClass: top objectClass: groupOfNames description: tagGroup cn: Admins ou: Admins How can i use "memberof" filter format in my openLDAP? Thank you very much. iam sorry for my ambiguity.

2 4

When is it ok to call MDB_NEXT_MULTIPLE?
by Bryan Matsuo 31 Oct '15

31 Oct '15

The docs imply that the MDB_NEXT_MULTIPLE cursor operation may only be used following MDB_GET_MULTIPLE (or another MDB_NEXT_MULTIPLE). Is that the case? In my experience MDB_NEXT_MULTIPLE has behaved the same as MDB_GET_MULTIPLE following MDB_NEXT_NODUP. That was a desirable thing in my case. I am wondering if that behavior can be depended on. The documentation for MDB_NEXT_MULTIPLE is probably technically correct. But it is vague. I don't understand what "preparing the cursor" entails.

1 0

Binding mdb_set_compare with Go
by Bryan Matsuo 31 Oct '15

31 Oct '15

openldap-technical, I am working on some Go (golang) bindings[1] for the LMDB library and I have some interest in exposing the functionality of mdb_set_compare (and mdb_set_dupsort). But it is proving difficult and I have a question about the function(s). Calling mdb_set_compare from the Go runtime is challenging. Using C APIs with callbacks comes with restrictions[2][3]. I believe it impossible to bind these functions way that is flexible, as one would expect. A potential change to LMDB that would make binding drastically easier is having MDB_cmp_func to take a third "context" argument with type void*. Then a binding could safely use an arbitrary Go function for comparisons. Is it possible for future versions of LMDB to add a third argument to the MDB_cmp_func signature? Otherwise would it be acceptable for a variant API to be added using a different function type, one accepting three arguments? Thanks for the consideration. Cheers, - Bryan [1] Go bindings -- https://github.com/bmatsuo/lmdb-go [2] Cgo pointer restrictions -- https://github.com/golang/proposal/blob/master/design/12416-cgo-pointers.md [3] Cgo documentation -- https://golang.org/cmd/cgo/

4 10

Re: Unable to build LMDB on SUSE Linux: undefined reference to pthread_mutexattr_setrobust / pthread_mutex_consistent
by Howard Chu 30 Oct '15

30 Oct '15

> Hello, > > I am trying to build LMDB libraries from source on SUSE Linux using gcc 4.7.2 to try for an experimental project at work. I am getting some build errors. I see pthread.h and libpthread.{a/so} installed in /usr/include and /usr/lib64, respectively. But I do not see these functions in the header file or in the library. Maybe the pthread library version is old. I am not sure. I tried searching on the web, but I was not able to understand how to install a different version of the pthread library (it seems to come packaged with the OS?). I do not have admin rights so I would try installing in my local area. > > Can someone please advise on things I can try to resolve this issue? Thank you for your time and help. You're not using a released branch of LMDB code. When you use a development branch you're expected to actually know how your development environment works. > (P.S. I had built LMDB successfully on a Mac OS X machine (home computer) without any issues) > > $ make > gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast -Wuninitialized -c mdb.c > mdb.c: In function ‘mdb_mutex_failed’: > mdb.c:9827:4: warning: implicit declaration of function ‘pthread_mutex_consistent’ [-Wimplicit-function-declaration] > gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast -Wuninitialized -c midl.c > ar rs liblmdb.a mdb.o midl.o > ar: creating liblmdb.a > gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast -Wuninitialized -fPIC -c mdb.c -o mdb.lo > mdb.c: In function ‘mdb_mutex_failed’: > mdb.c:9827:4: warning: implicit declaration of function ‘pthread_mutex_consistent’ [-Wimplicit-function-declaration] > gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast -Wuninitialized -fPIC -c midl.c -o midl.lo > gcc -pthread -shared -o liblmdb.so mdb.lo midl.lo > gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast -Wuninitialized -c mdb_stat.c > gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast -Wuninitialized mdb_stat.o liblmdb.a -o mdb_stat > liblmdb.a(mdb.o): In function `mdb_env_setup_locks': > /nfs/pdx/proj/dt/tctg03/pgupta6/lmdb-mdb.master/libraries/liblmdb/mdb.c:4642: undefined reference to `pthread_mutexattr_setrobust' > liblmdb.a(mdb.o): In function `mdb_mutex_failed': > /nfs/pdx/proj/dt/tctg03/pgupta6/lmdb-mdb.master/libraries/liblmdb/mdb.c:9827: undefined reference to `pthread_mutex_consistent' > collect2: error: ld returned 1 exit status > make: *** [mdb_stat] Error 1 > > My environment is as follows: > > $ more /etc/SuSE-release > SUSE Linux Enterprise Server 11 (x86_64) > VERSION = 11 > PATCHLEVEL = 2 > > $ uname -a > Linux 3.0.101-0.7.29.1.8482.4.PTF-default #1 SMP Tue May 5 16:00:34 UTC 2015 () x86_64 x86_64 x86_64 GNU/Linux SUSE Linux Enterprise Server 11 definitely supports robust mutexes, since they actually list bug fixes for that feature. https://www.suse.com/support/update/announcement/2013/suse-su-20131852-1.ht… But it's possible that the function definitions are hidden or renamed. Look for them in /usr/include/pthread.h and then supply the appropriate preprocessor flags to expose their definitions. You may need to adjust the LMDB code to use pthread_mutexattr_setrobust_np and pthread_mutex_consistent_np. If you don't know how to do this, stick with the actual release branch. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Ch

1 0

Attribute syntax and search filters
by Michael 30 Oct '15

30 Oct '15

I originally had a request from developers to allow substr searches on the "drawId" integer attribute you see below. As you know, substr searches on integers are not supported so I changed the schema and modified the attribute type to a numeric string. This worked as expected but now they are coming back to me asking why negative numbers are not being matched in their search filters. After some reading I understand the numeric string syntax is used to hold strings comprised of one or more ASCII numeric digits digits and/or space characters. The hyphen is not allowed, so it is not possible to represent negative values. Is there any alternative here? Original schema entry attributetype ( 3.0.0.3 NAME 'drawId' DESC 'ID of the retailer a user is assigned to' EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE ) Current schema entry. attributetype ( 3.0.0.3 NAME 'drawId' DESC 'ID of the retailer a user is assigned to' EQUALITY numericStringMatch SUBSTR numericStringSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.36 SINGLE-VALUE )

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