openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

(ITS#5226) ldapadd: invalid format (line 1) entry: ""
by babu.shanmugham＠gmail.com 08 Nov '07

08 Nov '07

Full_Name: Babu Shanmugam Version: 2.1 OS: windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.230.0.45) Hey, I am stuck u with this error....ldapadd: invalid format (line 1) entry: "".... I am not sure which file to change, either init.ldif or slapd.conf. My files contents looks like below. 1..slapd.conf. database bdb suffix "dc=mymozilla,dc=com" rootdn "cn=Manager,dc=mymozilla,dc=com" rootpw passmozilla directory C:/openldap/var/openldap-data index objectClass eq 2. init.ldif : dn: dc=mymozilla,dc=com objectClass: eq objectClass: organization objectClass: eq description: Description of your domain o: Something else about your domain dc: mymozilla When i run this command, ldapadd -x -D "cn=Manager,dc=mymozilla,dc=com" -w passmozilla -v -f init.ldif , i get the following error init.ldif ldap_initialize( <DEFAULT> ) ldapadd: invalid format (line 1) entry: "" Please let me know how to overcome this. Regards.... Babu Shanmugam

1 0

Re: (ITS#5225) unexpected results in slapadd
by quanah＠zimbra.com 08 Nov '07

08 Nov '07

--On Thursday, November 08, 2007 1:01 PM -0500 "Allan E. Johannesen" <aej(a)WPI.EDU> wrote: >>>>>> "quanah" == Quanah Gibson-Mount <quanah(a)zimbra.com> writes: > > quanah> --On Thursday, November 08, 2007 4:46 PM +0000 aej(a)wpi.edu wrote: >>> Full_Name: Allan E. Johannesen Version: 2.4.6 OS: RHEL4 i686 URL: >>> http://users.wpi.edu/~aej Submission from: (NULL) (130.215.24.208) >>> >>> >>> Dependent on load flags (I normally have been using -w -q), I get >>> various results. Assertion failure, segfault, or success. > > quanah> Looks like it is related to the use of the -w flag, since your > segfault quanah> and assertions were hit when it was part of the command. > Thanks for quanah> the example bits to reproduce. > > Although the schemas probably don't come into play, and could probably be > removed from the config, I also put the two wpi schemas in > http://users.wpi.edu/~aej > > I forgot them when I was submitting. Please make sure you CC the ITS system on all emails about this bug. Thanks. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5225) unexpected results in slapadd
by quanah＠zimbra.com 08 Nov '07

08 Nov '07

--On Thursday, November 08, 2007 4:46 PM +0000 aej(a)wpi.edu wrote: > Full_Name: Allan E. Johannesen > Version: 2.4.6 > OS: RHEL4 i686 > URL: http://users.wpi.edu/~aej > Submission from: (NULL) (130.215.24.208) > > > Dependent on load flags (I normally have been using -w -q), I get various > results. Assertion failure, segfault, or success. Looks like it is related to the use of the -w flag, since your segfault and assertions were hit when it was part of the command. Thanks for the example bits to reproduce. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5225) unexpected results in slapadd
by aej＠wpi.edu 08 Nov '07

08 Nov '07

Full_Name: Allan E. Johannesen Version: 2.4.6 OS: RHEL4 i686 URL: http://users.wpi.edu/~aej Submission from: (NULL) (130.215.24.208) Dependent on load flags (I normally have been using -w -q), I get various results. Assertion failure, segfault, or success. utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# rm /var/openldap-data/* utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# ln /var/openldap-bdb/DB_CONFIG /var/openldap-data/ utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# servers/slapd/slapadd -w -q -f /usr/local/etc/openldap/slapd.utility5.conf < users.ldapv2.2007.11.08.ldif slapadd: entry.c:760: entry_encode: Assertion `i == a->a_numvals' failed. Abort utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# rm /var/openldap-data/* utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# ln /var/openldap-bdb/DB_CONFIG /var/openldap-data/ utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# servers/slapd/slapadd -q -f /usr/local/etc/openldap/slapd.utility5.conf < users.ldapv2.2007.11.08.ldif utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# rm /var/openldap-data/* utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# ln /var/openldap-bdb/DB_CONFIG /var/openldap-data/ utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# servers/slapd/slapadd -w -f /usr/local/etc/openldap/slapd.utility5.conf < users.ldapv2.2007.11.08.ldif Segmentation fault utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# rm /var/openldap-data/* utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# ln /var/openldap-bdb/DB_CONFIG /var/openldap-data/ utility5:/tools/src/openldap/RHEL4-i686/openldap-2.4.6# servers/slapd/slapadd -f /usr/local/etc/openldap/slapd.utility5.conf < users.ldapv2.2007.11.08.ldif I've placed DB_CONFIG, users.ldapv2.2007.11.08.ldif, and slapd.utility5.conf in http://users.wpi.edu/~aej/

1 0

Re: (ITS#5187) test020-proxycache failing in RE_2_4
by rhafer＠suse.de 08 Nov '07

08 Nov '07

On Donnerstag, 8. November 2007, you wrote: > <quote who="Ralf Haferkamp"> > > > On Donnerstag, 8. November 2007, rhafer(a)suse.de wrote: > >> I think I found a way. > >> 1. The SLAPD_ABANDON/op->o_abandon part of the cleanup handler will now > >> only get executed if the final result for the search has not been > >> received > >> (caching_reason == PC_IGNORE). > >> 2. Additionally, to add the entries to the cache, I do no longer use the > >> original Connection Object but create a new one > >> (connection_fake_init()), > >> because the op->o_abandon will be set for the original connection as > >> soon > >> as the client closes it. > >> > >> I'll do some more testing locally an submit this to HEAD later for more > >> external testing. > > > > Fix submitted to HEAD. Please test (preferably on the machine that caused > > this > > test to fail most often ;) ). > > I'll try this tonight. > > Just to clarify, this is a fix in the code, rather than the test, which I > thought Howard had changed? Yes, it is a fix in the pcache code. The fix in the testcase was only done temporarely in the RE24 branch (HEAD was not changed). I intend to remove it as soon as I get positive feedback. -- Ralf

1 0

Re: (ITS#5187) test020-proxycache failing in RE_2_4
by ghenry＠OpenLDAP.org 08 Nov '07

08 Nov '07

<quote who="Ralf Haferkamp"> > On Donnerstag, 8. November 2007, rhafer(a)suse.de wrote: >> I think I found a way. >> 1. The SLAPD_ABANDON/op->o_abandon part of the cleanup handler will now >> only get executed if the final result for the search has not been >> received >> (caching_reason == PC_IGNORE). >> 2. Additionally, to add the entries to the cache, I do no longer use the >> original Connection Object but create a new one >> (connection_fake_init()), >> because the op->o_abandon will be set for the original connection as >> soon >> as the client closes it. >> >> I'll do some more testing locally an submit this to HEAD later for more >> external testing. > Fix submitted to HEAD. Please test (preferably on the machine that caused > this > test to fail most often ;) ). I'll try this tonight. Just to clarify, this is a fix in the code, rather than the test, which I thought Howard had changed? > > -- > Ralf >

1 0

Re: (ITS#5187) test020-proxycache failing in RE_2_4
by rhafer＠suse.de 08 Nov '07

08 Nov '07

On Donnerstag, 8. November 2007, rhafer(a)suse.de wrote: > I think I found a way. > 1. The SLAPD_ABANDON/op->o_abandon part of the cleanup handler will now > only get executed if the final result for the search has not been received > (caching_reason == PC_IGNORE). > 2. Additionally, to add the entries to the cache, I do no longer use the > original Connection Object but create a new one (connection_fake_init()), > because the op->o_abandon will be set for the original connection as soon > as the client closes it. > > I'll do some more testing locally an submit this to HEAD later for more > external testing. Fix submitted to HEAD. Please test (preferably on the machine that caused this test to fail most often ;) ). -- Ralf

1 0

RE: (ITS#5215) Use of ln is hardcoded in some files
by h.b.furuseth＠usit.uio.no 08 Nov '07

08 Nov '07

emmanuel.duru(a)atosorigin.com writes: > Then with MSYS, I get an error when running make on servers/slapd > Makefile: in case there is no extra LDFLAG, (...) Try this patch: --- servers/slapd/Makefile.in~ 2007-02-14 16:59:43.000000000 +0100 +++ servers/slapd/Makefile.in 2007-11-08 15:40:32.475898000 +0100 @@ -157,3 +157,3 @@ slapd.def: libbackends.a liboverlays.a version.o - @for i in $(LDFLAGS) ; do \ + @for i in XX $(LDFLAGS) ; do \ path=`expr "$$i" : "-L$.*$"`; \ @@ -169,3 +169,4 @@ base=`expr "$$i" : "-l$.*$"`; \ - for p in $$paths ; do \ + for p in " " $$paths ; do \ + test "x$$p" = "x " && continue ; \ for ext in la dll dll.a a ; do \ -- Regards, Hallvard

1 0

Re: ITS#5212 command that caused the crash
by hyc＠symas.com 08 Nov '07

08 Nov '07

tonni(a)hetnet.nl wrote: > Howard Chu skrev, on 07-11-2007 04:14: >> That's all we needed. Fixed now in HEAD. > > Do you happen to have a patch handy? I don't feel like waiting for > 2.4.7, this is the only serious bug I've found to date with 2.4.6. http://www.openldap.org/lists/openldap-commit/200711/msg00010.html -- -- 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

RE: (ITS#5215) Use of ln is hardcoded in some files
by emmanuel.duru＠atosorigin.com 08 Nov '07

08 Nov '07

OK, forget about my remark on Cygwin/MinGW. However, you should update the "Porting OpenLDAP" FAQ to mention MSYS. Then with MSYS, I get an error when running make on servers/slapd Makefile: in case there is no extra LDFLAG, the lines @for i in $(LDFLAGS) ; do \ path=`expr "$$i" : "-L$.*$"`; \ if test $$? != 0; then continue; fi; \ paths="$$paths $$path"; \ done; \ cause a sh error: "syntax error near unexpected token ';'" -----Message d'origine----- De : Howard Chu [mailto:hyc@symas.com] Envoyé : mercredi 7 novembre 2007 04:08 À : emmanuel.duru(a)atosorigin.com Cc : openldap-its(a)openldap.org Objet : Re: (ITS#5215) Use of ln is hardcoded in some files emmanuel.duru(a)atosorigin.com wrote: > Full_Name: Emmanuel Duru > Version: 2.3.38 > OS: Windows > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (195.68.44.148) > > > configure allows the use of "cp" instead of "ln", but the build/shtool tool uses > a hardcoded "ln" (line 1266). > Some makefiles (libraries/liblunicode, libraries/libldap_r and > servers/slapd/back-hdb) use a hardcoded "-s" option. This is a problem on > Windows because in cygwin environment "cp -s" behaves the same way as "ln -s". > The use of "ln" is not welcome here because it creates a Windows shortcut, which > is not understood by mingw compiler. We only support the MSYS build environment on Windows. If you'd like to submit a patch to address this issue that doesn't break the other platforms, we can look at incorporating it. -- -- 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