(ITS#5090) Error with attribute "jpegPhoto"
by nicolas.sandraz＠gmail.com
Full_Name: Sandraz Nicolas
Version: 2.3.30
OS: Linux (debian Etch)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (81.252.72.177)
when i use a LDIF file with the falowing attribute jpegPhoto associate with the
object class inetOrgPerson i have this error:
slapadd : /tmp/build/openldap2.3-2.3.30/servers/slapd/schema_check.c:87 :
entry_schema_check: Assertion `a->a_vals[0].bv_val != ((void *)0)' failed.
i use this line (on my ldif file) to add a picture on my LDAP directory:
jpegPhoto: < file///etc/ldap/pictures/test.jpg
note: when i remove this line from my ldif file i can import all information!
15 years, 9 months
(ITS#5089) test043-delta-syncrepl: test failed - producer and consumer databases differ
by michael＠stroeder.com
Full_Name: Michael Ströder
Version: HEAD
OS: openSUSE 10.2
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (83.124.34.52)
Running ./scripts/test043-delta-syncrepl...
running defines.sh
Starting producer slapd on TCP/IP port 9011...
Using ldapsearch to check that producer slapd is running...
Using ldapadd to create the context prefix entries in the producer...
Starting consumer slapd on TCP/IP port 9012...
Using ldapsearch to check that consumer slapd is running...
Waiting 5 seconds for slapd to start...
Using ldapadd to populate the producer directory...
Waiting 15 seconds for syncrepl to receive changes...
Stopping the provider, sleeping 10 seconds and restarting it...
Using ldapsearch to check that producer slapd is running...
Using ldapmodify to modify producer directory...
Waiting 15 seconds for syncrepl to receive changes...
Stopping consumer to test recovery...
Modifying more entries on the producer...
Restarting consumer...
Waiting 25 seconds for syncrepl to receive changes...
Try updating the consumer slapd...
Waiting 15 seconds for syncrepl to receive changes...
Using ldapsearch to read all the entries from the producer...
Using ldapsearch to read all the entries from the consumer...
Filtering producer results...
Filtering consumer results...
Comparing retrieved entries from producer and consumer...
test failed - producer and consumer databases differ
15 years, 9 months
Re: (ITS#5051) Translucent overlay and back-monitor
by ghenry＠suretecsystems.com
<quote who="Pierangelo Masarati">
> Gavin Henry wrote:
>
>> OK, thanks. Do you have any reference for custom monitoring examples?
>
> Not sure what you mean. By "custom monitoring" I mean that pieces of
> code may register callbacks in back-monitor to enrich the monitor
> entries with dynamically generated data. Right now, the only code that
> exploits this functionality is back-bdb/back-hdb, but it's something we
> use intensively for custom modules we develop (the monitor database can
> be proficiently used as an interface for non-persistent interaction with
> the DSA).
Ah, right. Sorry, I misunderstood custom as something done via
configuration in the front end, not via callbacks.
>
> With reference to code, see servers/slapd/back-bdb/monitor.c (the API is
> implemented in servers/slapd-back-monitor/init.c).
Will do, sounds very useful indeed.
>
> What back-bdb/hdb publishes by means of this API is not documented,
> AFAIK; it might be worth mentioning somewhere in the docs, as this
> monitoring could be quite useful for tuning. Nothing that cannot be
> accessed thru db_stat, the advantage is access via LDAP protocol.
Exactly, sounds very useful and one that I can investigate and document in
the Monitoring section, with implementation examples (not code) in the
Tuning and Maintenance sections of our guide.
>
> A recent addition was the capability to monitor what unindexed
> attributes were used in searches.
Yeah, I commented on that previously. Nice.
Gavin.
>
> 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
> ---------------------------------------
>
>
>
15 years, 9 months
Re: (ITS#5051) Translucent overlay and back-monitor
by ando＠sys-net.it
Gavin Henry wrote:
> OK, thanks. Do you have any reference for custom monitoring examples?
Not sure what you mean. By "custom monitoring" I mean that pieces of
code may register callbacks in back-monitor to enrich the monitor
entries with dynamically generated data. Right now, the only code that
exploits this functionality is back-bdb/back-hdb, but it's something we
use intensively for custom modules we develop (the monitor database can
be proficiently used as an interface for non-persistent interaction with
the DSA).
With reference to code, see servers/slapd/back-bdb/monitor.c (the API is
implemented in servers/slapd-back-monitor/init.c).
What back-bdb/hdb publishes by means of this API is not documented,
AFAIK; it might be worth mentioning somewhere in the docs, as this
monitoring could be quite useful for tuning. Nothing that cannot be
accessed thru db_stat, the advantage is access via LDAP protocol.
A recent addition was the capability to monitor what unindexed
attributes were used in searches.
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
---------------------------------------
15 years, 9 months
Re: (ITS#5051) Translucent overlay and back-monitor
by ghenry＠suretecsystems.com
<quote who="ando(a)sys-net.it">
> ghenry(a)suretecsystems.com wrote:
>
>> Ok. What can the rootdn do on the monitor database then? Write to
>> anything?
>> I can update the "Monitoring" section with this info then ;-)
>
> As usual, the privilege of the rootdn consists in bypassing ACLs. In
> this case, you just need the rootdn, it doesn't need to be able to bind
> (i.e. no rootpw and no fancy SASL rules to map someone with that
> identity), since it will only be used for internal purposes, namely to
> look up where bdb custom monitoring will be placed.
OK, thanks. Do you have any reference for custom monitoring examples?
Gavin.
>
> 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
> ---------------------------------------
>
>
>
>
15 years, 9 months
ITS#4211
by ando＠sys-net.it
Quanah,
for which is which, HEAD now has back-config support for both slapo-rwm
and slapd-relay. You may resume your configuration replication
experiments...
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
---------------------------------------
15 years, 9 months
Re: (ITS#5051) Translucent overlay and back-monitor
by ando＠sys-net.it
ghenry(a)suretecsystems.com wrote:
> Ok. What can the rootdn do on the monitor database then? Write to anything?
> I can update the "Monitoring" section with this info then ;-)
As usual, the privilege of the rootdn consists in bypassing ACLs. In
this case, you just need the rootdn, it doesn't need to be able to bind
(i.e. no rootpw and no fancy SASL rules to map someone with that
identity), since it will only be used for internal purposes, namely to
look up where bdb custom monitoring will be placed.
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
---------------------------------------
15 years, 9 months
(ITS#5088) ObjectClass inheritance check in back-sql
by ando＠sys-net.it
Full_Name: Pierangelo Masarati
Version: HEAD/re23
OS: irrelevant
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (82.63.140.131)
Submitted by: ando
When extra objectClasses for an entry are listed in table ldap_entry_objclasses,
if any of them is structural and derived from the objectClass used to map the
RDBMS data to LDAP, the entry is now rejected because the computed objectClass
does not match the objectClass used to map data, although the entry would be
perfectly valid from an LDAP standpoint.
This is now fixed in HEAD/re23.
p.
15 years, 9 months
(ITS#5087) slapacl is broken for back-hdb
by hyc＠OpenLDAP.org
Full_Name: Howard Chu
Version: 2.3/HEAD
OS:
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (76.168.84.21)
Submitted by: hyc
The tool_id2entry_get function neglects the fix_dn step for hdb, so every
retrieved entry has a zero-length DN. A patch to HEAD is coming.
Really there should never have been such a function, tool_entry_get should have
been used for this purpose.
15 years, 9 months
Re: (ITS#5077) syncrepl.add_cmp() infinite loop on swapped values
by donn＠u.washington.edu
On Aug 10, 2007, at 2:16 PM, Howard Chu wrote:
> donn(a)u.washington.edu wrote:
>> Full_Name: Donn Cave
>> Version: 2.4.4
>> OS: Red Hat Linux
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (128.95.135.150)
>> In "while" loop at 2656, I find old->a_vals are like [..., a,
>> b, ...] and
>> new->a_vals are like [..., b, a, ...].
>> Matches are found at old [i] == new [k = j+1] and old [k = i+1] ==
>> new [j], but
>> this just shows that neither an add nor a delete is called for,
>> and the loop end
>> is reached without having incremented i or j.
>> Actual attribute values I'm looking at right now in the debugger are
>> eduPersonAffiliation: old [ member, alum, employee, faculty ],
>> new [ member,
>> alum, faculty, employee ]. I built the replica from a slapcat
>> dump on the idle
>> master, started the slapd syncrepl client and applied a lot of normal
>> modifications to the master, until it hit the infinite loop. It
>> has been a
>> recurrent problem.
>
> Now fixed in HEAD, please test.
Aug 10 15:06:55 rufus03 slapd[31488]: null_callback : error code 0x14
Aug 10 15:06:55 rufus03 slapd[31488]: syncrepl_entry: rid=101
be_modify (20)
Aug 10 15:06:55 rufus03 slapd[31488]: syncrepl_entry: rid=101
be_modify failed (20)
I could put some more research into this, but tell me if this
doesn't make sense. Suppose this mysteriously swapped order:
a,b,...
b,a,...
Your fix increments the first list's index, so next iteration it's
b,...
b,a,...
which is fine, but next iteration is
...
a,...
"a" looks new at this point, and I try to add it, but it isn't new -
we just forgot that it was in "old" - and I get error 0x14
(LDAP_TYPE_OR_VALUES_EXISTS)
Donn Cave, donn(a)u.washington.edu
15 years, 9 months
