openldap-devel

openldap-devel@openldap.org

1416 discussions

connection management, thread pool
by Howard Chu 09 Oct '11

09 Oct '11

It's looking like using a single mutex-controlled thread pool is a major bottleneck in the slapd frontend. Thinking it over, I've hit a number of different ideas but nothing without drawbacks. Ideally we would get rid of the distinction between listener threads and worker threads, and only have worker threads. Each thread would be responsible for a fraction of the open sockets, and service them directly instead of queueing work into a thread pool. This would essentially mimic the behavior of SLAPD_NO_THREADS, just duplicated N times. The upsides of such an approach are numerous; a whole slew of locks completely disappear from the design and we'd be keeping work local to the CPU that originally received a request. The obvious downside is that Abandon/Cancel ops would never be useful (as they currently are not useful in single-threaded slapd). I.e., since the thread responsible for a connection will always be occupied in actually processing an operation, it will never come back to read the next request on the connection (e.g. Abandon) until the current op is already finished. A possible solution to that would be to always do a quick poll in send_ldap_response() etc. to check for new requests on a connection before sending another reply. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Overlay Mod - AccessLog + back-ldap
by Jim Finn 30 Sep '11

30 Sep '11

I am in the process extending the capability of the accesslog overlay to include logging of the client IP address of each request/op. I have successfully implemented this on 2.3.42. The next step is to optionally record the IP address of the server fielding the request. I'm particularly interested which server back-ldap is using to respond to the request. The closest I have come to finding the back-end server is li->li_url but this is just the uri list as config'd in slapd.conf. I'm hoping to find some assistance in determining the back-end server. Here is the changes that have been made to 2.3.43/servers/slapd/overlays/accesslog.c: ###BEGIN DIFF### 35d34 < #include "../back-ldap/back-ldap.h" 167c166 < *ad_reqReferral, *ad_reqOld, *ad_reqClient, *ad_reqServer; --- > *ad_reqReferral, *ad_reqOld; 321,328d319 < { "( " LOG_SCHEMA_AT ".30 NAME 'reqClient' " < "DESC 'Client Source Address' " < "SYNTAX OMsDirectoryString " < "SINGLE-VALUE )", &ad_reqClient }, < { "( " LOG_SCHEMA_AT ".31 NAME 'reqServer' " < "DESC 'Destination Server Address' " < "SYNTAX OMsDirectoryString " < "SINGLE-VALUE )", &ad_reqServer }, 345c336 < "reqResult $ reqMessage $ reqReferral $ reqClient $ reqServer) )", --- > "reqResult $ reqMessage $ reqReferral ) )", 839,863d829 < //jfinn(a)searshc.com: Log Client IP Address/Hostname/URI to "reqClient" < // attribute. < < BerValue clientIP; < clientIP.bv_val = malloc(255); < strcpy(clientIP.bv_val,op->o_hdr->oh_conn->c_peer_name.bv_val); < strtok(clientIP.bv_val, "="); // use strtok to sanitize the string < clientIP.bv_val = strtok (NULL, ":"); // IP=x.x.x.x:XXXX ---> x.x.x.x < clientIP.bv_len = strlen (clientIP.bv_val); < attr_merge_one( e, ad_reqClient, &clientIP, NULL ); < < // end Client IP address logging < < //jfinn(a)searshc.com: Log Server IP Address/Hostname/URI to "reqServer" < // attribute for use with back-ldap backend. < ldapinfo_t *ldap_info = (ldapinfo_t *)op->o_bd->be_private; < BerValue serverIP; < serverIP.bv_val = malloc(255); < // ldap_info->li_uri is just the URI string as config'd in slapd.conf. < serverIP.bv_val = ldap_info->li_uri; < serverIP.bv_len = strlen(serverIP.bv_val); < attr_merge_one( e, ad_reqServer, &serverIP, NULL ); < < // end Server IP address logging < ###END DIFF### Thanks in advance for your assistance! Jim Finn This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you.

1 0

Plans for 2.4.27?
by Michael Ströder 30 Sep '11

30 Sep '11

HI! Are there plans for a 2.4.27 release with the recent syncrepl fixes? Ciao, Michael.

2 5

Re: ldap_get_value returns corrupt pointer
by kyle king 23 Sep '11

23 Sep '11

On 09/20/2011 06:21 PM, kyle king wrote: > Under heavy threaded use ldap_get_value returns a corrupted memory > pointer, not a char pointer pointer that was specified. I have narrowed the corruption problem down to the file libraries/libldap/get_values.c apoximatly line 80 the ber_scanf in the if statement. When it work on my machine, it returns pointers for 'vals' such as: vals pointer: 0x105c920 and when it fails: vals pointer 0x7f6130004c20 Kyle A. King Quentus Technologies, INC Cell Phone: 703-635-9512 Work Phone: 253-218-6030 Email: kyle.king(a)quentustech.com

4 3

Re: ldap_get_value returns corrupt pointer
by kyle king 23 Sep '11

23 Sep '11

I found out I was using a deprecated function then new one > ldap_get_value_len deals with this issue. -- Kyle A. King Quentus Technologies, INC Cell Phone: 703-635-9512 Work Phone: 253-218-6030 Email: kyle.king(a)quentustech.com

1 0

Re: openldap.git branch mdb.master updated. 0ab841598ffb490f4246f892248f0b409e411cc1
by Howard Chu 18 Sep '11

18 Sep '11

> - Log ----------------------------------------------------------------- > commit 0ab841598ffb490f4246f892248f0b409e411cc1 > Author: Howard Chu<hyc(a)symas.com> > Date: Sun Sep 18 16:39:18 2011 -0700 > > Fix 09006ccec7928c9cf53bca6abe741e8d4d466c98 > > Check for stale DBs was in the wrong place. Since back-mdb does no caching, it's OK to run slapadd while slapd is running; slapd will see the new data immediately. In fact you can run multiple slapds on the same database and they will stay perfectly in sync. I'm not sure that that's actually a useful thing to do, but you can do it if you want... -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 2

back-sql maintenance
by Shawn A. Wilson 18 Sep '11

18 Sep '11

I have been using OpenLDAP on Linux for a number of years and am now evaluating a transition towards the back-sql backend but I understand this is no longer actively maintained. Would somebody on this list be so kind as to go into some of the reasoning behind this lack of development? Is there now a better alternative for LDAP integration with an existing SQL schema? Is the methodology of back-sql seriously flawed? Is it just a lack of volunteers? I have encountered a possible bug and, having the resources, would like to help maintain this SQL backend if that is the appropriate thing to do. Thanks, -shawn

2 1

Is JDBC-LDAP still maintained?
by Alan Evans 15 Sep '11

15 Sep '11

I am trying to find if anyone still actively maintains JDBC-LDAP. I have encountered a problem and I have tracked it back to what I think is the problem but I am not a java developer so I cannot say for certain. I posted to the list at MyVirtualDirectory some time ago since it was their binary distribution I was using, but I never received a response. Does the OpenLDAP community still maintain the JDBC-LDAP driver or does the community serve as an archival place? It looks like the last commits to the git repo were years ago. Regards, -Alan

1 0

Re: openldap.git branch mdb.master updated. 0533f80364810fb89b1feac892f9397fffe6ebd0
by Howard Chu 14 Sep '11

14 Sep '11

> - Log ----------------------------------------------------------------- > commit 0533f80364810fb89b1feac892f9397fffe6ebd0 > Author: Howard Chu<hyc(a)symas.com> > Date: Wed Sep 14 11:31:27 2011 -0700 > > Add MacOSX support > > mmap() with FIXEDMAP fails, otherwise things work. Interestingly enough, it succeeds under gdb. At a guess, address space layout randomization prevents it from working in the normal case. I haven't bothered to dig into this further; as far as I'm concerned MacOSX is a broken OS and isn't worth the time. (google "macosx process shared mutexes" and follow the trail thru semaphores and all the other brokenness if you feel like wasting a few hours of your life as I just did.) -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

MDB (not) on MacOSX
by Howard Chu 07 Sep '11

07 Sep '11

Apparently MacOSX doesn't support process-shared mutexes, so mdb startup always fails. We can look into a workaround later, but for now, don't expect this combination to work. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

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-devel