openldap-bugs

openldap-bugs@openldap.org

1 participants
20960 discussions

Re: OpenLdap ERROR: passwd: Authentication token manipulation error (ITS#5125)
by ando＠sys-net.it 07 Sep '07

07 Sep '07

diabeticithink(a)yahoo.com wrote: > Thank you for the help. I cannot upgrade to a later version of OpenLdap > because RHEL 4.0 doesn't support it. Bummer, eh? Well, there is nothing the OpenLDAP project can do for you, then, other than providing more than 3 years of development since 2.2.13 (it was released June 2004), that RedHat in the first place, but basically you seem to be willing to ignore (it's just one click away: untar, configure, make, make install). Or, you should ask RedHat to either upgrade OpenLDAP in RHEL 4.0, or fix your specific bug, if any (I still suspect a misconfiguration, possibly unrelated to OpenLDAP software itself, given that OpenLDAP software does not generate that specific message). As distributors, they are responsible for providing you up-to-date software when available (how responsive they are might depend on the type of maintenance contract you have with them). 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: OpenLdap ERROR: passwd: Authentication token manipulation error (ITS#5125)
by diabeticithink＠yahoo.com 07 Sep '07

07 Sep '07

Thank you for the help. I cannot upgrade to a later version of OpenLdap because RHEL 4.0 doesn't support it. Bummer, eh? -----Original Message----- From: Pierangelo Masarati [mailto:openldap-its@OpenLDAP.org] Sent: Friday, September 07, 2007 2:18 AM To: diabeticithink(a)yahoo.com Cc: openldap-its(a)OpenLDAP.org Subject: Re: OpenLdap ERROR: passwd: Authentication token manipulation error (ITS#5125) OpenLDAP 2.2.13 is obsolete. Support has been dropped ages ago and even in the case a problem is solved, no new release can occur in that branch. The current release is 2.3.38, so please upgrade and check if the problem persists. In any case, although the error message may appear scaring, there is no indication of a software error, so please direct further discussion to the openldap-software mailing list. This ITS is to track OpenLDAP software bugs, so please don't use it until there's evidence of a software bug. This ITS will be closed. p.

1 0

RE: OpenLdap ERROR: passwd: Authentication token manipulation error (ITS#5125)
by diabeticithink＠yahoo.com 07 Sep '07

07 Sep '07

Yes, it's the OpenLdap software that created this. As soon as I disable the Openldap, the users can change their password without a problem. Any idea on how to fix this? -----Original Message----- From: Kurt Zeilenga [mailto:openldap-its@OpenLDAP.org] Sent: Friday, September 07, 2007 4:10 AM To: diabeticithink(a)yahoo.com Subject: Re: OpenLdap ERROR: passwd: Authentication token manipulation error (ITS#5125) Actually, discussion of this error message should be directed to a mailing list about the LDAP client software, or other software, that actually produced the message. That message doesn't appear to be generated by any OpenLDAP Software.

1 0

Re: (ITS#5113) pcache returns incomplete results
by rhafer＠suse.de 07 Sep '07

07 Sep '07

On Donnerstag, 6. September 2007, ando(a)sys-net.it wrote: > rhafer(a)suse.de wrote: > > Hm, current HEAD first calls add_query, which adds the CachedQuery to the > > cache and after that calls cache_entries to add the entries of that Query > > to the cache. That means that query_containment already know about the > > Query before its result is completely cached. > > In RE23 it is just the other way arround (first cache_entries() then > > add_query()). > > I see two possible solution: > > > > 1. Switch back to the old behaviour. But I guess the change was made for > > a reason. I don't know that yet. Seems the change happend between r1.95 > > and r1.96 of pcache.c (log message: "Fix concurrency issues"). > > > > 2. Protect the cached query with an rw_lock. Writelock it while > > cache_entries() is executing and readlock it during searches. This would > > give us the behaviour that Ando suggested in the discussion of ITS#5112. > > (pcache would not try to cache the same search request mulitple times, > > but block the second request until the first one is cached and then > > answer it from the cache) > > +1 (if there's no drawback, of course) The only drawback (if it really is a drawback) is that subsequent clients will have to wait for the caching to be completed. Depending on the query that is being cached can take pretty long. On the other hand one can also view this as an advantage, as it save some network traffic between the proxy that the backend-server. :) -- Ralf

1 0

(ITS#5126) Auto-generation of devel/admin on website
by ghenry＠OpenLDAP.org 07 Sep '07

07 Sep '07

Full_Name: Gavin Henry Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry Dear all, I would like http://www.openldap.org/devel/admin/ to be automatically generated once a week. Daily is too often and might catch a broken make or similar. We can discuss the best time of day to run the job. Thanks, Gavin.

1 0

Re: (ITS#5124) segfault on modify operation by slurpd with rwm overlay
by ando＠sys-net.it 07 Sep '07

07 Sep '07

ando(a)sys-net.it wrote: > I'll check > if this could also happen with syncrepl, and try to figure out a > workaround. This is now fixed in HEAD and in re23. Please test. Thanks, 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#5124) segfault on modify operation by slurpd with rwm overlay
by ando＠sys-net.it 07 Sep '07

07 Sep '07

jclarke(a)linagora.com wrote: > We are using 2.3.37 for both master and slave, and have confirmed that > disactivating the rwm overlay in slapd.conf avoids the problem. The failure is related to the fact that you rewrite the bindDN; this tricks slapo-rwm(5) into failing to recognize that the operation is actually an update, resulting in a double free at cleanup. I'll check if this could also happen with syncrepl, and try to figure out a workaround. In the meanwhile you should be able to solve the problem by reworking the bindDN rewrite rules so that the updatedn is not rewritten. 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#5124) segfault on modify operation by slurpd with rwm overlay
by ando＠sys-net.it 07 Sep '07

07 Sep '07

jclarke(a)linagora.com wrote: > With a simple master/slave setup, and the rwm overlay activated for the bindDN > context, any modify operation made on the master, replicated with slurpd causes > the slave to crash. > > You will find below a backtrace of the slave when it crashes, and the > configuration files we're using on the master, the slave, an LDIF of the > contents of the directory are in the archive on ftp.openldap.org indicated in > the ITS. > > We are using 2.3.37 for both master and slave, and have confirmed that > disactivating the rwm overlay in slapd.conf avoids the problem. I'll try to look at your report, but let me note that slurpd is deprecated; since you're running OpenLDAP 2.3.37, you're strongly recommended to use syncrepl. 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#5113) pcache returns incomplete results
by ando＠sys-net.it 06 Sep '07

06 Sep '07

rhafer(a)suse.de wrote: > Hm, current HEAD first calls add_query, which adds the CachedQuery to the > cache and after that calls cache_entries to add the entries of that Query to > the cache. That means that query_containment already know about the Query > before its result is completely cached. > In RE23 it is just the other way arround (first cache_entries() then > add_query()). > I see two possible solution: > > 1. Switch back to the old behaviour. But I guess the change was made for a > reason. I don't know that yet. Seems the change happend between r1.95 and > r1.96 of pcache.c (log message: "Fix concurrency issues"). > > 2. Protect the cached query with an rw_lock. Writelock it while > cache_entries() is executing and readlock it during searches. This would give > us the behaviour that Ando suggested in the discussion of ITS#5112. (pcache > would not try to cache the same search request mulitple times, but block the > second request until the first one is cached and then answer it from the > cache) +1 (if there's no drawback, of course) 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#5113) pcache returns incomplete results
by rhafer＠suse.de 06 Sep '07

06 Sep '07

On Mittwoch, 29. August 2007, Howard Chu wrote: > rhafer(a)suse.de wrote: > > Full_Name: Ralf Haferkamp > > Version: HEAD > > OS: > > URL: ftp://ftp.openldap.org/incoming/ > > Submission from: (NULL) (89.166.180.39) > > > > > > While the results of a query are being cached, slapo-pcache will answer > > queries that match the same template from the cache that is currently > > being populated. This means that subsequent queries will get incomplete > > results until the original query is completely cached. > > I don't see how that is possible. The query-in-progress isn't added to the > cache until the final result is received. Until then, query_containment > should not know anything is there to answer with. Hm, current HEAD first calls add_query, which adds the CachedQuery to the cache and after that calls cache_entries to add the entries of that Query to the cache. That means that query_containment already know about the Query before its result is completely cached. In RE23 it is just the other way arround (first cache_entries() then add_query()). I see two possible solution: 1. Switch back to the old behaviour. But I guess the change was made for a reason. I don't know that yet. Seems the change happend between r1.95 and r1.96 of pcache.c (log message: "Fix concurrency issues"). 2. Protect the cached query with an rw_lock. Writelock it while cache_entries() is executing and readlock it during searches. This would give us the behaviour that Ando suggested in the discussion of ITS#5112. (pcache would not try to cache the same search request mulitple times, but block the second request until the first one is cached and then answer it from the cache) -- Ralf

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