michael(a)stroeder.com wrote:
> I can't see it with RE24 (at the moment 2.4.10).
> Which version are you looking at?
>
> On my system slapo-accesslog is built and actively used.
> BTW: Other schema elements of slapo-accesslog are not available either:
> object class auditModify, attribute type reqAuthzID etc.
HEAD. I checked the code to see if the HIDE flag was being set, and I
didn't notice it was (it's being added right before registering the
schema item, rather than when defining it, that's why I overlooked it).
Of course you can't see it with 2.4. I think its publication as
non-experimental is pending Howard's completion of the related I.D.
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: ando(a)sys-net.it
-----------------------------------
Pierangelo Masarati wrote:
> michael(a)stroeder.com wrote:
>> Full_Name: Michael Ströder
>> Version: RE24
>> OS: OpenSUSE Linux 10.2
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (84.163.82.89)
>>
>>
>> Please add attribute type 'auditContext' to subschema.
>
> It is registered by slapo-accesslog(5). I can see it when
> slapo-accesslog(5) is built.
I can't see it with RE24 (at the moment 2.4.10).
Which version are you looking at?
On my system slapo-accesslog is built and actively used.
BTW: Other schema elements of slapo-accesslog are not available either:
object class auditModify, attribute type reqAuthzID etc.
Ciao, Michael.
vorlon(a)debian.org wrote:
> So meta_back_db_config() seems to be getting called before
> meta_back_db_open() ?
This is now fixed in HEAD; however, despite solving the sigsegv issue,
the test still fails because ldap_first_message(3) is not available.
This sounds odd, can anyone explain why it is not getting loaded?
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: ando(a)sys-net.it
-----------------------------------
vorlon(a)debian.org wrote:
> So meta_back_db_config() seems to be getting called before
> meta_back_db_open() ?
... which is correct. A fix is coming.
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: ando(a)sys-net.it
-----------------------------------
On Sun, Jun 29, 2008 at 11:29:58PM -0700, Steve Langasek wrote:
> Are you seeing this as well, or is this somehow specific to Debian? (It
> doesn't seem like it should be related to libltdl in any way, and we don't
> have any other patches that touch the meta backend; and I saw this segfault
> both with the version of the patch I sent, and the one extracted from CVS.)
> Unfortunately, running these tests under gdb seems to be pretty awkward. :/
Well, here's the backtrace:
0x00007f9d6a45ef60 in meta_back_db_config (be=0xa7bbb0,
fname=0x9f1040 "/home/devel/openldap/build-area/openldap2.3-2.4.10/debian/build/tests/testrun/slapd.3.conf", lineno=65, argc=6, argv=0xa3d230)
at /home/devel/openldap/build-area/openldap2.3-2.4.10/servers/slapd/back-meta/config.c:1162
1162 return mi->mi_ldap_extra->idassert_parse_cf( fname, lineno, argc, argv, &mi->mi_targets[ mi->mi_ntargets - 1 ]->mt_idassert );
#0 0x00007f9d6a45ef60 in meta_back_db_config (be=0xa7bbb0,
fname=0x9f1040 "/home/devel/openldap/build-area/openldap2.3-2.4.10/debian/build/tests/testrun/slapd.3.conf", lineno=65, argc=6, argv=0xa3d230)
at /home/devel/openldap/build-area/openldap2.3-2.4.10/servers/slapd/back-meta/config.c:1162
#1 0x000000000042ab13 in read_config_file (fname=<value optimized out>,
depth=<value optimized out>, cf=0x0, cft=0x71e0e0)
at /home/devel/openldap/build-area/openldap2.3-2.4.10/servers/slapd/config.c:786
#2 0x000000000042692d in read_config (
fname=0x9f1040 "/home/devel/openldap/build-area/openldap2.3-2.4.10/debian/build/tests/testrun/slapd.3.conf", dir=0x0)
at /home/devel/openldap/build-area/openldap2.3-2.4.10/servers/slapd/bconfig.c:3461
#3 0x0000000000419f3b in main (argc=8, argv=0x7fff77dc3e88)
at /home/devel/openldap/build-area/openldap2.3-2.4.10/servers/slapd/main.c:754
$1 = (ldap_extra_t *) 0x0
So meta_back_db_config() seems to be getting called before
meta_back_db_open() ?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek(a)ubuntu.com vorlon(a)debian.org
vorlon(a)debian.org wrote:
> On Sun, Jun 29, 2008 at 05:23:57PM -0700, Howard Chu wrote:
>> Steve Langasek wrote:
>>> Is the correct fix to add
>>> this function to the ldap_extra_t struct, as in the attached patch?
>
>> Pretty much. There are a few other functions that need to be added as
>> well. All of them are provided in current CVS HEAD, just grab the
>> relevant changes from there.
>
> Ok. With the patch from CVS HEAD applied, I'm seeing a segfault in make
> test (specifically, the meta backend test):
>
> >>>>> Starting test035-meta ...
> running defines.sh
>
> Starting slapd on TCP/IP port 9011...
> Using ldapsearch to check that slapd is running...
> Using ldapadd to populate the database...
> Starting slapd on TCP/IP port 9012...
> Using ldapsearch to check that slapd is running...
> Using ldapadd to populate the database...
> Starting slapd on TCP/IP port 9013...
> /home/devel/openldap/build-area/openldap2.3-2.4.10/tests/scripts/test035-meta: line 118: 22990 Segmentation fault $SLAPD -f $CONF3 -h $URI3 -d $LVL /$TIMING > $LOG3 2>&1
I'm not seeing anything like that, but I don't build back-meta as a
module. It would be helpful if you provide at least a stack backtrace
for that sigsegv, to help understand where and why it occurred.
> Are you seeing this as well, or is this somehow specific to Debian? (It
> doesn't seem like it should be related to libltdl in any way, and we don't
> have any other patches that touch the meta backend; and I saw this segfault
> both with the version of the patch I sent, and the one extracted from CVS.)
> Unfortunately, running these tests under gdb seems to be pretty awkward. :/
One thing that is still missing from that test is that if you build
back-ldap as a module, you need to load it before opening a back-meta
database, in order load the requested symbols. I'm fixing this right now.
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: ando(a)sys-net.it
-----------------------------------
On Sun, Jun 29, 2008 at 05:23:57PM -0700, Howard Chu wrote:
> Steve Langasek wrote:
>> Is the correct fix to add
>> this function to the ldap_extra_t struct, as in the attached patch?
> Pretty much. There are a few other functions that need to be added as
> well. All of them are provided in current CVS HEAD, just grab the
> relevant changes from there.
Ok. With the patch from CVS HEAD applied, I'm seeing a segfault in make
test (specifically, the meta backend test):
>>>>> Starting test035-meta ...
running defines.sh
Starting slapd on TCP/IP port 9011...
Using ldapsearch to check that slapd is running...
Using ldapadd to populate the database...
Starting slapd on TCP/IP port 9012...
Using ldapsearch to check that slapd is running...
Using ldapadd to populate the database...
Starting slapd on TCP/IP port 9013...
/home/devel/openldap/build-area/openldap2.3-2.4.10/tests/scripts/test035-meta: line 118: 22990 Segmentation fault $SLAPD -f $CONF3 -h $URI3 -d $LVL /$TIMING > $LOG3 2>&1
Are you seeing this as well, or is this somehow specific to Debian? (It
doesn't seem like it should be related to libltdl in any way, and we don't
have any other patches that touch the meta backend; and I saw this segfault
both with the version of the patch I sent, and the one extracted from CVS.)
Unfortunately, running these tests under gdb seems to be pretty awkward. :/
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek(a)ubuntu.com vorlon(a)debian.org
--=-GddVbqVLc61XV3X/kWQ/
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
I've uploaded the patch to http://abartlet.net/memberof.patch
--=20
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc.
--=-GddVbqVLc61XV3X/kWQ/
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQBIaD8sz4A8Wyi0NrsRAjTZAJ4mQaT1xP5zbZG4Db0UM1BbzfmDYACePtXf
MCnHmzCUac6KL/WbRX7aSxE=
=2c9m
-----END PGP SIGNATURE-----
--=-GddVbqVLc61XV3X/kWQ/--
--=-AN4G/3lLejTAf6KGBTk7
Content-Type: multipart/mixed; boundary="=-NvwPd4A703Oz/HjyG5IJ"
--=-NvwPd4A703Oz/HjyG5IJ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
I think I've figured out the right way to fix this, handling modify with
0 replacement elements just like a delete.
See attached.=20
--=20
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Red Hat Inc.
--=-NvwPd4A703Oz/HjyG5IJ
Content-Disposition: attachment; filename=memberof.patch
Content-Type: text/x-patch; name=memberof.patch; charset=UTF-8
Content-Transfer-Encoding: base64
SW5kZXg6IHNlcnZlcnMvc2xhcGQvb3ZlcmxheXMvbWVtYmVyb2YuYw0KPT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNT
IGZpbGU6IC9yZXBvL09wZW5MREFQL3BrZy9sZGFwL3NlcnZlcnMvc2xhcGQvb3ZlcmxheXMvbWVt
YmVyb2YuYyx2DQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMTkNCmRpZmYgLXUgLXIxLjE5IG1lbWJl
cm9mLmMNCi0tLSBzZXJ2ZXJzL3NsYXBkL292ZXJsYXlzL21lbWJlcm9mLmMJMTEgSmFuIDIwMDgg
MDU6MDc6NDMgLTAwMDAJMS4xOQ0KKysrIHNlcnZlcnMvc2xhcGQvb3ZlcmxheXMvbWVtYmVyb2Yu
YwkzMCBKdW4gMjAwOCAwMToyODoxMiAtMDAwMA0KQEAgLTg0MywxMSArODQzLDE3IEBADQogCQkJ
CQlicmVhazsNCiAJCQ0KIAkJCQljYXNlIExEQVBfTU9EX1JFUExBQ0U6DQorCQkJCQkvKiBIYW5k
bGUgdGhpcyBqdXN0IGxpa2UgYSBkZWxldGUgKHNlZSBhYm92ZSkgKi8NCisJCQkJCWlmICggbWwt
PnNtbF9udmFsdWVzID09IE5VTEwgKSB7DQorCQkJCQkJbWxwID0gJm1sLT5zbWxfbmV4dDsNCisJ
CQkJCQlicmVhazsNCisJCQkJCX0NCisNCiAJCQkJY2FzZSBMREFQX01PRF9BREQ6DQogCQkJCQkv
KiBOT1RFOiByaWdodCBub3csIHRoZSBhdHRyaWJ1dGVUeXBlIHdlIHVzZQ0KIAkJCQkJICogZm9y
IG1lbWJlciBtdXN0IGhhdmUgYSBub3JtYWxpemVkIHZhbHVlICovDQogCQkJCQlhc3NlcnQoIG1s
LT5zbWxfbnZhbHVlcyAhPSBOVUxMICk7DQotCQkNCisNCiAJCQkJCWZvciAoIGkgPSAwOyAhQkVS
X0JWSVNOVUxMKCAmbWwtPnNtbF9udmFsdWVzWyBpIF0gKTsgaSsrICkgew0KIAkJCQkJCWludAkJ
cmM7DQogCQkJCQkJRW50cnkJCSplOw0KQEAgLTEzNjIsNyArMTM2OCw3IEBADQogCQkJCQliZXJf
YnZhcnJheV9mcmVlX3goIHZhbHMsIG9wLT5vX3RtcG1lbWN0eCApOw0KIAkJCQl9DQogCQ0KLQkJ
CQlpZiAoIG1sLT5zbWxfb3AgPT0gTERBUF9NT0RfREVMRVRFICkgew0KKwkJCQlpZiAoIG1sLT5z
bWxfb3AgPT0gTERBUF9NT0RfREVMRVRFIHx8IG1sLT5zbWxfbnZhbHVlcyA9PSBOVUxMKSB7DQog
CQkJCQlicmVhazsNCiAJCQkJfQ0KIAkJCQkvKiBmYWxsIHRocnUgKi8NCg==
--=-NvwPd4A703Oz/HjyG5IJ--
--=-AN4G/3lLejTAf6KGBTk7
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQBIaDb3z4A8Wyi0NrsRAqd2AJ9pvfUj4jqL8HyFCfMh3zE47IfNwwCfTXOo
/lvXcMQzo0XgFPVqe8W/h1c=
=ssFN
-----END PGP SIGNATURE-----
--=-AN4G/3lLejTAf6KGBTk7--
Full_Name: Andrew Bartlett
Version: CVS HEAD
OS: Fedora 9
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (59.167.251.137)
The memberOf plugin asserts if I attempt a modify like:
(snippet from our python test script, using ldb, but I hope you get the idea)
ldb.modify_ldif("""
dn: cn=ldaptestgroup2,cn=users,""" + self.base_dn + """
changetype: modify
replace: member
""")
slapd: memberof.c:849: memberof_op_modify: Assertion `ml->sml_mod.sm_nvalues !=
((void *)0)' failed.
I think this just needs to be handled like the delete case, which our tests
already show pass correctly.