openldap-bugs

openldap-bugs@openldap.org

1 participants
20962 discussions

Re: (ITS#5339) wrong referral from back-bdb
by h.b.furuseth＠usit.uio.no 29 Jan '08

29 Jan '08

I wrote: > !be_issuffix( op->o_bd,&op->o_req_ndn ) > which looks to me like a test for whether this function is _not_ to be > called for this database. No, that's a test if the DN is the exact suffix, not if it has the suffix. Anyway, for what it's worth "make test" succeeds with an "assert(0)" after the !be_issuffix test. -- Hallvard

1 0

ldap_result error
by Fabio Ubaldi 29 Jan '08

29 Jan '08

Hi all, I have two processes running on the same PC that receive data from an LDAP server. Each process opens a connection with a different "slapd" server (i.e each server runs on a different PC) and launches "search" requests at a fixed rate (about 100 searches/s). Each process creates a thread that polls the server responses using the API "ldap_result" the used macro are LDAP_RES_ANY and LDAP_MSG_ONE. When the two processes send the requestes one of the two "ldap_result" return with error (-1) and the error is "Can't contact the LDAP server". I tried to launch one processes and it works fine (the maximum measured rate is 800 searches/s). Also I launch the two processes alternating the search requestes and it works fine. It seems that the error happens only if the two process runs simultaneously (I use a dual core PC). Thinking of a race condition error , I used the libldap_r library to build process, but the error still remains. The openldap version is 2.3.27 both for slapd servers and the libraries. Have anyone encountered a similar error ? Thanks in advance for the reply

1 0

Re: (ITS#5339) wrong referral from back-bdb
by h.b.furuseth＠usit.uio.no 29 Jan '08

29 Jan '08

hyc(a)symas.com writes: > Can you try testing with be_chk_referrals NULL'd out? That breaks test032-chain. -- Hallvard

1 0

Re: (ITS#5339) wrong referral from back-bdb
by hyc＠symas.com 29 Jan '08

29 Jan '08

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: HEAD > OS: > URL: > Submission from: (NULL) (129.240.6.233) > Submitted by: hallvard > > > If a referral object's "ref" DN differs from the entry DN, and > you update a subordinate of the referral object, the DN part > of the referral from back-bdb is wrong. > > bash$ cat ref.ldif > dn: o=we > o: we > ref: ldap://elsewhere/o=they > objectClass: referral > objectClass: extensibleObject > > dn: cn=me,o=we > cn: me > objectClass: organizationalRole > > bash$ ldapadd ...< ref.ldif > adding new entry "o=we" > > adding new entry "cn=me,o=we" > ldap_add: Referral (10) > matched DN: o=we > referrals: > ldap://elsewhere/cn=me,o=we > > It works if NULL is changed to&e->e_name at back-bdb/referral.c line 96: > > rs->sr_ref = referral_rewrite( ref, NULL, > &op->o_req_dn, LDAP_SCOPE_DEFAULT ); > > I don't quite understand that function though: > Why does it use default_referral (slapd.conf 'referral')? That is for > use when no local backend database handles the operation, which I would > think means no database's be_chk_referrals() gets be called. And indeed > the function uses it if > !be_issuffix( op->o_bd,&op->o_req_ndn ) > which looks to me like a test for whether this function is _not_ to be > called for this database. I've never understood that function either. ;) It seems completely unnecessary, since the individual operations' code also does referral checks. Can you try testing with be_chk_referrals NULL'd out? -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#5339) wrong referral from back-bdb
by h.b.furuseth＠usit.uio.no 29 Jan '08

29 Jan '08

Full_Name: Hallvard B Furuseth Version: HEAD OS: URL: Submission from: (NULL) (129.240.6.233) Submitted by: hallvard If a referral object's "ref" DN differs from the entry DN, and you update a subordinate of the referral object, the DN part of the referral from back-bdb is wrong. bash$ cat ref.ldif dn: o=we o: we ref: ldap://elsewhere/o=they objectClass: referral objectClass: extensibleObject dn: cn=me,o=we cn: me objectClass: organizationalRole bash$ ldapadd ... < ref.ldif adding new entry "o=we" adding new entry "cn=me,o=we" ldap_add: Referral (10) matched DN: o=we referrals: ldap://elsewhere/cn=me,o=we It works if NULL is changed to &e->e_name at back-bdb/referral.c line 96: rs->sr_ref = referral_rewrite( ref, NULL, &op->o_req_dn, LDAP_SCOPE_DEFAULT ); I don't quite understand that function though: Why does it use default_referral (slapd.conf 'referral')? That is for use when no local backend database handles the operation, which I would think means no database's be_chk_referrals() gets be called. And indeed the function uses it if !be_issuffix( op->o_bd, &op->o_req_ndn ) which looks to me like a test for whether this function is _not_ to be called for this database.

1 0

Re: (ITS#5280) JLDAP waits for response for request which hasn't been sent because of connection shutdown
by Rastogi Arpit 25 Jan '08

25 Jan '08

Hi Marcin , I will be out of the city for a couple of weeks . I am copying my manager and back up owner for the issue. However I would like to know which server you are using as I tried replicating the issue but was not able to using edirectory server. the debug messages suggest that it is in search but those are not of much help till we replicate the issue . If you require any help back up owner will try to provide you the help based on his priorities. And also in the forum if any body is interested he can take the bug forward working with you . regards Arpit

1 0

Re: (ITS#5280) JLDAP waits for response for request which hasn't been sent because of connection shutdown
by rarpit＠novell.com 25 Jan '08

25 Jan '08

1 0

(ITS#5338) Wrong debug message in ldap_open
by ma＠sernet.de 24 Jan '08

24 Jan '08

Full_Name: Michael Adam Version: 2.3 and current CVS OS: Linux URL: http://samba.org/~obnox/openldap/openldap.ldap_open.diff Submission from: (NULL) (77.181.84.116) I know, ldap_open() is deprecated, but anyhow: The final debug message in ldap_open() is wrong. Success and failure are confused. A patch to fix this debug message is available at the URL mentioned below.

1 0

Re: (ITS#5337) Start Slapd failure!!!
by ando＠sys-net.it 24 Jan '08

24 Jan '08

dugangfeng(a)163.com wrote: > hi all: > I start slapd by -d -1 command,'slapd -d -1',but print this: > > > @(#) $OpenLDAP: slapd 2.2.13 (Aug 19 2004 21:22:15) $ ^^^ you're actully running OpenLDAP 2.2.13 with more recent schema files. > root@porky.build.redhat.com:/usr/src/build/440386-i386/BUILD/openldap-2.2.13/openldap-2.2.13/build-servers/servers/slapd > daemon_init: <null> > daemon_init: listen on ldap:/// > daemon_init: 1 listeners to open... > ldap_url_parse_ext(ldap:///) > daemon: initialized ldap:/// > daemon_init: 2 listeners opened > slapd init: initiated server. > slap_sasl_init: initialized! > bdb_initialize: initialize BDB backend > bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) > bdb_initialize: initialize BDB backend > bdb_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) > reading config file /etc/openldap/slapd.conf > line 5 (include /etc/openldap/schema/core.schema) > reading config file /etc/openldap/schema/core.schema > line 78 (attributetype ( 2.5.4.2 NAME 'knowledgeInformation' DESC 'RFC2256: > knowledge information' EQUALITY caseIgnoreMatch SYNTAX > 1.3.6.1.4.1.1466.115.121.1.15{32768} )) > line 87 (attributetype ( 2.5.4.4 NAME ( 'sn' 'surname' ) DESC 'RFC2256: last > (family) name(s) for which the entity is known by' SUP name )) > line 93 (attributetype ( 2.5.4.5 NAME 'serialNumber' DESC 'RFC2256: serial > number of the entity' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch > SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{64} )) > line 100 (attributetype ( 2.5.4.6 NAME ( 'c' 'countryName' ) DESC 'RFC4519: > two-letter ISO-3166 country code' SUP name SYNTAX 1.3.6.1.4.1.1466.115.121.1.11 > SINGLE-VALUE )) > /etc/openldap/schema/core.schema: line 100: AttributeType inappropriate > SUPerior: "c" > slapd shutdown: freeing system resources. > slapd stopped. > connections_destroy: nothing to destroy. > > > please help me ,thanks. You need to use consistent code/configuration. As there is no evidence of a bug, this ITS will be closed. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. 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: (ITS#5337) Start Slapd failure!!!
by hyc＠symas.com 24 Jan '08

24 Jan '08

dugangfeng(a)163.com wrote: > Full_Name: dugangfeng > Version: openldap-2.4.7 > OS: linuxAS4 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (61.181.247.78) > > > hi all: > I start slapd by -d -1 command,'slapd -d -1',but print this: Your report says OpenLDAP 2.4.7 but the debug output you provided clearly says OpenLDAP 2.2.13, from August 2004. It appears you're running the wrong version. > @(#) $OpenLDAP: slapd 2.2.13 (Aug 19 2004 21:22:15) $ > root@porky.build.redhat.com:/usr/src/build/440386-i386/BUILD/openldap-2.2.13/openldap-2.2.13/build-servers/servers/slapd > daemon_init:<null> > please help me ,thanks. The ITS is for actual bug reports, not for help requests. Use the OpenLDAP-software mailing list for help using the software. There is no OpenLDAP bug here, this ITS will be closed. If you actually paid attention to the diagnostic output it would be obvious what the problem is. The biggest help we can give you is to tell you to read more carefully. -- -- Howard Chu Chief Architect, 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:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs