- openldap-bugs - openldap.org

(ITS#5326) Add could re-build entry's DN using parent's DN and entry's RDN
by ando＠sys-net.it 13 Jan '08

13 Jan '08

Full_Name: Pierangelo Masarati Version: irrelevant OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.72.89.40) Submitted by: ando I think it is reasonable to reconstruct an entry's DN by using the parent's DN and the entry's RDN. The rationale consists in ensuring the tree naming is as uniform as possible. p.

1 0

Re: (ITS#5312) ldapmodify(1) man page claims that "changetype:" not necessary
by h.b.furuseth＠usit.uio.no 13 Jan '08

13 Jan '08

Howard Chu writes: > The outcome of the original discussion, which Kurt again reminded me > of today, was that ldapmodify should quit its guessing games and just > accept valid LDIF input. All I see in the -devel discussion is about bugs in the parser. I see nothing about removing the default "add:"/"replace:" derived from "changetype:", though perhaps it's in the off-list discussion it refers to. > The description of the exceptions in the manpage seemed imply they > were there to accommodate slurpd users, who needed a mechanism for > applying failed updates to a target server. Now that all slurpd/replog > support has been dropped, there really is no more justification for > these exceptions. That's not my impression, nor my recollection of the -r option. The manpage lists some differences from ldif format - replog, and defaulting changetype, add/replace. But they do not seem related. Not in the old code either; removing replog code can be done cleanly and does not interfere with those defaults. BTW I was wrong about when -r was removed. Seems to have been in the middle of the 2.0 branch; I only checked the beginning. ldapmodify rev 1.97, May 2 2001 "Clean up some logic, based upon Novell patches". I see a small patch from Novell shortly before that, ITS#1075, about a bug in the -r option. The "patches" referred to means more I've missed, I guess. >> As far as I can tell Logschema doesn't support full LDIF modify though. >> reqMod is unordered, so one cannot make two modifications to the same >> attribute. E.g. "delete: foo" followed by "replace: foo". > > I suppose reqMod should be made ordered. My point about logschema is that > reqMod's syntax doesn't require separators/terminators or as many redundant > attribute references. > > attr:- foo > attr:+ bar > > is a far more efficient representation than > > delete: attr > attr: foo > - > add: attr > attr: bar > - Which is why I want the old 'replace:' default back... With a doc warning that one must use the verbose LDIF format if one wants to not worry about attribute names like "increment" or "changetype". > The logschema format is also easily grep-able without resorting to grep > windowing and other such hassles. And that was roughly the old ldapmodify format. See manpage umich ldap-3.3/doc/man/man1/ldapmodify.1. I wonder why we removed it. There are a few weird LDAP change requests that do not map to that format, e.g. add: cn cn: foo - add: cn cn: bar - but that could have been fixed simply by allowing a '-' line as in the current format. >> Maybe it's time to take this to the ldapext list and hear what others >> do. > > This is really getting off topic, unless you're suggesting that we > spec this for a new version of LDIF. Not really, more the opposite - if we just relax some restrictions on the old format ldapmodify accepted before, that's fine. But otherwise, if we end up inventing a new way to parse ldifs rather than just accepting more of what the code accepted before, I think it'd be best to see what others do first. And if so we might as well go further. I don't suggest that as part of resolving this ITS, certainly. -- Regards, Hallvard

1 0

Re: (ITS#5325) Build error: __lock_getlocker undefined symbol
by h.b.furuseth＠usit.uio.no 13 Jan '08

13 Jan '08

ando(a)sys-net.it writes: > (...) There are tons of (sysadmin side) ways to make > sure the right library is loaded, so I vote against supporting this > feature. Of course, I'm fine about documenting that --with-uniquename > is not supported. configure should in any case check for __lock_getlocker(), since it's not a documented Berkeley DB function. Note that their headers do not declare it, OpenLDAP back-bdb.h does. -- Regards, Hallvard

1 0

Re: (ITS#5325) Build error: __lock_getlocker undefined symbol
by ando＠sys-net.it 12 Jan '08

12 Jan '08

tim(a)bishnet.net wrote: > For reference, it's because my libdb is built using --with-uniquename. > This means the function name is actually __lock_getlocker_4006. > > I didn't see this in the documentation. OpenLDAP should either correctly > handle this case, or document that it's not supported. I think using that option is a Bad Idea (TM); it is the Wrong Solution to the problem of having multiple coexisting versions of a library. In any case, adding support for that feature would be problematic and definitely prone to user (and developer) errors, since the value used to make names unique is not exposed in any header file, so it would have to be manually defined. There are tons of (sysadmin side) ways to make sure the right library is loaded, so I vote against supporting this feature. Of course, I'm fine about documenting that --with-uniquename is not supported. 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#5325) Build error: __lock_getlocker undefined symbol
by tim＠bishnet.net 11 Jan '08

11 Jan '08

On Fri, Jan 11, 2008 at 12:30:42PM -0800, Howard Chu wrote: > tim(a)bishnet.net wrote: > >Full_Name: Tim Bishop > >Version: 2.4.7 > >OS: Solaris 9 > >URL: > >Submission from: (NULL) (129.12.3.176) > > > > > >I'm having trouble building 2.4.7 against bdb 4.6.21. The build error is: > > > >Undefined first referenced > > symbol in file > >__lock_getlocker libbackends.a(bdbinit.o) > >ld: fatal: Symbol referencing errors. No output written to .libs/slapd > >collect2: ld returned 1 exit status > >make[2]: *** [slapd] Error 1 > > > >Is bdb 4.6.21 supported? > > Yes. > > It looks like either you're linking against the wrong version of libdb, or > something is odd in the way your libdb was built. There's no OpenLDAP > software bug here, this ITS will be closed. Use the -software mailing list > for questions about working with the source. For reference, it's because my libdb is built using --with-uniquename. This means the function name is actually __lock_getlocker_4006. I didn't see this in the documentation. OpenLDAP should either correctly handle this case, or document that it's not supported. Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984

1 0

Re: (ITS#5325) Build error: __lock_getlocker undefined symbol
by hyc＠symas.com 11 Jan '08

11 Jan '08

tim(a)bishnet.net wrote: > Full_Name: Tim Bishop > Version: 2.4.7 > OS: Solaris 9 > URL: > Submission from: (NULL) (129.12.3.176) > > > I'm having trouble building 2.4.7 against bdb 4.6.21. The build error is: > > Undefined first referenced > symbol in file > __lock_getlocker libbackends.a(bdbinit.o) > ld: fatal: Symbol referencing errors. No output written to .libs/slapd > collect2: ld returned 1 exit status > make[2]: *** [slapd] Error 1 > > Is bdb 4.6.21 supported? Yes. > > Is there a configure option to force a particular version of bdb? Read the INSTALL document. It looks like either you're linking against the wrong version of libdb, or something is odd in the way your libdb was built. There's no OpenLDAP software bug here, this ITS will be closed. Use the -software mailing list for questions about working with the source. -- -- 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#5308) test034-translucent crashes with back-ldif
by ando＠sys-net.it 11 Jan '08

11 Jan '08

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: HEAD > OS: Linux > URL: > Submission from: (NULL) (129.240.6.233) > Submitted by: hallvard > > > "./run -b ldif test034-translucent" crashes in str2entry2() at: > entry.c:298: if( ad_prev->ad_type->sat_equality && > because ad_prev == NULL - which got through due to this statement: > entry.c:278: if (( ad_prev && ad != ad_prev ) || ( i == lines )) { The real bug here is that the loop for attribute normalizations is run also in case there is no attrs. In fact, the same error shows up if you craft a shell backend (back-shell, back-perl) so that an LDIF only containing a DN is returned. It is now fixed in HEAD; please test. Please, also check and test for any side-effect introduced by the fix, as it impacts all calls to str2entry (many, I believe). 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

(ITS#5325) Build error: __lock_getlocker undefined symbol
by tim＠bishnet.net 11 Jan '08

11 Jan '08

Full_Name: Tim Bishop Version: 2.4.7 OS: Solaris 9 URL: Submission from: (NULL) (129.12.3.176) I'm having trouble building 2.4.7 against bdb 4.6.21. The build error is: Undefined first referenced symbol in file __lock_getlocker libbackends.a(bdbinit.o) ld: fatal: Symbol referencing errors. No output written to .libs/slapd collect2: ld returned 1 exit status make[2]: *** [slapd] Error 1 Is bdb 4.6.21 supported? Is there a configure option to force a particular version of bdb? Thanks, Tim.

1 0

Re: (ITS#5324) Access violation on Windows due to %n in format strings
by hyc＠symas.com 11 Jan '08

11 Jan '08

ghenry(a)suretecsystems.com wrote: > > In libraries/libldap/url.c, function ldap_url_desc2str, there are a > couple of >> sprintfs that use %n in their format strings to return position information. >> The latest Windows SDKs have heavily deprecated %n and its use now results in an >> unfortunate access violation and process crash. > > ldap_url_desc2str calls desc2str, which is where the sprintfs are. > > There's actually only one in an if/else in that function. > > This is the same for the latest 2.3 libldap and 2.4 libldap > > but this doesn't really answer your question. Already fixed in HEAD. -- -- 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#5324) Access violation on Windows due to %n in format strings
by ghenry＠suretecsystems.com 11 Jan '08

11 Jan '08

> In libraries/libldap/url.c, function ldap_url_desc2str, there are a couple of > sprintfs that use %n in their format strings to return position information. > The latest Windows SDKs have heavily deprecated %n and its use now results in an > unfortunate access violation and process crash. ldap_url_desc2str calls desc2str, which is where the sprintfs are. There's actually only one in an if/else in that function. This is the same for the latest 2.3 libldap and 2.4 libldap but this doesn't really answer your question. > > We've added a call to "_set_printf_count_output(1)" in libraries/libldap/init.c > function ldap_int_initialize() to re-enable %n so we're sufficiently worked > around for the moment. We're happy with our own workaround so we're not asking > for any kind of quick turnaround on this issue. If you want to fix this, please > do so in your own time and in your own way. You can consider this a courtesy > report only. > > If you decide not to fix this, please let me know because we'll need to add a > formal test case to our regression suites to make sure we don't resurrect the > issue when we upgrade our OpenLDAP clients. > > The msdn.microsoft.com website has the details of their proprietary function and > SDK versions where it's required in case you want to use our approach. I > included the URL so that you can get to it directly without going through MSDN's > searching. My own opinion is finding a way to do without the %n is probably > better and would result in fewer ifdefs in the code (always a plus in my book) > and less Microsoft specific code lurking around to bite us later. > > We did pull down 2.3.39 and our tech that looked at the code tells me the %n's > are still there and there's no _set_printf_count_output call so we think the > problem still exists in the latest version. Give me a virtual slap if I've got > this wrong. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by ghenry＠OpenLDAP.org 11 Jan '08

11 Jan '08

ghenry(a)suretecsystems.com wrote: > joshua(a)itsecureadmin.com wrote: >> Full_Name: Joshua Miller >> Version: 2.4.7 >> OS: CentOS 5 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (198.134.96.10) >> >> >> OL Version 2.4.7 >> Berkely DB 4.6 >> OS CentOS 5 >> >> Command: slapindex >> >> ISSUE: >> >> When attempting to generate cn=config from a configuration file using slapindex, >> no cn=config is generated: >> >> # cd /etc/openldap >> # mkdir slapd.d >> # /usr/sbin/slapindex -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d >> # echo $? >> 0 >> >> Program exits without error. >> >> # ls /etc/openldap/slapd.d >> >> Subsequently, running this command immediately after generates the appropriate >> cn=config: >> >> # slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d >> config file testing succeeded >> # ll slapd.d >> total 8 >> drwxr-x--- 4 root root 4096 Jan 10 13:07 cn=config >> -rw------- 1 root root 1097 Jan 10 13:07 cn=config.ldif >> # >> >> > > man slapindex does indeed so you can do this... > "does indeed say you can do this..." that should read. -- Kind Regards, Gavin Henry. OpenLDAP Engineering Team. E ghenry(a)OpenLDAP.org Community developed LDAP software. http://www.openldap.org/project/

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by ghenry＠suretecsystems.com 11 Jan '08

11 Jan '08

joshua(a)itsecureadmin.com wrote: > Full_Name: Joshua Miller > Version: 2.4.7 > OS: CentOS 5 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (198.134.96.10) > > > OL Version 2.4.7 > Berkely DB 4.6 > OS CentOS 5 > > Command: slapindex > > ISSUE: > > When attempting to generate cn=config from a configuration file using slapindex, > no cn=config is generated: > > # cd /etc/openldap > # mkdir slapd.d > # /usr/sbin/slapindex -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d > # echo $? > 0 > > Program exits without error. > > # ls /etc/openldap/slapd.d > > Subsequently, running this command immediately after generates the appropriate > cn=config: > > # slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d > config file testing succeeded > # ll slapd.d > total 8 > drwxr-x--- 4 root root 4096 Jan 10 13:07 cn=config > -rw------- 1 root root 1097 Jan 10 13:07 cn=config.ldif > # > > man slapindex does indeed so you can do this... -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

RE: (ITS#5320) bug on the filter functionnality =*
by jpgressard＠hotmail.com 11 Jan '08

11 Jan '08

--_5a7f2691-df18-4e09-b6ca-32d395149553_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Hallvard, I have followed the advices of Hallvard and it works. So after an upgrade to 2.4.7, you have to rebuild the indexes.1 - Stop the = slapd deamon2 - launch slapindex3 - relaunch the slapd deamon Thanks for your help. Jean-Paul> From: h.b.furuseth(a)usit.uio.no> To: jpgressard(a)hotmail.com> > jp= gressard(a)hotmail.com writes:> > The query (&(sn=3DXXXXXX*)(givenName=3D*))c= an not find the entry below.> > Does it help to stop slapd, run sbin/slapin= dex, and restart slapd?> You need to do that if you edit slapd.conf's index= statements,> and possibly when you upgrade.> > -- > Hallvard _________________________________________________________________ Nouveau ! Cr=E9ez votre profil Messenger ! http://home.services.spaces.live.com/= --_5a7f2691-df18-4e09-b6ca-32d395149553_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <style> .hmmessage P { margin:0px; padding:0px } body.hmmessage { FONT-SIZE: 10pt; FONT-FAMILY:Tahoma } </style> </head> <body class=3D'hmmessage'> Hi Hallvard, I have followed the advices of Hallvard and it works. So after an upgrade to 2.4.7, you have to rebuild the indexes. 1 - Stop = the slapd deamon 2 - launch slapindex 3 - relaunch the slapd deamon<B= R> Thanks for your help. Jean-Paul > From: h.b.furuseth(a)usit.uio.no > To: jpgressard= @hotmail.com > > jpgressard(a)hotmail.com writes: > > T= he query (&(sn=3DXXXXXX*)(givenName=3D*))can not find the entry below.<= BR>> > Does it help to stop slapd, run sbin/slapindex, and restar= t slapd? > You need to do that if you edit slapd.conf's index stateme= nts, > and possibly when you upgrade. > > -- > Ha= llvard <hr />Windows Live Messenger 2008 vient de sortir, enco= re plus de fun ! <a href=3D'http://www.windowslive.fr/majmessenger.asp' ta= rget=3D'_new'>T=E9l=E9chargez gratuitement Messenger 2008</a></body> </html>= --_5a7f2691-df18-4e09-b6ca-32d395149553_--

1 0

(ITS#5324) Access violation on Windows due to %n in format strings
by jeff.lewis＠teradata.com 10 Jan '08

10 Jan '08

Full_Name: Jeff Lewis Version: 2.3.20 OS: Microsoft Windows on IA64 URL: http://msdn2.microsoft.com/en-us/library/ms175782.aspx Submission from: (NULL) (192.127.94.7) We (Teradata, formerly NCR) have encountered a small glitch with the latest Windows SDK and OpenLDAP client tools. We're getting an access violation where we did not get one with the older SDK. Our IA64 builds require the newer SDK because of codegen issues with the older compilers...but soon, we're going to be moving to the newer SDK for i386 and x8664 so the problem will begin to crop up there as well. Here's the problem: In libraries/libldap/url.c, function ldap_url_desc2str, there are a couple of sprintfs that use %n in their format strings to return position information. The latest Windows SDKs have heavily deprecated %n and its use now results in an unfortunate access violation and process crash. We've added a call to "_set_printf_count_output(1)" in libraries/libldap/init.c function ldap_int_initialize() to re-enable %n so we're sufficiently worked around for the moment. We're happy with our own workaround so we're not asking for any kind of quick turnaround on this issue. If you want to fix this, please do so in your own time and in your own way. You can consider this a courtesy report only. If you decide not to fix this, please let me know because we'll need to add a formal test case to our regression suites to make sure we don't resurrect the issue when we upgrade our OpenLDAP clients. The msdn.microsoft.com website has the details of their proprietary function and SDK versions where it's required in case you want to use our approach. I included the URL so that you can get to it directly without going through MSDN's searching. My own opinion is finding a way to do without the %n is probably better and would result in fewer ifdefs in the code (always a plus in my book) and less Microsoft specific code lurking around to bite us later. We did pull down 2.3.39 and our tech that looked at the code tells me the %n's are still there and there's no _set_printf_count_output call so we think the problem still exists in the latest version. Give me a virtual slap if I've got this wrong. If you decide to fix this, I'm at your disposal and can provide some testing support since IA64 platforms are pretty rare. If you want to get in touch with me and my email address doesn't work (we're in a spin-off transition right now so our infrastructure isn't as stable as it should be), you can reach me by phone at 310-616-2384.

1 0

Re: (ITS#5323) dyngroup.c:dgroup_cf() bug
by hyc＠symas.com 10 Jan '08

10 Jan '08

h.b.furuseth(a)usit.uio.no wrote: > I wrote: >> To avoid that, start the code with something like >> ap = on->on_bi.bi_private; >> app = ≈ > > Duh.. ignore that one. > Probably should ignore all of this. dynlist totally supersedes dyngroup now. -- -- 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#5323) dyngroup.c:dgroup_cf() bug
by h.b.furuseth＠usit.uio.no 10 Jan '08

10 Jan '08

I wrote: > To avoid that, start the code with something like > ap = on->on_bi.bi_private; > app = ≈ Duh.. ignore that one. -- Hallvard

1 0

(ITS#5323) dyngroup.c:dgroup_cf() bug
by h.b.furuseth＠usit.uio.no 10 Jan '08

10 Jan '08

Full_Name: Hallvard B Furuseth Version: HEAD, RE24 OS: URL: Submission from: (NULL) (129.240.6.233) Submitted by: hallvard overlays/dyngroup.c:dgroup_cf() has some strange LDAP_MOD_DELETE code: app = (adpair **)&on->on_bi.bi_private; for (...; ...; ..., app = &ap->ap_next) { ap = *app; } *app = ap->ap_next; Last statement is a no-op, since *app == *(&ap->ap_next) == ap->ap_next. I'm not sure what it's intended to do. Also the first statement makes the void* object bi_private be accessed as an adpair* object. Breaks the 'strict aliasing' rules, so I guess it can miscompile. To avoid that, start the code with something like ap = on->on_bi.bi_private; app = ≈

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by hyc＠symas.com 10 Jan '08

10 Jan '08

joshua(a)itsecureadmin.com wrote: > Quanah Gibson-Mount wrote: >> --On Thursday, January 10, 2008 9:09 PM +0000 joshua(a)itsecureadmin.com >>> Full_Name: Joshua Miller >>> Version: 2.4.7 >>> OS: CentOS 5 >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (198.134.96.10) >> What makes you think you should be using slapindex to do this? > > > The admin guide suggests that any slap* command should do this: > > http://www.openldap.org/doc/admin24/slapdconf2.html#cn=config > > > Also, the slapd-config man page: > > Alternatively, an existing slapd.conf file can be converted to > the new format using slapd or any of the slap tools: > slaptest -f /etc/openldap/slapd.conf -F ETCDIR/slapd.d The docs are incomplete. slapd or slaptest will always work; the other tools (slapadd/slapcat/slapindex) don't actually invoke the config database's startup routine unless you're explicitly operating on the config backend therefore the conversion won't occur in general. -- -- 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#5322) slaptest exits on seg fault (SIGSEGV) if id2entry.bdb does not exist
by joshua＠itsecureadmin.com 10 Jan '08

10 Jan '08

Full_Name: Joshua Miller Version: 2.4.7 OS: CentOS 5 URL: http://ditree.com/work/gdb.ol2.4.7.out Submission from: (NULL) (198.134.96.10) When issuing slaptest prior to executing slapd to generate an id2entry.bdb file, slaptest/slapindex exits with a segmentation fault (SIGSEGV). Use case: user installs OpenLDAP, generates a configuration file, slapd.conf. User decides to generate cn=config prior to running slapd. User receives seg fault through running slaptest to perform this operation. Steps to reproduce: * install openldap 2.4.7, using berkley db 4.6 * create suitable slapd.conf * attempt to validate the configuration file using the following command: slaptest -f slapd.conf Expected results: Success Actual results: Segmentation Fault (SIGSEGV). Possibly useless gdb output located at: http://ditree.com/work/gdb.ol2.4.7.out

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by joshua＠itsecureadmin.com 10 Jan '08

10 Jan '08

Quanah Gibson-Mount wrote: > --On Thursday, January 10, 2008 9:09 PM +0000 joshua(a)itsecureadmin.com >> Full_Name: Joshua Miller >> Version: 2.4.7 >> OS: CentOS 5 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (198.134.96.10) > > What makes you think you should be using slapindex to do this? The admin guide suggests that any slap* command should do this: http://www.openldap.org/doc/admin24/slapdconf2.html#cn=config Also, the slapd-config man page: Alternatively, an existing slapd.conf file can be converted to the new format using slapd or any of the slap tools: slaptest -f /etc/openldap/slapd.conf -F ETCDIR/slapd.d Thanks, -- Joshua M. Miller - RHCE,VCP

1 0

Re: (ITS#5321) slapindex fails to create cn=config from configuration file
by quanah＠zimbra.com 10 Jan '08

10 Jan '08

--On Thursday, January 10, 2008 9:09 PM +0000 joshua(a)itsecureadmin.com wrote: > Full_Name: Joshua Miller > Version: 2.4.7 > OS: CentOS 5 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (198.134.96.10) > > > OL Version 2.4.7 > Berkely DB 4.6 > OS CentOS 5 > > Command: slapindex What makes you think you should be using slapindex to do this? --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5321) slapindex fails to create cn=config from configuration file
by joshua＠itsecureadmin.com 10 Jan '08

10 Jan '08

Full_Name: Joshua Miller Version: 2.4.7 OS: CentOS 5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (198.134.96.10) OL Version 2.4.7 Berkely DB 4.6 OS CentOS 5 Command: slapindex ISSUE: When attempting to generate cn=config from a configuration file using slapindex, no cn=config is generated: # cd /etc/openldap # mkdir slapd.d # /usr/sbin/slapindex -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d # echo $? 0 Program exits without error. # ls /etc/openldap/slapd.d Subsequently, running this command immediately after generates the appropriate cn=config: # slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d config file testing succeeded # ll slapd.d total 8 drwxr-x--- 4 root root 4096 Jan 10 13:07 cn=config -rw------- 1 root root 1097 Jan 10 13:07 cn=config.ldif #

1 0

Re: (ITS#5320) bug on the filter functionnality =*
by quanah＠zimbra.com 10 Jan '08

10 Jan '08

--On Thursday, January 10, 2008 3:31 PM +0000 jpgressard(a)hotmail.com wrote: > I tested the same query on the version 2.4.6 and it was working. > Furthermore, if I amend the query to (&(sn=XXX*)(givenName=D*)), or > (sn=XXX*) I find the entry. As noted when 2.4.7 was released, you want to regenerate your indices. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5320) bug on the filter functionnality =*
by h.b.furuseth＠usit.uio.no 10 Jan '08

10 Jan '08

jpgressard(a)hotmail.com writes: > The query (&(sn=XXXXXX*)(givenName=*))can not find the entry below. Does it help to stop slapd, run sbin/slapindex, and restart slapd? You need to do that if you edit slapd.conf's index statements, and possibly when you upgrade. -- Hallvard

1 0

(ITS#5320) bug on the filter functionnality =*
by jpgressard＠hotmail.com 10 Jan '08

10 Jan '08

Full_Name: Jean-Paul Gressard Version: 2.4.7 OS: Madrake distribution (v10) URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (158.232.2.8) The query (&(sn=XXXXXX*)(givenName=*))can not find the entry below. dn: uid=XXXXXXDDDDD14977,l=Geneva,c=CH,o=who,o=directoryroot sn: XXXXXX objectClass: inetOrgPerson uid: XXXXXXDDDDD14977 telephoneNumber: 14977 o: who givenName: DDDDD cn: XXXXXX, DDDDD I tested the same query on the version 2.4.6 and it was working. Furthermore, if I amend the query to (&(sn=XXX*)(givenName=D*)), or (sn=XXX*) I find the entry.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs