(ITS#5797) build failed
by cycwj＠163.com
Full_Name: bluewind
Version: 2.4.12
OS: ubunt server 8
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (219.133.134.8)
try to build on ubutnu server 8, use install manaul from www.openldap.org
#./configure (ok)
#make depen (ok)
#make (ok)
but,when execution
#make test
the system stop on "Running slapadd to build slapd database...", no any
response
after about 1 hour
14 years, 10 months
Re: (ITS#5773) bi_entry_get_rw() and overlays issue
by hyc＠symas.com
ando(a)sys-net.it wrote:
> h.b.furuseth(a)usit.uio.no wrote:
>> ando(a)sys-net.it writes:
>>> I think bi_entry_get_rw() needs work.
>> Or maybe phase it out in favor of some other call?
>>
>>> In fact, as also discussed in ITS#5628, callers either return the
>>> entry or have no means to modify the arguments of the request.
>> It has more troubles than that. See e.g. the notes about passing rw=1
>> (write) to it here:
>> http://www.openldap.org/lists/openldap-devel/200803/msg00055.html
>> And there is no equivalent of the REP_ENTRY_MUSTRELEASE flag which
>> says to pass an rw=1 argument to bi_entry_release_rw().
>
> Well, I see many places where an entry needs to be fetched. Typically,
> it needs to be done read-only.
In fact, the rw flag makes no sense. You can only fetch an entry ro; if you
actually fetched it for write access and modified the entry, there's no API to
commit the changed entry to stable storage. You would only be making a
transient change to a cached copy (which could disappear as soon as you
release the entry). So if we're going to change this API, the first thing to
do is get rid of the rw flag. You must use be_modify if you want to change
anything about an entry...
> So the difference between
> bi_entry_get_ro() and an internal search is that if we are fine with the
> entry in-cache, we save lots of manipulation. However this might no
> longer suffice when overlays muck with the entry (like slapo-rwm).
> Moreover, when overlays are present, I see the need to:
> 1) run it like it came from outside, going thru all the overlays
That's what overlays currently do when they do the bd_info swap and then call
be_entry_get_rw().
> 2) go straight to the underlying database
That's done by calling bd_info->bi_entry_get_rw()...
> 3) go thru overlays starting at some point (e.g. when called from inside
> an overlay under the assumption the entry is fetched as that overlay
> would see it, so with only any possible mucking from overlays layered
> deeper than the caller).
That's what overlay_entry_get_ov() does. Also note that passing a NULL
overinst here accomplishes (2).
> This probably needs to modify the way
> callbacks are actually called, allowing some "after self" feature in
> playing not just the overlay list, but also the response (and the cleanup).
Then we need an "opcode" for this, so that response / cleanup handlers know
why they're being invoked.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
14 years, 10 months
(ITS#5796) back-sql intermittently failing
by robb＠wtg.cw.com
Full_Name: Robert Brooks
Version: 2
OS: 2.4.12
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (62.49.19.14)
Set up is a pair of centos 4 hosts, one acts as primary, the other is a syncrepl
consumer and mysql slave. Apart from syncrepl config/myqsl slave all config and
software versions are the same. Mysql queries on both hosts are to localhost via
socket.
After a period of operation (24-48 hours) the slave host drops the back-sql part
of directory for some queries (same query will suceed some times). Using strace
it can been seen that the ldap searches are not resulting in queries to mysql.
Back-sql is a subordinate db and results from hdb backed part of directory are
returned.
Restarting slapd fixes the problem, but start-up reports the shutdown was
unclean on hdb db. Operation of primary is reliable.
14 years, 10 months
Re: (ITS#5640) slapd scans too many objects at startup
by hyc＠symas.com
ali.pouya(a)free.fr wrote:
> Howard Chu wrote :
>
>> I see.
>>
>> This has been fixed for back-bdb/hdb in HEAD. If the database was shut down
>> cleanly before, there will be no scan on the next startup.
>
> Hi Howard,
> Thanks for the corrections.
> We tested the HEAD extracted on monday november 3. Unfortunately the problem
> explained in point 2 persists (even after a clean shutdown).
> Our directory contains 10 million entries. It can evolve to 40 million entries
> next year.
> The local sacanning speed is around 250 000 entries per minute.
> So the scan of the recent objects on the standby mirror after startup can take
> several minutes (unless if we distribute the write operations on both mirrors).
I don't see this happening on my builds. Maybe you should post your configs
and a sample of the data and modifications used to illustrate the problem.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
14 years, 10 months
Re: (ITS#5794) Password exop unwilling to verify old password
by hyc＠symas.com
aja(a)nlgroup.ca wrote:
> Full_Name: Arthur Anhalt
> Version: 2.4.12
> OS: Ubuntu 8.04
> URL:
> Submission from: (NULL) (205.200.169.138)
>
>
> When parsing password change extended operations,
> servers/slapd/passwd.c:slap_passwd_parse() calls ber_get_stringbv() with
> LBER_BV_NOTERM set. The resulting bv_val doesn't end with a \0.
>
> In libraries/liblutil/passwd.c:chk_crypt will return an error is the old and
> new
> passwords do not end with a null terminator. I believe more of the chk_*
> functions
> return the same error.
>
> This is the same bug as ITS#5575, but affects the core system, not contributed
> code.
Fixed in HEAD, thanks.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
14 years, 10 months
Re: (ITS#5783) Possible DB corruption
by moya＠latertulia.org
El jue, 06-11-2008 a las 07:30 -0800, Howard Chu escribió:
> moya(a)latertulia.org wrote:
> > Full_Name: Maykel Moya
> > Version: 2.4.11
> > OS: Debian Lenny
> > URL: ftp://ftp.openldap.org/incoming/
> > Submission from: (NULL) (200.55.135.211)
> >
> >
> > It's second time that I have bitten by this:
> >
> > Oct 31 07:49:24 swage slapd[4308]: PROXIED attributeDescription "DC" inserted.
> >
> > After that I'm unable to bind against the DSA. The problem has arise in two
> > independent systems.
>
> This is now fixed in HEAD.
Oh, thanks. Is there a way I can get the patch for applying it to my
system?
Regards,
maykel
14 years, 10 months
Re: (ITS#5795) Modification of cn=config prevents to bind at next directory restart
by hyc＠symas.com
hyc(a)symas.com wrote:
> emmanuel.duru(a)atosorigin.com wrote:
>> Full_Name: Emmanuel Duru
>> Version: 2.4.11
>> OS: Windows
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (80.78.0.137)
>>
>>
>> I have set a rootdn on cn=config which is a real entry
>> (cn=admin,ou=somewhere,o=myorg,c=fr).
>> I bind with this DN.
>> I perform a change on cn=config (change the log level).
>> At next slapd startup, I get:
>> PROXIED attributeDescription "OU" inserted.
>> PROXIED attributeDescription "O" inserted.
>> PROXIED attributeDescription "C" inserted.
>> and then when trying to bind, I get an invalid credentials error (49).
>> The problem seems to come from modifiersname in cn=config entry, because if I
>> delete this attribute and restarts slapd, all is fine.
>
> Ah, thanks for this. You're seeing the same as #5783, but you've provided much
> more useful information here.
>
Now fixed in HEAD.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
14 years, 10 months
