Hi,
On Fri, 5 Jun 2015, Adarsha S wrote:
Hi,
I've integrated openldap-2.4.25 with free-radius 2.23 and samba 3.5.1
why are you using a more than 4 year old openldap version ? Check the release history on:
http://www.openldap.org/software/release/changes.html
and you will see:
OpenLDAP 2.4.40 Release (2014/09/20) OpenLDAP 2.4.39 Release (2014/01/26) OpenLDAP 2.4.38 Release (2013/11/16) OpenLDAP 2.4.37 Release (2013/10/27) OpenLDAP 2.4.36 Release (2013/08/17) OpenLDAP 2.4.35 Release (2013/03/31) OpenLDAP 2.4.34 Release (2013/03/01) OpenLDAP 2.4.33 Release (2012/10/10) OpenLDAP 2.4.32 Release (2012/07/31) OpenLDAP 2.4.31 Release (2012/04/21) OpenLDAP 2.4.30 Release (2012/02/29) OpenLDAP 2.4.29 Release (2012/02/12) OpenLDAP 2.4.28 Release (2011/11/26) OpenLDAP 2.4.27 Release (2011/11/24) OpenLDAP 2.4.26 Release (2011/06/30) OpenLDAP 2.4.25 Release (2011/03/26)
I've a setup where I used windows 2003 server for LDAP and debian Linux machine as radius server.
when ever chase-referral is enabled, on restarting of windbind process, there is a memory jump happening in radiusd process.
On disabling chase-refferal, the radiusd process works fine with no memory jump.
radiusd process is using openlad 2.4.25 function calls for binding to LDAP server and search
Please guide me how to identify this memory leak?
update first and see if it still persists.
Greetings Christian
Thanks, Adarsha