- openldap-bugs - openldap.org

Re: (ITS#7568) [Patch] Minor documentation fixes
by hyc＠symas.com 10 Apr '13

10 Apr '13

jsynacek(a)redhat.com wrote: > Full_Name: Jan Synacek > Version: master > OS: Linux - Fedora 18 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (209.132.186.34) > > > I'm attaching two patches that fix minor documentation issues in ldap.conf.5 and > slaptest's usage output. Thanks, added to master. > http://jsynacek.fedorapeople.org/openldap/jsynacek-20130409-0001-Fix-typos-… > http://jsynacek.fedorapeople.org/openldap/jsynacek-20130409-0002-Add-Q-to-s… Personally I don't see much point to -Q here; the purpose of slaptest is to tell you what errors are there. With -Q you get no useful information when an error occurs. Judging from the fact that no one has noticed this omission in the 6 years since -Q was added, I don't believe this particular feature has been of any importance one way or the other. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#7569) Patch: fixed a group enumeration bug in nssov
by tedcheng＠symas.com 10 Apr '13

10 Apr '13

Full_Name: Ted C. Cheng Version: HEAD OS: Solaris 8, 10, Linux URL: https://dl.dropbox.com/u/94235048/symas2255.patch Submission from: (NULL) (76.174.250.179) Importing a patch from Symas #2255 that fixed a group enumeration bug in nssov. The "rc" variable was not initialized in nssov write_group function. Theoretically, this bug should affect all platforms. Solaris 8 (64-bit) caught the bug because rc got a non-zero value when not initialized.

1 0

Re: (ITS#7565) unacceptable growth on delete with back-mdb
by quanah＠zimbra.com 10 Apr '13

10 Apr '13

--On Friday, April 05, 2013 7:46 PM +0000 quanah(a)OpenLDAP.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.35 > OS: Linux 2.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.39.181) Fixed in current RE24. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7568) [Patch] Minor documentation fixes
by jsynacek＠redhat.com 09 Apr '13

09 Apr '13

Full_Name: Jan Synacek Version: master OS: Linux - Fedora 18 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (209.132.186.34) I'm attaching two patches that fix minor documentation issues in ldap.conf.5 and slaptest's usage output. http://jsynacek.fedorapeople.org/openldap/jsynacek-20130409-0001-Fix-typos-… http://jsynacek.fedorapeople.org/openldap/jsynacek-20130409-0002-Add-Q-to-s…

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by quanah＠zimbra.com 08 Apr '13

08 Apr '13

--On Monday, April 08, 2013 8:31 PM -0600 Leo Mocofan <lm5(a)ualberta.ca> wrote: > > > > > > > I noticed something similar on ubuntu10 as well. I upgraded my server to > ubuntu12, and I also set /proc/sys/vm/dirty_ratio to 90 and > /proc/sys/vm/dirty_expire_centisecs to 60000, and that helped > significantly > with back-mdb using current OpenLDAP master. An ldapadd of almost 3.5 > million users takes approximately 4 hours now for my dataset vs 16. so > 4x > faster. > > > > > Thank you for your suggestions. I tried these two settings and ldapadd > wrote 3 GB in 8 hours (out of 4.3 GB). How big is your database ? My DB is 5.6GB in size after load is complete. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by lm5＠ualberta.ca 08 Apr '13

08 Apr '13

--bcaec548a14bc68c7904d9e4584b Content-Type: text/plain; charset=ISO-8859-1 > > I noticed something similar on ubuntu10 as well. I upgraded my server to > ubuntu12, and I also set /proc/sys/vm/dirty_ratio to 90 and > /proc/sys/vm/dirty_expire_centisecs to 60000, and that helped significantly > with back-mdb using current OpenLDAP master. An ldapadd of almost 3.5 > million users takes approximately 4 hours now for my dataset vs 16. so 4x > faster. > Thank you for your suggestions. I tried these two settings and ldapadd wrote 3 GB in 8 hours (out of 4.3 GB). How big is your database ? Have you considered running the database from a ramdisk ? Using ramfs in Linux, I got the fastest times on all the tests I tried. Leo Mocofan --bcaec548a14bc68c7904d9e4584b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c= cc solid;padding-left:1ex"><div><div>I noticed something similar on ubuntu1= 0 as well. =A0I upgraded my server to<br> ubuntu12, and I also set /proc/sys/vm/dirty_ratio to 90 and<br> /proc/sys/vm/dirty_expire_centisecs to 60000, and that helped significantly= <br> with back-mdb using current OpenLDAP master. =A0An ldapadd of almost 3.5<br= > million users takes approximately 4 hours now for my dataset vs 16. =A0so 4= x<br> faster.<br></div></div></blockquote><div><br></div><div>Thank you for your = suggestions. I tried these two settings and ldapadd wrote 3 GB in 8 hours (= out of 4.3 GB). How big is your database ?<br><br></div><div>Have you consi= dered running the database from a ramdisk ? Using ramfs in Linux, I got the= fastest times on all the tests I tried.<br> <br></div><div>Leo Mocofan<br></div><div><br></div></div></div></div> --bcaec548a14bc68c7904d9e4584b--

1 0

(ITS#7564)
by tamas.kenez＠kishonti.net 08 Apr '13

08 Apr '13

--_000_06BD065177CD164EB234102C529395EF6483AF2AAMSPRD0311MB436_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Please cancel this issue. Reason: the mtest.c test program uses an experimental flag MDB_FIXEDMAP whi= ch causes the failure. Without the flag it works fine. --_000_06BD065177CD164EB234102C529395EF6483AF2AAMSPRD0311MB436_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"HU" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><span lang=3D"EN-US">Please cancel this issue.<o:p><= /o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p> </o:p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US">Reason: the mtest.c test progra= m uses an experimental flag MDB_FIXEDMAP which causes the failure.<o:p></o:= p></span></p> <p class=3D"MsoNormal"><span lang=3D"EN-US">Without the flag it works fine.= <o:p></o:p></span></p> </div> </body> </html> --_000_06BD065177CD164EB234102C529395EF6483AF2AAMSPRD0311MB436_--

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by quanah＠zimbra.com 07 Apr '13

07 Apr '13

--On Saturday, April 06, 2013 1:07 PM -0600 - lidutu <lm5(a)ualberta.ca> wrote: > > > > > > > > So what is happening on the slapd server while things are paused? > > Also, if you use an ldapi:/// socket rather than a tcp/ip socket, do you > see the same issue? > > > > > A have changed to use the ldapi:/// socket and there is no improvement. > > > It seems that one thread of slapd is repeatedly waiting on epoll_wait. > Strace prints > epoll_wait(6, > > and then pauses for couple of seconds. > > > > Iotop shows to slapd threads writing to disk. Right after I start > ldapadd, they write to disk at approximately 60MB/s each. Over time, they > go down to 2-3 MB/s each. > > TID PRIO USER DISK READ DISK WRITE > SWAPIN IO COMMAND > 15264 be/4 ldap 0.00 B/s 2.81 M/s 0.00 % 99.99 % > slapd -u ldap -g ldap -f /etc/openldap/slapd.conf -h > ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock > 15255 be/4 ldap 0.00 B/s 3.00 M/s 0.00 % 19.48 % > slapd -u ldap -g ldap -f /etc/openldap/slapd.conf -h > ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock I noticed something similar on ubuntu10 as well. I upgraded my server to ubuntu12, and I also set /proc/sys/vm/dirty_ratio to 90 and /proc/sys/vm/dirty_expire_centisecs to 60000, and that helped significantly with back-mdb using current OpenLDAP master. An ldapadd of almost 3.5 million users takes approximately 4 hours now for my dataset vs 16. so 4x faster. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7567) Alias dereferencing slowness
by luca.scamoni＠gruppopa.it 07 Apr '13

07 Apr '13

Full_Name: Luca Scamoni Version: 2.4.35 OS: Linux URL: ftp://www.sys-net.it/alias-deref-ITS2.tar.gz Submission from: (NULL) (78.134.117.13) Investigating alias dereferencing slowness on a customer production system I came upon a suspect behaviour with back-hdb/bdb. It seems that slapd, when dereferencing, instead of looking for the exact aliased DN, starts scanning more entries than needed (at least this is what I can tell looking to the logs set to log anything) On the customer system, with over 700,000 entries, the time taken to perform a simple search with alias dereferencing for a single entry, takes as much as performing a full ldapsearch of the entire ldap tree. To reproduce I created a small testcase (that I can't upload because there's no space left on ftp.openldap.org/incoming). The test case contains also the log and the operations performed on test data to show the issue. I tested with openldap 2.4.23, 2.4.31 and 2.4.35. The issue is present in all versions but seems to manifest itself only with back-bdb/hdb. Back-mdb seems not to show the issue (even looking at the logs) but right now, moving to back-mdb is not something the customer is ready to take. regards Luca

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by lm5＠ualberta.ca 06 Apr '13

06 Apr '13

--bcaec54eef8cfe673204d9b5eb1e Content-Type: text/plain; charset=ISO-8859-1 > So what is happening on the slapd server while things are paused? > > Also, if you use an ldapi:/// socket rather than a tcp/ip socket, do you > see the same issue? > A have changed to use the ldapi:/// socket and there is no improvement. It seems that one thread of slapd is repeatedly waiting on epoll_wait. Strace prints epoll_wait(6, and then pauses for couple of seconds. Iotop shows to slapd threads writing to disk. Right after I start ldapadd, they write to disk at approximately 60MB/s each. Over time, they go down to 2-3 MB/s each. TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND 15264 be/4 ldap 0.00 B/s 2.81 M/s 0.00 % 99.99 % slapd -u ldap -g ldap -f /etc/openldap/slapd.conf -h ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock 15255 be/4 ldap 0.00 B/s 3.00 M/s 0.00 % 19.48 % slapd -u ldap -g ldap -f /etc/openldap/slapd.conf -h ldapi://%2fvar%2frun%2fopenldap%2fslapd.sock I took an strace for all the process and threads involved over a 2 minute period. Process slapd - main thread: futex(0x7f2efa38e9d0, FUTEX_WAIT, 15251, NULL Process slapd - thread: % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 57.08 1.639877 474 3457 268 futex 42.54 1.222208 1076 1136 fdatasync 0.17 0.004913 0 272650 writev 0.11 0.003194 3 1137 pwrite 0.06 0.001736 0 272649 lseek 0.02 0.000530 0 4544 1136 read 0.01 0.000282 0 2273 write 0.00 0.000132 0 2273 sendto 0.00 0.000065 0 1136 open 0.00 0.000061 0 1136 stat 0.00 0.000041 0 1136 epoll_ctl 0.00 0.000011 0 1136 close 0.00 0.000000 0 116 mprotect 0.00 0.000000 0 2272 fcntl 0.00 0.000000 0 1136 getuid 0.00 0.000000 0 1136 getppid 0.00 0.000000 0 1136 gettid ------ ----------- ----------- --------- --------- ---------------- 100.00 2.873050 570459 1404 total Process slapd - thread: % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 50.67 1.128008 399 2828 213 futex 48.96 1.089974 1161 939 fdatasync 0.15 0.003311 0 226607 writev 0.13 0.002928 3 939 pwrite 0.07 0.001544 0 226607 lseek 0.01 0.000214 0 1879 write 0.01 0.000139 0 1879 sendto 0.00 0.000065 0 940 open 0.00 0.000046 0 3760 940 read 0.00 0.000029 0 94 mprotect 0.00 0.000021 0 940 close 0.00 0.000021 0 940 getppid 0.00 0.000019 0 940 getuid 0.00 0.000015 0 940 epoll_ctl 0.00 0.000014 0 940 stat 0.00 0.000000 0 1880 fcntl 0.00 0.000000 0 940 gettid ------ ----------- ----------- --------- --------- ---------------- 100.00 2.226348 473992 1153 total Process slapd - thread: % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- -nan 0.000000 0 1386 read -nan 0.000000 0 13861 sendto -nan 0.000000 0 3866 294 futex -nan 0.000000 0 2772 epoll_wait -nan 0.000000 0 1386 epoll_ctl ------ ----------- ----------- --------- --------- ---------------- 100.00 0.000000 23271 294 total Process ldapadd: % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 99.19 0.056533 18 3194 poll 0.48 0.000276 0 4866 read 0.32 0.000183 0 6846 write 0.00 0.000000 0 1 restart_syscall ------ ----------- ----------- --------- --------- ---------------- 100.00 0.056992 14907 total --bcaec54eef8cfe673204d9b5eb1e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: base64 PGRpdiBkaXI9Imx0ciI+PGJyPjxkaXYgY2xhc3M9ImdtYWlsX2V4dHJhIj48ZGl2IGNsYXNzPSJn bWFpbF9xdW90ZSI+PGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2lu OjBweCAwcHggMHB4IDAuOGV4O2JvcmRlci1sZWZ0OjFweCBzb2xpZCByZ2IoMjA0LDIwNCwyMDQp O3BhZGRpbmctbGVmdDoxZXgiPjxkaXYgY2xhc3M9ImltIj48L2Rpdj48ZGl2IGNsYXNzPSJpbSI+ DQoNClNvIHdoYXQgaXMgaGFwcGVuaW5nIG9uIHRoZSBzbGFwZCBzZXJ2ZXIgd2hpbGUgdGhpbmdz IGFyZSBwYXVzZWQ/PGJyPg0KPGJyPg0KQWxzbywgaWYgeW91IHVzZSBhbiBsZGFwaTovLy8gc29j a2V0IHJhdGhlciB0aGFuIGEgdGNwL2lwIHNvY2tldCwgZG8geW91IHNlZSB0aGUgc2FtZSBpc3N1 ZT88YnI+PC9kaXY+PC9ibG9ja3F1b3RlPjxkaXY+oDxicj48L2Rpdj48ZGl2PkEgaGF2ZSBjaGFu Z2VkIHRvIHVzZSB0aGUgbGRhcGk6Ly8vIHNvY2tldCBhbmQgdGhlcmUgaXMgbm8gaW1wcm92ZW1l bnQuPGJyPjxicj48L2Rpdj4NCjxkaXY+SXQgc2VlbXMgdGhhdCBvbmUgdGhyZWFkIG9mIHNsYXBk IGlzIHJlcGVhdGVkbHkgd2FpdGluZyBvbiBlcG9sbF93YWl0LiBTdHJhY2UgcHJpbnRzPGJyPmVw b2xsX3dhaXQoNiw8YnI+PC9kaXY+PGRpdj5hbmQgdGhlbiBwYXVzZXMgZm9yIGNvdXBsZSBvZiBz ZWNvbmRzLjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PklvdG9wIHNob3dzIHRvIHNsYXBk IHRocmVhZHMgd3JpdGluZyB0byBkaXNrLiBSaWdodCBhZnRlciBJIHN0YXJ0IGxkYXBhZGQsIHRo ZXkgd3JpdGUgdG8gZGlzayBhdCBhcHByb3hpbWF0ZWx5IDYwTUIvcyBlYWNoLiBPdmVyIHRpbWUs IHRoZXkgZ28gZG93biB0byAyLTMgTUIvcyBlYWNoLjxicj4NCjxicj5USUSgoKAgUFJJT6CgoCBV U0VSoKCgIERJU0sgUkVBRKCgoCBESVNLIFdSSVRFoKCgIFNXQVBJTqCgoCBJT6CgoCBDT01NQU5E PGJyPjE1MjY0IGJlLzQgbGRhcKCgoKCgoKAgMC4wMCBCL3OgoKAgMi44MSBNL3OgIDAuMDAgJSA5 OS45OSAlIHNsYXBkIC11IGxkYXAgLWcgbGRhcCAtZiAvZXRjL29wZW5sZGFwL3NsYXBkLmNvbmYg LWggbGRhcGk6Ly8lMmZ2YXIlMmZydW4lMmZvcGVubGRhcCUyZnNsYXBkLnNvY2s8YnI+DQoxNTI1 NSBiZS80IGxkYXCgoKCgoKCgIDAuMDAgQi9zoKCgIDMuMDAgTS9zoCAwLjAwICUgMTkuNDggJSBz bGFwZCAtdSBsZGFwIC1nIGxkYXAgLWYgL2V0Yy9vcGVubGRhcC9zbGFwZC5jb25mIC1oIGxkYXBp Oi8vJTJmdmFyJTJmcnVuJTJmb3BlbmxkYXAlMmZzbGFwZC5zb2NrPGJyPjxicj48L2Rpdj48ZGl2 PkkgdG9vayBhbiBzdHJhY2UgZm9yIGFsbCB0aGUgcHJvY2VzcyBhbmQgdGhyZWFkcyBpbnZvbHZl ZCBvdmVyIGEgMiBtaW51dGUgcGVyaW9kLjxicj4NCjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+ UHJvY2VzcyBzbGFwZCAtIG1haW4gdGhyZWFkOjxicj5mdXRleCgweDdmMmVmYTM4ZTlkMCwgRlVU RVhfV0FJVCwgMTUyNTEsIE5VTEw8YnI+PGJyPjwvZGl2PjxkaXY+UHJvY2VzcyBzbGFwZCAtIHRo cmVhZDo8YnI+JSB0aW1loKCgoCBzZWNvbmRzoCB1c2Vjcy9jYWxsoKCgoCBjYWxsc6CgoCBlcnJv cnMgc3lzY2FsbDxicj4tLS0tLS0gLS0tLS0tLS0tLS0gLS0tLS0tLS0tLS0gLS0tLS0tLS0tIC0t LS0tLS0tLSAtLS0tLS0tLS0tLS0tLS0tPGJyPg0KoDU3LjA4oKCgIDEuNjM5ODc3oKCgoKCgoKAg NDc0oKCgoKAgMzQ1N6CgoKCgoCAyNjggZnV0ZXg8YnI+oDQyLjU0oKCgIDEuMjIyMjA4oKCgoKCg oCAxMDc2oKCgoKAgMTEzNqCgoKCgoKCgoKAgZmRhdGFzeW5jPGJyPqAgMC4xN6CgoCAwLjAwNDkx M6CgoKCgoKCgoKAgMKCgoCAyNzI2NTCgoKCgoKCgoKCgIHdyaXRldjxicj6gIDAuMTGgoKAgMC4w MDMxOTSgoKCgoKCgoKCgIDOgoKCgoCAxMTM3oKCgoKCgoKCgoCBwd3JpdGU8YnI+DQqgIDAuMDag oKAgMC4wMDE3MzagoKCgoKCgoKCgIDCgoKAgMjcyNjQ5oKCgoKCgoKCgoCBsc2Vlazxicj6gIDAu MDKgoKAgMC4wMDA1MzCgoKCgoKCgoKCgIDCgoKCgoCA0NTQ0oKCgoKAgMTEzNiByZWFkPGJyPqAg MC4wMaCgoCAwLjAwMDI4MqCgoKCgoKCgoKAgMKCgoKCgIDIyNzOgoKCgoKCgoKCgIHdyaXRlPGJy PqAgMC4wMKCgoCAwLjAwMDEzMqCgoKCgoKCgoKAgMKCgoKCgIDIyNzOgoKCgoKCgoKCgIHNlbmR0 bzxicj4NCqAgMC4wMKCgoCAwLjAwMDA2NaCgoKCgoKCgoKAgMKCgoKCgIDExMzagoKCgoKCgoKCg IG9wZW48YnI+oCAwLjAwoKCgIDAuMDAwMDYxoKCgoKCgoKCgoCAwoKCgoKAgMTEzNqCgoKCgoKCg oKAgc3RhdDxicj6gIDAuMDCgoKAgMC4wMDAwNDGgoKCgoKCgoKCgIDCgoKCgoCAxMTM2oKCgoKCg oKCgoCBlcG9sbF9jdGw8YnI+oCAwLjAwoKCgIDAuMDAwMDExoKCgoKCgoKCgoCAwoKCgoKAgMTEz NqCgoKCgoKCgoKAgY2xvc2U8YnI+DQqgIDAuMDCgoKAgMC4wMDAwMDCgoKCgoKCgoKCgIDCgoKCg oKAgMTE2oKCgoKCgoKCgoCBtcHJvdGVjdDxicj6gIDAuMDCgoKAgMC4wMDAwMDCgoKCgoKCgoKCg IDCgoKCgoCAyMjcyoKCgoKCgoKCgoCBmY250bDxicj6gIDAuMDCgoKAgMC4wMDAwMDCgoKCgoKCg oKCgIDCgoKCgoCAxMTM2oKCgoKCgoKCgoCBnZXR1aWQ8YnI+oCAwLjAwoKCgIDAuMDAwMDAwoKCg oKCgoKCgoCAwoKCgoKAgMTEzNqCgoKCgoKCgoKAgZ2V0cHBpZDxicj4NCqAgMC4wMKCgoCAwLjAw MDAwMKCgoKCgoKCgoKAgMKCgoKCgIDExMzagoKCgoKCgoKCgIGdldHRpZDxicj4tLS0tLS0gLS0t LS0tLS0tLS0gLS0tLS0tLS0tLS0gLS0tLS0tLS0tIC0tLS0tLS0tLSAtLS0tLS0tLS0tLS0tLS0t PGJyPjEwMC4wMKCgoCAyLjg3MzA1MKCgoKCgoKCgoKCgoKCgoCA1NzA0NTmgoKCgoCAxNDA0IHRv dGFsPGJyPjxicj5Qcm9jZXNzIHNsYXBkIC0gdGhyZWFkOjxicj4NCiUgdGltZaCgoKAgc2Vjb25k c6AgdXNlY3MvY2FsbKCgoKAgY2FsbHOgoKAgZXJyb3JzIHN5c2NhbGw8YnI+LS0tLS0tIC0tLS0t LS0tLS0tIC0tLS0tLS0tLS0tIC0tLS0tLS0tLSAtLS0tLS0tLS0gLS0tLS0tLS0tLS0tLS0tLTxi cj6gNTAuNjegoKAgMS4xMjgwMDigoKCgoKCgoCAzOTmgoKCgoCAyODI4oKCgoKCgIDIxMyBmdXRl eDxicj6gNDguOTagoKAgMS4wODk5NzSgoKCgoKCgIDExNjGgoKCgoKAgOTM5oKCgoKCgoKCgoCBm ZGF0YXN5bmM8YnI+DQqgIDAuMTWgoKAgMC4wMDMzMTGgoKCgoKCgoKCgIDCgoKAgMjI2NjA3oKCg oKCgoKCgoCB3cml0ZXY8YnI+oCAwLjEzoKCgIDAuMDAyOTI4oKCgoKCgoKCgoCAzoKCgoKCgIDkz OaCgoKCgoKCgoKAgcHdyaXRlPGJyPqAgMC4wN6CgoCAwLjAwMTU0NKCgoKCgoKCgoKAgMKCgoCAy MjY2MDegoKCgoKCgoKCgIGxzZWVrPGJyPqAgMC4wMaCgoCAwLjAwMDIxNKCgoKCgoKCgoKAgMKCg oKCgIDE4NzmgoKCgoKCgoKCgIHdyaXRlPGJyPg0KoCAwLjAxoKCgIDAuMDAwMTM5oKCgoKCgoKCg oCAwoKCgoKAgMTg3OaCgoKCgoKCgoKAgc2VuZHRvPGJyPqAgMC4wMKCgoCAwLjAwMDA2NaCgoKCg oKCgoKAgMKCgoKCgoCA5NDCgoKCgoKCgoKCgIG9wZW48YnI+oCAwLjAwoKCgIDAuMDAwMDQ2oKCg oKCgoKCgoCAwoKCgoKAgMzc2MKCgoKCgoCA5NDAgcmVhZDxicj6gIDAuMDCgoKAgMC4wMDAwMjmg oKCgoKCgoKCgIDCgoKCgoKCgIDk0oKCgoKCgoKCgoCBtcHJvdGVjdDxicj4NCqAgMC4wMKCgoCAw LjAwMDAyMaCgoKCgoKCgoKAgMKCgoKCgoCA5NDCgoKCgoKCgoKCgIGNsb3NlPGJyPqAgMC4wMKCg oCAwLjAwMDAyMaCgoKCgoKCgoKAgMKCgoKCgoCA5NDCgoKCgoKCgoKCgIGdldHBwaWQ8YnI+oCAw LjAwoKCgIDAuMDAwMDE5oKCgoKCgoKCgoCAwoKCgoKCgIDk0MKCgoKCgoKCgoKAgZ2V0dWlkPGJy PqAgMC4wMKCgoCAwLjAwMDAxNaCgoKCgoKCgoKAgMKCgoKCgoCA5NDCgoKCgoKCgoKCgIGVwb2xs X2N0bDxicj4NCqAgMC4wMKCgoCAwLjAwMDAxNKCgoKCgoKCgoKAgMKCgoKCgoCA5NDCgoKCgoKCg oKCgIHN0YXQ8YnI+oCAwLjAwoKCgIDAuMDAwMDAwoKCgoKCgoKCgoCAwoKCgoKAgMTg4MKCgoKCg oKCgoKAgZmNudGw8YnI+oCAwLjAwoKCgIDAuMDAwMDAwoKCgoKCgoKCgoCAwoKCgoKCgIDk0MKCg oKCgoKCgoKAgZ2V0dGlkPGJyPi0tLS0tLSAtLS0tLS0tLS0tLSAtLS0tLS0tLS0tLSAtLS0tLS0t LS0gLS0tLS0tLS0tIC0tLS0tLS0tLS0tLS0tLS08YnI+DQoxMDAuMDCgoKAgMi4yMjYzNDigoKCg oKCgoKCgoKCgoKAgNDczOTkyoKCgoKAgMTE1MyB0b3RhbDxicj48YnI+PC9kaXY+PGRpdj5Qcm9j ZXNzIHNsYXBkIC0gdGhyZWFkOjxicj4lIHRpbWWgoKCgIHNlY29uZHOgIHVzZWNzL2NhbGygoKCg IGNhbGxzoKCgIGVycm9ycyBzeXNjYWxsPGJyPi0tLS0tLSAtLS0tLS0tLS0tLSAtLS0tLS0tLS0t LSAtLS0tLS0tLS0gLS0tLS0tLS0tIC0tLS0tLS0tLS0tLS0tLS08YnI+DQqgIC1uYW6goKAgMC4w MDAwMDCgoKCgoKCgoKCgIDCgoKCgoCAxMzg2oKCgoKCgoKCgoCByZWFkPGJyPqAgLW5hbqCgoCAw LjAwMDAwMKCgoKCgoKCgoKAgMKCgoKAgMTM4NjGgoKCgoKCgoKCgIHNlbmR0bzxicj6gIC1uYW6g oKAgMC4wMDAwMDCgoKCgoKCgoKCgIDCgoKCgoCAzODY2oKCgoKCgIDI5NCBmdXRleDxicj6gIC1u YW6goKAgMC4wMDAwMDCgoKCgoKCgoKCgIDCgoKCgoCAyNzcyoKCgoKCgoKCgoCBlcG9sbF93YWl0 PGJyPg0KoCAtbmFuoKCgIDAuMDAwMDAwoKCgoKCgoKCgoCAwoKCgoKAgMTM4NqCgoKCgoKCgoKAg ZXBvbGxfY3RsPGJyPi0tLS0tLSAtLS0tLS0tLS0tLSAtLS0tLS0tLS0tLSAtLS0tLS0tLS0gLS0t LS0tLS0tIC0tLS0tLS0tLS0tLS0tLS08YnI+MTAwLjAwoKCgIDAuMDAwMDAwoKCgoKCgoKCgoKCg oKCgoCAyMzI3MaCgoKCgoCAyOTQgdG90YWw8YnI+PGJyPlByb2Nlc3MgbGRhcGFkZDo8YnI+JSB0 aW1loKCgoCBzZWNvbmRzoCB1c2Vjcy9jYWxsoKCgoCBjYWxsc6CgoCBlcnJvcnMgc3lzY2FsbDxi cj4NCi0tLS0tLSAtLS0tLS0tLS0tLSAtLS0tLS0tLS0tLSAtLS0tLS0tLS0gLS0tLS0tLS0tIC0t LS0tLS0tLS0tLS0tLS08YnI+oDk5LjE5oKCgIDAuMDU2NTMzoKCgoKCgoKCgIDE4oKCgoKAgMzE5 NKCgoKCgoKCgoKAgcG9sbDxicj6gIDAuNDigoKAgMC4wMDAyNzagoKCgoKCgoKCgIDCgoKCgoCA0 ODY2oKCgoKCgoKCgoCByZWFkPGJyPqAgMC4zMqCgoCAwLjAwMDE4M6CgoKCgoKCgoKAgMKCgoKCg IDY4NDagoKCgoKCgoKCgIHdyaXRlPGJyPg0KoCAwLjAwoKCgIDAuMDAwMDAwoKCgoKCgoKCgoCAw oKCgoKCgoKAgMaCgoKCgoKCgoKAgcmVzdGFydF9zeXNjYWxsPGJyPi0tLS0tLSAtLS0tLS0tLS0t LSAtLS0tLS0tLS0tLSAtLS0tLS0tLS0gLS0tLS0tLS0tIC0tLS0tLS0tLS0tLS0tLS08YnI+MTAw LjAwoKCgIDAuMDU2OTkyoKCgoKCgoKCgoKCgoKCgoCAxNDkwN6CgoKCgoKCgoKAgdG90YWw8YnI+ PC9kaXY+PC9kaXY+PC9kaXY+PC9kaXY+DQo= --bcaec54eef8cfe673204d9b5eb1e--

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by quanah＠zimbra.com 05 Apr '13

05 Apr '13

--On Friday, April 05, 2013 8:52 PM -0600 - lidutu <lm5(a)ualberta.ca> wrote: > > > > Hi Quanah, > > I have started doing tests with Gentoo Linux running openldap 2.4.35, > glibc 2.16 and linux kernel 3.4, 3.8 and 3.9-rc5. I have tried ext2, > ext4, reiserfs and jfs. Ldapadd is still very slow compared to BSD > regardless of the openldap backend. > > > Also a correction to the initial report: using a memory based file > system, ldapadd the whole database took 22 min. So what is happening on the slapd server while things are paused? Also, if you use an ldapi:/// socket rather than a tcp/ip socket, do you see the same issue? --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by lm5＠ualberta.ca 05 Apr '13

05 Apr '13

--047d7b414c2ebdcec404d9a84c9d Content-Type: text/plain; charset=ISO-8859-1 Hi Quanah, I have started doing tests with Gentoo Linux running openldap 2.4.35, glibc 2.16 and linux kernel 3.4, 3.8 and 3.9-rc5. I have tried ext2, ext4, reiserfs and jfs. Ldapadd is still very slow compared to BSD regardless of the openldap backend. Also a correction to the initial report: using a memory based file system, ldapadd the whole database took 22 min. Leo On Fri, Apr 5, 2013 at 5:48 PM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Friday, April 05, 2013 11:46 PM +0000 quanah(a)zimbra.com wrote: > > --On Friday, April 05, 2013 11:36 PM +0000 lm5(a)ualberta.ca wrote: >> >> Full_Name: Leo Mocofan >>> Version: 2.4.31 >>> OS: Debian Testing >>> URL: ftp://ftp.openldap.org/**incoming/<ftp://ftp.openldap.org/incoming/> >>> Submission from: (NULL) (129.128.11.107) >>> >> >> If you are going to test back-mdb, then you need to use a current >> OpenLDAP release (2.4.35). >> >> In any case, I don't see a bug report here? It sounds more like you're >> asking for tuning advice? I would ask what filesystem you are using >> (ext2? ext4?) etc. For ext4, I had to modify dirty_bytes to keep the >> Debian/Ubuntu flush process from killing load performance. >> > > Oh, one other note -- I advise avoiding the debian/ubuntu build versions > of BDB, if that is what you are using. They do not build BDB with the > correct configure options, seriously impacting performance. > > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > > --047d7b414c2ebdcec404d9a84c9d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><div>Hi Quanah,<br><br></div>I have started doing tes= ts with Gentoo Linux running openldap 2.4.35, glibc 2.16 and linux kernel 3= .4, 3.8 and 3.9-rc5. I have tried ext2, ext4, reiserfs and jfs. Ldapadd is = still very slow compared to BSD regardless of the openldap backend. <br> <br></div><div>Also a correction to the initial report: using a memory base= d file system, ldapadd the whole database took 22 min.<br></div><div><br></= div>Leo<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo= te"> On Fri, Apr 5, 2013 at 5:48 PM, Quanah Gibson-Mount <span dir=3D"ltr"><<= a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</a>= ></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0= 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class=3D"im">--On Friday, April 05, 2013 11:46 PM +0000 <a href=3D"mai= lto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</a> wrote:<br> <br> </div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0= 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> --On Friday, April 05, 2013 11:36 PM +0000 <a href=3D"mailto:lm5@ualberta.c= a" target=3D"_blank">lm5(a)ualberta.ca</a> wrote:<br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Full_Name: Leo Mocofan<br> Version: 2.4.31<br> OS: Debian Testing<br> URL: <a href=3D"ftp://ftp.openldap.org/incoming/" target=3D"_blank">ftp://f= tp.openldap.org/<u></u>incoming/</a><br> Submission from: (NULL) (129.128.11.107)<br> </blockquote> <br> If you are going to test back-mdb, then you need to use a current<br> OpenLDAP =A0release (2.4.35).<br> <br> In any case, I don't see a bug report here? =A0It sounds more like you&= #39;re<br> asking for tuning advice? =A0I would ask what filesystem you are using<br> (ext2? =A0ext4?) etc. =A0For ext4, I had to modify dirty_bytes to keep the<= br> Debian/Ubuntu flush process from killing load performance.<br> </blockquote> <br></div> Oh, one other note -- I advise avoiding the debian/ubuntu build versions of= BDB, if that is what you are using. =A0They do not build BDB with the corr= ect configure options, seriously impacting performance.<div class=3D"HOEnZb= "> <div class=3D"h5"><br> <br> --Quanah<br> <br> --<br> <br> Quanah Gibson-Mount<br> Sr. Member of Technical Staff<br> Zimbra, Inc<br> A Division of VMware, Inc.<br> --------------------<br> Zimbra :: =A0the leader in open source messaging and collaboration<br> <br> </div></div></blockquote></div><br></div> --047d7b414c2ebdcec404d9a84c9d--

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by quanah＠zimbra.com 05 Apr '13

05 Apr '13

--On Friday, April 05, 2013 11:46 PM +0000 quanah(a)zimbra.com wrote: > --On Friday, April 05, 2013 11:36 PM +0000 lm5(a)ualberta.ca wrote: > >> Full_Name: Leo Mocofan >> Version: 2.4.31 >> OS: Debian Testing >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (129.128.11.107) > > If you are going to test back-mdb, then you need to use a current > OpenLDAP release (2.4.35). > > In any case, I don't see a bug report here? It sounds more like you're > asking for tuning advice? I would ask what filesystem you are using > (ext2? ext4?) etc. For ext4, I had to modify dirty_bytes to keep the > Debian/Ubuntu flush process from killing load performance. Oh, one other note -- I advise avoiding the debian/ubuntu build versions of BDB, if that is what you are using. They do not build BDB with the correct configure options, seriously impacting performance. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7566) ldapadd slower on Linux than BSD
by quanah＠zimbra.com 05 Apr '13

05 Apr '13

--On Friday, April 05, 2013 11:36 PM +0000 lm5(a)ualberta.ca wrote: > Full_Name: Leo Mocofan > Version: 2.4.31 > OS: Debian Testing > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (129.128.11.107) If you are going to test back-mdb, then you need to use a current OpenLDAP release (2.4.35). In any case, I don't see a bug report here? It sounds more like you're asking for tuning advice? I would ask what filesystem you are using (ext2? ext4?) etc. For ext4, I had to modify dirty_bytes to keep the Debian/Ubuntu flush process from killing load performance. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7566) ldapadd slower on Linux than BSD
by lm5＠ualberta.ca 05 Apr '13

05 Apr '13

Full_Name: Leo Mocofan Version: 2.4.31 OS: Debian Testing URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (129.128.11.107) We are currently testing Linux, OpenBSD and FreeBSD to run our LDAP service. Our tests showed that Linux has great performance numbers in most of the areas but we found one test that is very slow. The database has 1 million entries and is 4.5 GB in size. Importing the whole dababase using slapadd takes minutes on all platforms. When we tried to import the database using ldapadd we noticed a huge difference: FreeBSD - 42 min, OpenBSD - 59 min, Linux - 863 min. Changing file systems for backend in Linux had no effect. Using memory based file system for the backend in Linux the time for ldapadd dropped to 3 min. Strace for ldapadd shows: write(1, "adding new entry \"uid=noname,o"..., 60) = 60 time(NULL) = 1365202241 getrusage(RUSAGE_SELF, {ru_utime={1, 684105}, ru_stime={0, 212013}, ...}) = 0 time(NULL) = 1365202241 times({tms_utime=168, tms_stime=21, tms_cutime=0, tms_cstime=0}) = 1719044914 getrusage(RUSAGE_SELF, {ru_utime={1, 684105}, ru_stime={0, 212013}, ...}) = 0 time(NULL) = 1365202241 times({tms_utime=168, tms_stime=21, tms_cutime=0, tms_cstime=0}) = 1719044914 write(4, "\27\27\27\27\17uJ,\324\324\324\324"..., 1237) = 1237 poll([{fd=4, events=POLLIN|POLLPRI}], 1, 100) = 0 (Timeout) poll([{fd=4, events=POLLIN|POLLPRI}], 1, 100) = 0 (Timeout) poll([{fd=4, events=POLLIN|POLLPRI}], 1, 100) = 0 (Timeout) poll([{fd=4, events=POLLIN|POLLPRI}], 1, 100) = 1 ([{fd=4, revents=POLLIN}]) Strace for one thread of slapd: write(12, "\27\27\27\27\17uJ,\324\324\324\324"..., 117) = 117 time([1365202241]) = 1365202241 sendto(4, "<167>Apr 5 16:50:41 slapd[4513]"..., 79, MSG_NOSIGNAL, NULL, 0) = 79 futex(0x7f36f8fd6724, FUTEX_WAIT_PRIVATE, 9166, NULL) = 0 futex(0x7f36f8fd66f8, FUTEX_WAKE_PRIVATE, 1) = 0 time(NULL) = 1365202242 read(12, "", 5) = 0 write(6, "0", 1) = 1 futex(0x7f36f8fd6724, FUTEX_WAIT_PRIVATE, 9169, NULL Strace for another thread of slapd: futex(0x7f36f8fd66f8, FUTEX_WAKE_PRIVATE, 1) = 1 time(NULL) = 1365202241 epoll_wait(7, {{EPOLLIN, {u32=4177193844, u64=139874082155380}}}, 1024, 150000) = 1 read(5, "0", 8192) = 1 time(NULL) = 1365202241 epoll_wait(7, {{EPOLLIN, {u32=4177193872, u64=139874082155408}}}, 1024, 150000) = 1 epoll_ctl(7, EPOLL_CTL_MOD, 12, {0, {u32=4177193872, u64=139874082155408}}) = 0 futex(0x7f36f8fd6724, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f36f8fd6720, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1 time(NULL) = 1365202242 epoll_wait(7, {{EPOLLIN, {u32=4177193844, u64=139874082155380}}}, 1024, 150000) = 1 read(5, "0", 8192) = 1 time(NULL) = 1365202242 epoll_wait(7, {}, 1024, 150000) = 0 time(NULL) = 1365202392 epoll_wait(7, Ldapadd is stuck in poll system call, while one thread of slapd is waiting on epoll_wait(7, After couple of seconds when apparently nothing happens, then everything starts working again. Changing the database backend from to bdb to hdb and mdb doesn't seem to have an effect. We then tried to force SLAP_EVENT_WAIT to use select instead of epoll_wait on Linux and ldapadd is still much slower on Linux. We are runnin Debian testing as of Apr 5, 2013, with glibc-2.13, linux-3.2.41, libdb-5.1.29, openldap-2.4.31.

1 0

Re: (ITS#7563) slapd modifies attribute value of pwdAttribute
by michael＠stroeder.com 05 Apr '13

05 Apr '13

Michael Ströder wrote: > Howard, please try yourself first before answering. > Dieter is right here. > > Example: > > dn: cn=Default Password Policy,ou=Policies,dc=stroeder,dc=de > changetype: modify > delete: pwdAttribute > pwdAttribute: userPassword > - > add: pwdAttribute > pwdAttribute: 2.5.4.35 > - > > Reading it: > > dn: cn=Default Password Policy,ou=Policies,dc=stroeder,dc=de > cn: Default Password Policy > [..] > pwdAttribute: userPassword > [..] > > I vaguely remember I had to implement a work-around in web2ldap to deal with > that when generating delta modification data when the user edits such an entry. BTW: This has nothing to do with replication. Howard Chu wrote before: "Also as a general rule the X.500 data model requires that a server store and return exactly what the user provided." see http://www.openldap.org/lists/openldap-technical/201303/msg00189.html Ciao, Michael.

1 0

(ITS#7565) unacceptable growth on delete with back-mdb
by quanah＠OpenLDAP.org 05 Apr '13

05 Apr '13

Full_Name: Quanah Gibson-Mount Version: 2.4.35 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.39.181) With back-mdb, if you add a large number of users to the database (via ldapadd), and then delete them (via ldapmodify), the DB explodes in size. After the initial ldapadd of 30 million users, the DB is 17GB in size. After deleting the 30 million users, the DB is 52GB in size. This is a 3.05 times larger than the DBs initial size. With back-hdb, there is no change in size of the DB (it is static). Clearly this is not a desirable state of affairs. This appears to be a bug with the freelist. After the add is complete, we have: zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -f . Freelist Status Tree depth: 3 Branch pages: 19 Leaf pages: 2007 Overflow pages: 5155 Entries: 15879 Free pages: 2612121 My delete run is not yet complete, but it is now: zimbra@zre-ldap001:~/data/ldap/mdb/db$ mdb_stat -f . Freelist Status Tree depth: 3 Branch pages: 99 Leaf pages: 11096 Overflow pages: 20891 Entries: 82932 Free pages: 9381096 (and growing) --Quanah

1 0

Re: (ITS#7563) slapd modifies attribute value of pwdAttribute
by michael＠stroeder.com 05 Apr '13

05 Apr '13

This is a cryptographically signed message in MIME format. --------------ms070208010706030608090702 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Howard, please try yourself first before answering. Dieter is right here. Example: dn: cn=3DDefault Password Policy,ou=3DPolicies,dc=3Dstroeder,dc=3Dde changetype: modify delete: pwdAttribute pwdAttribute: userPassword - add: pwdAttribute pwdAttribute: 2.5.4.35 - Reading it: dn: cn=3DDefault Password Policy,ou=3DPolicies,dc=3Dstroeder,dc=3Dde cn: Default Password Policy [..] pwdAttribute: userPassword [..] I vaguely remember I had to implement a work-around in web2ldap to deal w= ith that when generating delta modification data when the user edits such an = entry. Ciao, Michael. --------------ms070208010706030608090702 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCC BT8wggQnoAMCAQICDwCmSwABAAIAivjZQ8SBvzANBgkqhkiG9w0BAQUFADB8MQswCQYDVQQG EwJERTEcMBoGA1UEChMTVEMgVHJ1c3RDZW50ZXIgR21iSDElMCMGA1UECxMcVEMgVHJ1c3RD ZW50ZXIgQ2xhc3MgMSBMMSBDQTEoMCYGA1UEAxMfVEMgVHJ1c3RDZW50ZXIgQ2xhc3MgMSBM MSBDQSBJWDAeFw0xMjA2MDYxOTAyMTZaFw0xMzA2MDcxOTAyMTZaMCgxCzAJBgNVBAYTAkRF MRkwFwYDVQQDDBBNaWNoYWVsIFN0csO2ZGVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEAxXZGav40rnGNLxEggBW94MILWHlfC8a23Jew5U1gPlfRTXOjjzmoaZ1uCyGdgF6M VvuO9T1aTQNGH+OdeGe3P7Tfc/NsLJFJ2wtd8blvhmodUgse2eypiWjNOd4gZuhalBhgsQ0K b5D6/1foghII4E264iZlJ7AJ+UYcO+GxvFWT0YMTbLckgDkZk7c3qwTozdhYvXarvqx+8Ou/ kuxpQQhac/ebzxpu0N+RHSf2KIUS0g0tEGnPtGv6iL+9QNHc4JKo9Y9KKVw3tQy+Re+FQLxB 1fPE5F+qxuD3AUENpOwkMsqWLM94ohtx3CFqLpxfUPrnKFLAHOhHEbByYGvFPwIDAQABo4IC EDCCAgwwgaUGCCsGAQUFBwEBBIGYMIGVMFEGCCsGAQUFBzAChkVodHRwOi8vd3d3LnRydXN0 Y2VudGVyLmRlL2NlcnRzZXJ2aWNlcy9jYWNlcnRzL3RjX2NsYXNzMV9MMV9DQV9JWC5jcnQw QAYIKwYBBQUHMAGGNGh0dHA6Ly9vY3NwLml4LnRjY2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1 c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAU6bgoHUbP/M34TpvF7ktg69g7P9EwDAYDVR0TAQH/ BAIwADBKBgNVHSAEQzBBMD8GCSqCFAAsAQEBATAyMDAGCCsGAQUFBwIBFiRodHRwOi8vd3d3 LnRydXN0Y2VudGVyLmRlL2d1aWRlbGluZXMwDgYDVR0PAQH/BAQDAgTwMB0GA1UdDgQWBBS2 KAWfTfgJ/JQ63qLGwTXYLnI+LzBiBgNVHR8EWzBZMFegVaBThlFodHRwOi8vY3JsLml4LnRj Y2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1c3RjZW50ZXIuZGUvY3JsL3YyL3RjX0NsYXNzMV9M MV9DQV9JWC5jcmwwMwYDVR0lBCwwKgYIKwYBBQUHAwIGCCsGAQUFBwMEBggrBgEFBQcDBwYK KwYBBAGCNxQCAjAfBgNVHREEGDAWgRRtaWNoYWVsQHN0cm9lZGVyLmNvbTANBgkqhkiG9w0B AQUFAAOCAQEAQ3bvVUpEq+cQrLpcogyt5BJNk/WvUvOHqhzyj28M9pg9hcDl1+MYl5qqj6tR GSTLPQZyf287pcmbMwbcTGZO/gbW9v7RYcut6RauWdwKMCUmKC3J4fVfDq9ZETA2WOV68ef4 B3Gzdhghsbp3Rhp5dDmrCVKAHlafm6ZwJrEQ9P76fxnQZzRLgeKpZep5ePH5YHUB3+YaOQvJ FG0bOXvfHhRiRG7/HW2G+yDgjHSxDz8AFzMWL/RFePqZ4pn6T/SM/qU6WEpW39MWyJNoH/Kx QDYK8gGYuesn1ciMCTnjrvZQj0fonGTO4SfWekJRkuGrJ7dYSZRjYbDcWBBkdFLWzzCCBdgw ggTAoAMCAQICDgboAAEAAkqWLSQM/sXJMA0GCSqGSIb3DQEBBQUAMHkxCzAJBgNVBAYTAkRF MRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSQwIgYDVQQLExtUQyBUcnVzdENlbnRl ciBVbml2ZXJzYWwgQ0ExJjAkBgNVBAMTHVRDIFRydXN0Q2VudGVyIFVuaXZlcnNhbCBDQSBJ MB4XDTA5MTEwMzE0MDgxOVoXDTI1MTIzMTIxNTk1OVowfDELMAkGA1UEBhMCREUxHDAaBgNV BAoTE1RDIFRydXN0Q2VudGVyIEdtYkgxJTAjBgNVBAsTHFRDIFRydXN0Q2VudGVyIENsYXNz IDEgTDEgQ0ExKDAmBgNVBAMTH1RDIFRydXN0Q2VudGVyIENsYXNzIDEgTDEgQ0EgSVgwggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC75pBuz2Lp6QuqthDVR+V8XSsncZpozVVt 5KLv5P7yemMRwleKyH3PjmYfZUVL64Biab1GjovFblqVGCrep/EfdRonq20yU+P7TVhiLP8Z 5cegDZotIYhZhM0d8cPIij6w5d4IJM/8QCy6QSOUu4ASiTVItoYE4AFPjLqpmPwcie0fiqHH hpgmHnJla/7PZdkMZEsaCfVDEWBmJuMzVprJPT40anjG5VBLyM2I5DlsUCaeQCy2O3w3sqf1 3dyzUcv03IICuNc63towXA31Qt0TaVNU6YAmQjMepdfMbspmCZ+G8D2+xophEPPR/1vkstst smUMqX0XrLonTUJczglPAgMBAAGjggJZMIICVTCBmgYIKwYBBQUHAQEEgY0wgYowUgYIKwYB BQUHMAKGRmh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvY2VydHNlcnZpY2VzL2NhY2VydHMv dGNfdW5pdmVyc2FsX3Jvb3RfSS5jcnQwNAYIKwYBBQUHMAGGKGh0dHA6Ly9vY3NwLnRjdW5p dmVyc2FsLUkudHJ1c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAUkqR1LKSevoFE63n8isWVpesQ dXMwEgYDVR0TAQH/BAgwBgEB/wIBADBSBgNVHSAESzBJMAYGBFUdIAAwPwYJKoIUACwBAQEB MDIwMAYIKwYBBQUHAgEWJGh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvZ3VpZGVsaW5lczAO BgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFOm4KB1Gz/zN+E6bxe5LYOvYOz/RMIH9BgNVHR8E gfUwgfIwge+ggeyggemGRmh0dHA6Ly9jcmwudGN1bml2ZXJzYWwtSS50cnVzdGNlbnRlci5k ZS9jcmwvdjIvdGNfdW5pdmVyc2FsX3Jvb3RfSS5jcmyGgZ5sZGFwOi8vd3d3LnRydXN0Y2Vu dGVyLmRlL0NOPVRDJTIwVHJ1c3RDZW50ZXIlMjBVbml2ZXJzYWwlMjBDQSUyMEksTz1UQyUy MFRydXN0Q2VudGVyJTIwR21iSCxPVT1yb290Y2VydHMsREM9dHJ1c3RjZW50ZXIsREM9ZGU/ Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlPzANBgkqhkiG9w0BAQUFAAOCAQEAOcjE m+6+mO5Icm+N53G2DpCM07LBFSGoRpBoX0oE8TrJaIQh2KXmBHVdn9LU8kt3QzLclctgvwJV 0KwcsMUUl5tlCsMPpR3s2Ek5lbWpvvr0HqtW56blAQiINV9nBd1EJFASIkRjefGbV2nOq9Yz UU+N8HA7jq1ROhd/NZZraGhjthwKyfjfHV7PKxGlY+3M0MbTIG+q/GhIfm0euDpFqhKG88e9 ALXr/uoSn3MzeOcoOWjTpW3adtFO4VWVgKbgG7jNrFbvRVlHmFLbOm4msjE5aXWxLiTwpJ2X iF4zKca1vAdAOgw9us90jEtOeiH6GzjNxEMvb7TfeO6Zkuc6HDGCA84wggPKAgEBMIGPMHwx CzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQLExxU QyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRlciBD bGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wCQYFKw4DAhoFAKCCAhMwGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNDA1MTYzODUwWjAjBgkq hkiG9w0BCQQxFgQUHxv/K+bf1DIc3hHVPnUWsdJ/pvEwbAYJKoZIhvcNAQkPMV8wXTALBglg hkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBoAYJKwYBBAGCNxAEMYGSMIGP MHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQL ExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRl ciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wgaIGCyqGSIb3DQEJEAILMYGS oIGPMHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYD VQQLExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENl bnRlciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wDQYJKoZIhvcNAQEBBQAE ggEAFn6FSF038qyMGUYl1VtsoCpXsoQU8AP1E9C6x5iOg3kEK/0hXv0OZq7XuAdDZCryRBxj CzUs25YPHdGANcXOJkNpq8EvYFiIgUFZj3jrc8bl2qFs0bm9YN955CsQIXkG32wVs8QcpTup EnuTssA2/zNePYZLpUKiOjyuEiD0EzfiThJA2UlrFzXGWxSIN+wTfv7hJuIpNttYiKo19PQf ITI6C2+LtiGMnnZ2AREgTgRhkJyrYPGwOFoEKmuwo7f6GKnA1WMa8+LEuceQXvGL9YObolq0 PVd6W+GRxWhXixQMkEk5Jwi7XV3tyRkV45c5ZA79ZiD/ldjV/k+2HcSF7gAAAAAAAA== --------------ms070208010706030608090702--

1 0

(ITS#7564) LMDB library bug: reopening LMDB may fail, fixed-address mmap
by tamas.kenez＠kishonti.net 05 Apr '13

05 Apr '13

Full_Name: Tamás Kenéz Version: LMDB 8eef7a42 OS: windows 7 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.141.191.242) Using the LMDB library (commit 8eef7a4275eda) on windows 7: To reproduce: Run mtest multiple times. The test sometimes fails with the with the windows error code 487 (ERROR_INVALID_ADDRESS) in mdb_env_open -> mdb_env_open2 at this line env->me_map = MapViewOfFileEx(mh, flags & MDB_WRITEMAP ? FILE_MAP_WRITE : FILE_MAP_READ, 0, 0, env->me_mapsize, meta.mm_address); The reason is that when windows fails to map at the specified address (meta.mm_address) it returns 0. I tried this quick workaround: if ( !env->me_map ) env->me_map = MapViewOfFileEx(mh, flags & MDB_WRITEMAP ? FILE_MAP_WRITE : FILE_MAP_READ, 0, 0, env->me_mapsize, NULL); which does return valid address, but then it fails later here: else if (meta.mm_address && env->me_map != meta.mm_address) { /* Can happen because the address argument to mmap() is just a * hint. mmap() can pick another, e.g. if the range is in use. * The MAP_FIXED flag would prevent that, but then mmap could * instead unmap existing pages to make room for the new map. */ return EBUSY; /* TODO: Make a new MDB_* error code? */

1 0

Re: (ITS#7515) Nested liblmdb transaction bugs
by hyc＠symas.com 05 Apr '13

05 Apr '13

h.b.furuseth(a)usit.uio.no wrote: > I wrote: >>> Can't use a DBI from an aborted child txn, unlike aborted main txn: >> (...) >> Well, closing the DBI in mdb_txn_abort() caused problems. A fix >> in the opposite direction is easy, if we want DBIs to work that >> way: mdb_env_open() can open the DBI in any parent txns too. > > To get more consistent behavior, if that wasn't clear: Any parent > txn will receive the DBI independently of commit/abort, just like > the MDB_env. Future children of a preexisting txn still differ, > which is probably for the best. Changing that would take locking. > After much discussion, this part has been reverted. The rationale is simple: nothing created inside a TXN may be visible outside the TXN until the TXN successfully commits. On an abort or failed commit, all DBIs opened in the TXN are automatically closed, because technically they never existed. -- -- Howard Chu CTO, 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#7563) slapd modifies attribute value of pwdAttribute
by hyc＠symas.com 05 Apr '13

05 Apr '13

dieter(a)dkluenter.de wrote: > Full_Name: > Version: 2.4.33 > OS: openSuSE-12.3-x86_64 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (91.65.235.202) > > > the pwdAttribute type requires a syntax of 1.3.6.1.4.1.1466.115.121.1.38, > according to man slapo-ppolicy and ppolicy.schema. > when adding a policy, the value of pwdAttribute gets changend from OID 2.5.4.35 > to userPassword. You are mistaken. slapd never changes this attribute from what the user stored. > In a replicated system syncrepl complaints about > syncrepl_message_to_entry: rid=001 mods check (pwdAttribute: value #0 invalid > per syntax) do_syncrepl: rid=001 rc 21 retrying. This error will go away if you configure the ppolicy overlay on the consumer. Closing this ITS. > > -Dieter > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#7563) slapd modifies attribute value of pwdAttribute
by dieter＠dkluenter.de 05 Apr '13

05 Apr '13

Full_Name: Version: 2.4.33 OS: openSuSE-12.3-x86_64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (91.65.235.202) the pwdAttribute type requires a syntax of 1.3.6.1.4.1.1466.115.121.1.38, according to man slapo-ppolicy and ppolicy.schema. when adding a policy, the value of pwdAttribute gets changend from OID 2.5.4.35 to userPassword. In a replicated system syncrepl complaints about syncrepl_message_to_entry: rid=001 mods check (pwdAttribute: value #0 invalid per syntax) do_syncrepl: rid=001 rc 21 retrying. -Dieter

1 0

(ITS#7562) Remove deprecated slapd.replog(5) reference in manpages
by fumiyas＠osstech.co.jp 04 Apr '13

04 Apr '13

Full_Name: SATOH Fumiyasu Version: master OS: URL: https://gist.github.com/fumiyas/5316077 Submission from: (NULL) (219.111.105.97) Some manpages refer deprecated slapd.replog(5).

1 0

(ITS#7561) mdb_drop bugs
by h.b.furuseth＠usit.uio.no 04 Apr '13

04 Apr '13

Full_Name: Hallvard B Furuseth Version: mdb.master 8eef7a4275eda8f2fa2e0d1e67c1d5cbcd91607e OS: Linux x86_64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.69.163.163) Submitted by: hallvard mdb_drop() does not seem to return overflow pages to the freelist. Does not call cursor_del or anything, nor 'ovpages' loop like it has. E.g. the enclosed program which writes some pages and then drops the DB shows 59 free of 62 useed pages with non-overflows, but just 3 free of 38-39 with overflows. #include <lmdb.h> #include <assert.h> #include <stdio.h> #include <stdlib.h> int main(void) { MDB_env *env; MDB_txn *txn; MDB_dbi dbi; int rc, sz, sum; # define DBPATH "test.mdb" # define E(e) ((void) (rc = (e)), assert(!rc)) for (sz = 1500; sz < 9000; sz *= 2) { MDB_val key = {sizeof(sum), &sum}, data = {sz, NULL}; printf("======== datasize %d ========\n", sz); fflush(NULL); remove(DBPATH); E(mdb_env_create(&env)); E(mdb_env_set_maxdbs(env, 1)); E(mdb_env_open(env, DBPATH, MDB_NOSUBDIR, 0666)); E(mdb_txn_begin(env, 0, 0, &txn)); { E(mdb_dbi_open(txn, "foo", MDB_CREATE, &dbi)); for (sum = 0; (sum += sz) < 100000; ) E(mdb_put(txn, dbi, &key, &data, MDB_RESERVE)); E(mdb_txn_commit(txn)); } E(mdb_txn_begin(env, 0, 0, &txn)); { E(mdb_drop(txn, dbi, 1)); E(mdb_txn_commit(txn)); } mdb_env_close(env); system("../mdb_stat -naef " DBPATH " | grep -v ': 0$'"); } return 0; }

1 0

Re: (ITS#7447) backsql and german umlaute
by masarati＠aero.polimi.it 04 Apr '13

04 Apr '13

On 04/04/2013 08:13 AM, tomas.novosad(a)linuxbox.cz wrote: > Hello, > > i got exactly same problem. > > Only the discussed character is different ;-)). > When ThunderBird (or ldapsearch, it doesnt matter) send search query to LDAP with some UTF-8 character, > the result query to DB (PGSQL in this case) is like > (upper(last_name) LIKE '%šEV%') > > where the search parameter is: > %<lower case utf8 character>EV% > > obviously backsql does not correctly handle UTF8 characters. > > I can't find any way how to avoid this. > If only back-sql would leave the upper case conversion on DB - like > this: > (upper(last_name) LIKE upper('%šEV%'T The solution is to augment table ldap_attr_mappings (with non-trivial implications on DN searching and matching) with a field that specifies the encoding for a particular attribute, and convert back and forth any time an operation affects those attributes. Not trivial, but contributions are welcome. p. -- Pierangelo Masarati Associate Professor Dipartimento di Scienze e Tecnologie Aerospaziali Politecnico di Milano

1 0

(ITS#7447) backsql and german umlaute
by tomas.novosad＠linuxbox.cz 03 Apr '13

03 Apr '13

Hello, i got exactly same problem. Only the discussed character is different ;-)). When ThunderBird (or ldapsearch, it doesnt matter) send search query to LDAP with some UTF-8 character, the result query to DB (PGSQL in this case) is like (upper(last_name) LIKE '%šEV%') where the search parameter is: %<lower case utf8 character>EV% obviously backsql does not correctly handle UTF8 characters. I can't find any way how to avoid this. If only back-sql would leave the upper case conversion on DB - like this: (upper(last_name) LIKE upper('%šEV%')) or use ILIKE Anyone has any suggestion how to workaround this? Thanks in advance -- Tomáš Novosad

1 0

Re: (ITS#7560) ldappasword issue
by quanah＠zimbra.com 03 Apr '13

03 Apr '13

--On Wednesday, April 03, 2013 3:05 PM +0000 aman_bista(a)hotmail.com wrote: > Full_Name: amanbista > Version: 2.4.34 > OS: redhat linux 6.4 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (70.122.251.187) The ITS system is for filing bug reports only. Please direct your usage question to openldap-technical(a)openldap.org. This ITS will be closed. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7560) ldappasword issue
by aman_bista＠hotmail.com 03 Apr '13

03 Apr '13

Full_Name: amanbista Version: 2.4.34 OS: redhat linux 6.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (70.122.251.187) sir , i configured slapd.conf file, ran slapppaswd, eneted this password in slapd.conf file,i edited /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb.ldif and added olcRootPW: {SSHA}r2or9f2vYlvieCu0LP6wTnSdYfrddsuV olcTLSCertificateFile: /etc/pki/tls/certs/slapdcert.pem olcTLSCertificateKeyFile: /etc/pki/tls/certs/slapdkey.pem after i specified monitoring privilleges /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{2\}monitor.ldif changed the default domain name to our domain name updated db edited /etc/sysconfig/ldap SLAPD_LDAPS=yes after that i created certicate and tested configuration, it was successfull. i started ldap server created base domain as vi base.ldif to import base information to ldap directory. i ran command to dapadd -x -W -D cn=Manager,dc=yourdomain,dc=com -f base.ldif this is where it asked me ldappassword. it showed me error. what do i do next. please help. Thank you

1 0

Re: (ITS#7537) ppolicy hangs slapd on 64bit version debian
by marek.platta＠blstream.com 03 Apr '13

03 Apr '13

Hi, my config is: include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/nis.schema include /etc/ldap/schema/inetorgperson.schema include /etc/ldap/schema/openldap.schema include /etc/ldap/schema/ppolicy.schema pidfile /var/run/slapd.pid argsfile /var/run/slapd.args loglevel none modulepath /root/openldap-2.4.34/libraries/libldap/ moduleload back_hdb moduleload ppolicy.la sizelimit 99999999 tool-threads 1 backend hdb database monitor database hdb suffix "dc=example,dc=com" overlay ppolicy ppolicy_default "cn=default,ou=policies,dc=example,dc=com" rootdn "cn=Directory Manager,dc=example,dc=com" rootpw {SSHA}5jMwnEvS+5cgKVtQVieEYScUjEQvhSkQ directory "/usr/local/var/openldap-data" dbconfig set_cachesize 0 209715200 0 dbconfig set_lk_max_objects 150000 dbconfig set_lk_max_locks 150000 dbconfig set_lk_max_lockers 150000 index objectClass eq index uid eq index businessUnit eq index cn eq index lead eq index ishidden eq lastmod on checkpoint 512 30 access to attrs=userPassword,shadowLastChange,sambaLMPassword,sambaNTPassword by dn="cn=Directory Manager" write by dn="cn=admin-ro,dc=example,dc=com" read by anonymous auth by self write by * none access to * by dn="cn=Directory Manager" write by * read

1 0

Re: (ITS#7537) ppolicy hangs slapd on 64bit version debian
by hyc＠symas.com 03 Apr '13

03 Apr '13

Howard Chu wrote: > marek.platta(a)blstream.com wrote: >> Hi, >> >> I'm getting same error on 2.4.34 version > > Post your config. Also post a gdb backtrace from slapd when it's in this state. -- -- Howard Chu CTO, 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#7537) ppolicy hangs slapd on 64bit version debian
by hyc＠symas.com 03 Apr '13

03 Apr '13

marek.platta(a)blstream.com wrote: > Hi, > > I'm getting same error on 2.4.34 version Post your config. -- -- Howard Chu CTO, 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#7537) ppolicy hangs slapd on 64bit version debian
by marek.platta＠blstream.com 03 Apr '13

03 Apr '13

Hi, I'm getting same error on 2.4.34 version slapd says: 515bf1bf daemon: activity on 1 descriptor 515bf1bf daemon: activity on:515bf1bf 515bf1bf slap_listener_activate(7): 515bf1bf daemon: epoll: listen=7 busy 515bf1bf daemon: epoll: listen=8 active_threads=0 tvp=zero 515bf1bf >>> slap_listener(ldap:///) 515bf1bf daemon: listen=7, new connection on 12 515bf1bf daemon: added 12r (active) listener=(nil) 515bf1bf conn=1003 fd=12 ACCEPT from IP=192.168.6.212:53225 (IP=0.0.0.0:389) 515bf1bf daemon: activity on 2 descriptors 515bf1bf daemon: activity on:515bf1bf 12r515bf1bf 515bf1bf daemon: read active on 12 515bf1bf daemon: epoll: listen=7 active_threads=0 tvp=zero 515bf1bf daemon: epoll: listen=8 active_threads=0 tvp=zero 515bf1bf connection_get(12) 515bf1bf connection_get(12): got connid=1003 515bf1bf connection_read(12): checking for input on id=1003 ber_get_next ldap_read: want=8, got=8 0000: 30 37 02 01 01 60 32 02 07...`2. ldap_read: want=49, got=49 0000: 01 03 04 26 63 6e 3d 44 69 72 65 63 74 6f 72 79 ...&cn=Directory 0010: 20 6d 61 6e 61 67 65 72 2c 64 63 3d 65 78 61 6d manager,dc=exam 0020: 70 6c 65 2c 64 63 3d 63 6f 6d 80 05 74 65 73 74 ple,dc=com..test 0030: 31 1 ber_get_next: tag 0x30 len 55 contents: ber_dump: buf=0x1cea6f0 ptr=0x1cea6f0 end=0x1cea727 len=55 0000: 02 01 01 60 32 02 01 03 04 26 63 6e 3d 44 69 72 ...`2....&cn=Dir 0010: 65 63 74 6f 72 79 20 6d 61 6e 61 67 65 72 2c 64 ectory manager,d 0020: 63 3d 65 78 61 6d 70 6c 65 2c 64 63 3d 63 6f 6d c=example,dc=com 0030: 80 05 74 65 73 74 31 ..test1 515bf1bf op tag 0x60, time 1364980159 ber_get_next ldap_read: want=8 error=Resource temporarily unavailable 515bf1bf conn=1003 op=0 do_bind ber_scanf fmt ({imt) ber: ber_dump: buf=0x1cea6f0 ptr=0x1cea6f3 end=0x1cea727 len=52 0000: 60 32 02 01 03 04 26 63 6e 3d 44 69 72 65 63 74 `2....&cn=Direct 0010: 6f 72 79 20 6d 61 6e 61 67 65 72 2c 64 63 3d 65 ory manager,dc=e 0020: 78 61 6d 70 6c 65 2c 64 63 3d 63 6f 6d 80 05 74 xample,dc=com..t 0030: 65 73 74 31 est1 ber_scanf fmt (m}) ber: ber_dump: buf=0x1cea6f0 ptr=0x1cea720 end=0x1cea727 len=7 0000: 00 05 74 65 73 74 31 ..test1 515bf1bf >>> dnPrettyNormal: <cn=Directory manager,dc=example,dc=com> => ldap_bv2dn(cn=Directory manager,dc=example,dc=com,0) <= ldap_bv2dn(cn=Directory manager,dc=example,dc=com)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=Directory manager,dc=example,dc=com)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=directory manager,dc=example,dc=com)=0 515bf1bf <<< dnPrettyNormal: <cn=Directory manager,dc=example,dc=com>, <cn=directory manager,dc=example,dc=com> 515bf1bf conn=1003 op=0 BIND dn="cn=Directory manager,dc=example,dc=com" method=128 515bf1bf do_bind: version=3 dn="cn=Directory manager,dc=example,dc=com" method=128 515bf1bf ==> hdb_bind: dn: cn=Directory manager,dc=example,dc=com 515bf1bf conn=1003 op=0 BIND dn="cn=Directory manager,dc=example,dc=com" mech=SIMPLE ssf=0 515bf1bf do_bind: v3 bind: "cn=Directory manager,dc=example,dc=com" to "cn=Directory manager,dc=example,dc=com" 515bf1bf send_ldap_result: conn=1003 op=0 p=3 515bf1bf send_ldap_result: err=0 matched="" text="" 515bf1bf send_ldap_response: msgid=1 tag=97 err=0 ber_flush2: 14 bytes to sd 12 0000: 30 0c 02 01 01 61 07 0a 01 00 04 00 04 00 0....a........ ldap_write: want=14, written=14 0000: 30 0c 02 01 01 61 07 0a 01 00 04 00 04 00 0....a........ 515bf1bf conn=1003 op=0 RESULT tag=97 err=0 text= 515bf1bf daemon: activity on 1 descriptor 515bf1bf daemon: activity on:515bf1bf 515bf1bf daemon: epoll: listen=7 active_threads=0 tvp=zero 515bf1bf daemon: epoll: listen=8 active_threads=0 tvp=zero 515bf1bf daemon: activity on 1 descriptor 515bf1bf daemon: activity on:515bf1bf 12r515bf1bf 515bf1bf daemon: read active on 12 515bf1bf daemon: epoll: listen=7 active_threads=0 tvp=zero 515bf1bf daemon: epoll: listen=8 active_threads=0 tvp=zero 515bf1bf connection_get(12) 515bf1bf connection_get(12): got connid=1003 515bf1bf connection_read(12): checking for input on id=1003 ber_get_next ldap_read: want=8, got=8 0000: 30 4d 02 01 02 63 48 04 0M...cH. ldap_read: want=71, got=71 0000: 28 63 6e 3d 64 65 66 61 75 6c 74 2c 6f 75 3d 70 (cn=default,ou=p 0010: 6f 6c 69 63 69 65 73 2c 64 63 3d 65 78 61 6d 70 olicies,dc=examp 0020: 6c 65 2c 64 63 3d 63 6f 6d 0a 01 00 0a 01 00 02 le,dc=com....... 0030: 01 00 02 01 00 01 01 00 87 0b 6f 62 6a 65 63 74 ..........object 0040: 43 6c 61 73 73 30 00 Class0. ber_get_next: tag 0x30 len 77 contents: ber_dump: buf=0x1ceaff0 ptr=0x1ceaff0 end=0x1ceb03d len=77 0000: 02 01 02 63 48 04 28 63 6e 3d 64 65 66 61 75 6c ...cH.(cn=defaul 0010: 74 2c 6f 75 3d 70 6f 6c 69 63 69 65 73 2c 64 63 t,ou=policies,dc 0020: 3d 65 78 61 6d 70 6c 65 2c 64 63 3d 63 6f 6d 0a =example,dc=com. 0030: 01 00 0a 01 00 02 01 00 02 01 00 01 01 00 87 0b ................ 0040: 6f 62 6a 65 63 74 43 6c 61 73 73 30 00 objectClass0. 515bf1bf op tag 0x63, time 1364980159 ber_get_next ldap_read: want=8 error=Resource temporarily unavailable 515bf1bf conn=1003 op=1 do_search ber_scanf fmt ({miiiib) ber: ber_dump: buf=0x1ceaff0 ptr=0x1ceaff3 end=0x1ceb03d len=74 0000: 63 48 04 28 63 6e 3d 64 65 66 61 75 6c 74 2c 6f cH.(cn=default,o 0010: 75 3d 70 6f 6c 69 63 69 65 73 2c 64 63 3d 65 78 u=policies,dc=ex 0020: 61 6d 70 6c 65 2c 64 63 3d 63 6f 6d 0a 01 00 0a ample,dc=com.... 0030: 01 00 02 01 00 02 01 00 01 01 00 87 0b 6f 62 6a .............obj 0040: 65 63 74 43 6c 61 73 73 30 00 ectClass0. 515bf1bf >>> dnPrettyNormal: <cn=default,ou=policies,dc=example,dc=com> => ldap_bv2dn(cn=default,ou=policies,dc=example,dc=com,0) <= ldap_bv2dn(cn=default,ou=policies,dc=example,dc=com)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=default,ou=policies,dc=example,dc=com)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=default,ou=policies,dc=example,dc=com)=0 515bf1bf <<< dnPrettyNormal: <cn=default,ou=policies,dc=example,dc=com>, <cn=default,ou=policies,dc=example,dc=com> 515bf1bf SRCH "cn=default,ou=policies,dc=example,dc=com" 0 0515bf1bf 0 0 0 515bf1bf begin get_filter 515bf1bf PRESENT ber_scanf fmt (m) ber: ber_dump: buf=0x1ceaff0 ptr=0x1ceb02e end=0x1ceb03d len=15 0000: 87 0b 6f 62 6a 65 63 74 43 6c 61 73 73 30 00 ..objectClass0. 515bf1bf end get_filter 0 515bf1bf filter: (objectClass=*) ber_scanf fmt ({M}}) ber: ber_dump: buf=0x1ceaff0 ptr=0x1ceb03b end=0x1ceb03d len=2 0000: 00 00 .. 515bf1bf attrs:515bf1bf 515bf1bf conn=1003 op=1 SRCH base="cn=default,ou=policies,dc=example,dc=com" scope=0 deref=0 filter="(objectClass=*)" 515bf1bf => hdb_search 515bf1bf bdb_dn2entry("cn=default,ou=policies,dc=example,dc=com") 515bf1bf => access_allowed: search access to "cn=default,ou=policies,dc=example,dc=com" "entry" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: search access granted by manage(=mwrscxd) 515bf1bf base_candidates: base: "cn=default,ou=policies,dc=example,dc=com" (0x000004b5) 515bf1bf => test_filter 515bf1bf PRESENT 515bf1bf => access_allowed: search access to "cn=default,ou=policies,dc=example,dc=com" "objectClass" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: search access granted by manage(=mwrscxd) 515bf1bf <= test_filter 6 515bf1bf => send_search_entry: conn 1003 dn="cn=default,ou=policies,dc=example,dc=com" 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "entry" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (cn) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "cn" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (objectClass) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "objectClass" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result was in cache (objectClass) 515bf1bf => access_allowed: result was in cache (objectClass) 515bf1bf => access_allowed: result was in cache (objectClass) 515bf1bf => access_allowed: result not in cache (pwdAttribute) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdAttribute" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdExpireWarning) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdExpireWarning" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdInHistory) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdInHistory" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdMustChange) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdMustChange" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdSafeModify) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdSafeModify" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdAllowUserChange) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdAllowUserChange" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdLockout) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdLockout" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdLockoutDuration) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdLockoutDuration" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdMaxFailure) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdMaxFailure" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdMaxAge) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdMaxAge" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdCheckQuality) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdCheckQuality" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf => access_allowed: result not in cache (pwdMinLength) 515bf1bf => access_allowed: read access to "cn=default,ou=policies,dc=example,dc=com" "pwdMinLength" requested 515bf1bf <= root access granted 515bf1bf => access_allowed: read access granted by manage(=mwrscxd) 515bf1bf conn=1003 op=1 ENTRY dn="cn=default,ou=policies,dc=example,dc=com" ber_flush2: 440 bytes to sd 12 0000: 30 82 01 b4 02 01 02 64 82 01 ad 04 28 63 6e 3d 0......d....(cn= 0010: 64 65 66 61 75 6c 74 2c 6f 75 3d 70 6f 6c 69 63 default,ou=polic 0020: 69 65 73 2c 64 63 3d 65 78 61 6d 70 6c 65 2c 64 ies,dc=example,d 0030: 63 3d 63 6f 6d 30 82 01 7f 30 0f 04 02 63 6e 31 c=com0...0...cn1 0040: 09 04 07 64 65 66 61 75 6c 74 30 39 04 0b 6f 62 ...default09..ob 0050: 6a 65 63 74 43 6c 61 73 73 31 2a 04 03 74 6f 70 jectClass1*..top 0060: 04 09 70 77 64 50 6f 6c 69 63 79 04 06 70 65 72 ..pwdPolicy..per 0070: 73 6f 6e 04 10 70 77 64 50 6f 6c 69 63 79 43 68 son..pwdPolicyCh 0080: 65 63 6b 65 72 30 1e 04 0c 70 77 64 41 74 74 72 ecker0...pwdAttr 0090: 69 62 75 74 65 31 0e 04 0c 75 73 65 72 50 61 73 ibute1...userPas 00a0: 73 77 6f 72 64 30 1a 04 10 70 77 64 45 78 70 69 sword0...pwdExpi 00b0: 72 65 57 61 72 6e 69 6e 67 31 06 04 04 33 36 30 reWarning1...360 00c0: 30 30 13 04 0c 70 77 64 49 6e 48 69 73 74 6f 72 00...pwdInHistor 00d0: 79 31 03 04 01 31 30 17 04 0d 70 77 64 4d 75 73 y1...10...pwdMus 00e0: 74 43 68 61 6e 67 65 31 06 04 04 54 52 55 45 30 tChange1...TRUE0 00f0: 18 04 0d 70 77 64 53 61 66 65 4d 6f 64 69 66 79 ...pwdSafeModify 0100: 31 07 04 05 46 41 4c 53 45 30 1c 04 12 70 77 64 1...FALSE0...pwd 0110: 41 6c 6c 6f 77 55 73 65 72 43 68 61 6e 67 65 31 AllowUserChange1 0120: 06 04 04 54 52 55 45 30 15 04 0a 70 77 64 4c 6f ...TRUE0...pwdLo 0130: 63 6b 6f 75 74 31 07 04 05 46 41 4c 53 45 30 1a ckout1...FALSE0. 0140: 04 12 70 77 64 4c 6f 63 6b 6f 75 74 44 75 72 61 ..pwdLockoutDura 0150: 74 69 6f 6e 31 04 04 02 31 32 30 14 04 0d 70 77 tion1...120...pw 0160: 64 4d 61 78 46 61 69 6c 75 72 65 31 03 04 01 35 dMaxFailure1...5 0170: 30 19 04 09 70 77 64 4d 61 78 41 67 65 31 0c 04 0...pwdMaxAge1.. 0180: 0a 32 35 39 32 30 30 30 30 30 30 30 16 04 0f 70 .25920000000...p 0190: 77 64 43 68 65 63 6b 51 75 61 6c 69 74 79 31 03 wdCheckQuality1. 01a0: 04 01 32 30 13 04 0c 70 77 64 4d 69 6e 4c 65 6e ..20...pwdMinLen 01b0: 67 74 68 31 03 04 01 37 gth1...7 ldap_write: want=440, written=440 0000: 30 82 01 b4 02 01 02 64 82 01 ad 04 28 63 6e 3d 0......d....(cn= 0010: 64 65 66 61 75 6c 74 2c 6f 75 3d 70 6f 6c 69 63 default,ou=polic 0020: 69 65 73 2c 64 63 3d 65 78 61 6d 70 6c 65 2c 64 ies,dc=example,d 0030: 63 3d 63 6f 6d 30 82 01 7f 30 0f 04 02 63 6e 31 c=com0...0...cn1 0040: 09 04 07 64 65 66 61 75 6c 74 30 39 04 0b 6f 62 ...default09..ob 0050: 6a 65 63 74 43 6c 61 73 73 31 2a 04 03 74 6f 70 jectClass1*..top 0060: 04 09 70 77 64 50 6f 6c 69 63 79 04 06 70 65 72 ..pwdPolicy..per 0070: 73 6f 6e 04 10 70 77 64 50 6f 6c 69 63 79 43 68 son..pwdPolicyCh 0080: 65 63 6b 65 72 30 1e 04 0c 70 77 64 41 74 74 72 ecker0...pwdAttr 0090: 69 62 75 74 65 31 0e 04 0c 75 73 65 72 50 61 73 ibute1...userPas 00a0: 73 77 6f 72 64 30 1a 04 10 70 77 64 45 78 70 69 sword0...pwdExpi 00b0: 72 65 57 61 72 6e 69 6e 67 31 06 04 04 33 36 30 reWarning1...360 00c0: 30 30 13 04 0c 70 77 64 49 6e 48 69 73 74 6f 72 00...pwdInHistor 00d0: 79 31 03 04 01 31 30 17 04 0d 70 77 64 4d 75 73 y1...10...pwdMus 00e0: 74 43 68 61 6e 67 65 31 06 04 04 54 52 55 45 30 tChange1...TRUE0 00f0: 18 04 0d 70 77 64 53 61 66 65 4d 6f 64 69 66 79 ...pwdSafeModify 0100: 31 07 04 05 46 41 4c 53 45 30 1c 04 12 70 77 64 1...FALSE0...pwd 0110: 41 6c 6c 6f 77 55 73 65 72 43 68 61 6e 67 65 31 AllowUserChange1 0120: 06 04 04 54 52 55 45 30 15 04 0a 70 77 64 4c 6f ...TRUE0...pwdLo 0130: 63 6b 6f 75 74 31 07 04 05 46 41 4c 53 45 30 1a ckout1...FALSE0. 0140: 04 12 70 77 64 4c 6f 63 6b 6f 75 74 44 75 72 61 ..pwdLockoutDura 0150: 74 69 6f 6e 31 04 04 02 31 32 30 14 04 0d 70 77 tion1...120...pw 0160: 64 4d 61 78 46 61 69 6c 75 72 65 31 03 04 01 35 dMaxFailure1...5 0170: 30 19 04 09 70 77 64 4d 61 78 41 67 65 31 0c 04 0...pwdMaxAge1.. 0180: 0a 32 35 39 32 30 30 30 30 30 30 30 16 04 0f 70 .25920000000...p 0190: 77 64 43 68 65 63 6b 51 75 61 6c 69 74 79 31 03 wdCheckQuality1. 01a0: 04 01 32 30 13 04 0c 70 77 64 4d 69 6e 4c 65 6e ..20...pwdMinLen 01b0: 67 74 68 31 03 04 01 37 gth1...7 515bf1bf <= send_search_entry: conn 1003 exit. 515bf1bf send_ldap_result: conn=1003 op=1 p=3 515bf1bf send_ldap_result: err=0 matched="" text="" 515bf1bf send_ldap_response: msgid=2 tag=101 err=0 ber_flush2: 14 bytes to sd 12 0000: 30 0c 02 01 02 65 07 0a 01 00 04 00 04 00 0....e........ ldap_write: want=14, written=14 0000: 30 0c 02 01 02 65 07 0a 01 00 04 00 04 00 0....e........ 515bf1bf conn=1003 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= 515bf1bf daemon: activity on 1 descriptor 515bf1bf daemon: activity on:515bf1bf 515bf1bf daemon: epoll: listen=7 active_threads=0 tvp=zero 515bf1bf daemon: epoll: listen=8 active_threads=0 tvp=zero 515bf1c0 daemon: activity on 1 descriptor 515bf1c0 daemon: activity on:515bf1c0 12r515bf1c0 515bf1c0 daemon: read active on 12 515bf1c0 daemon: epoll: listen=7 active_threads=0 tvp=zero 515bf1c0 daemon: epoll: listen=8 active_threads=0 tvp=zero 515bf1c0 connection_get(12) 515bf1c0 connection_get(12): got connid=1003 515bf1c0 connection_read(12): checking for input on id=1003 ber_get_next ldap_read: want=8, got=8 0000: 30 62 02 01 03 66 5d 04 0b...f]. ldap_read: want=92, got=92 0000: 28 63 6e 3d 64 65 66 61 75 6c 74 2c 6f 75 3d 70 (cn=default,ou=p 0010: 6f 6c 69 63 69 65 73 2c 64 63 3d 65 78 61 6d 70 olicies,dc=examp 0020: 6c 65 2c 64 63 3d 63 6f 6d 30 31 30 15 0a 01 01 le,dc=com010.... 0030: 30 10 04 0c 70 77 64 4d 69 6e 4c 65 6e 67 74 68 0...pwdMinLength 0040: 31 00 30 18 0a 01 00 30 13 04 0c 70 77 64 4d 69 1.0....0...pwdMi 0050: 6e 4c 65 6e 67 74 68 31 03 04 01 38 nLength1...8 ber_get_next: tag 0x30 len 98 contents: ber_dump: buf=0x1dec740 ptr=0x1dec740 end=0x1dec7a2 len=98 0000: 02 01 03 66 5d 04 28 63 6e 3d 64 65 66 61 75 6c ...f].(cn=defaul 0010: 74 2c 6f 75 3d 70 6f 6c 69 63 69 65 73 2c 64 63 t,ou=policies,dc 0020: 3d 65 78 61 6d 70 6c 65 2c 64 63 3d 63 6f 6d 30 =example,dc=com0 0030: 31 30 15 0a 01 01 30 10 04 0c 70 77 64 4d 69 6e 10....0...pwdMin 0040: 4c 65 6e 67 74 68 31 00 30 18 0a 01 00 30 13 04 Length1.0....0.. 0050: 0c 70 77 64 4d 69 6e 4c 65 6e 67 74 68 31 03 04 .pwdMinLength1.. 0060: 01 38 .8 515bf1c0 op tag 0x66, time 1364980160 ber_get_next ldap_read: want=8 error=Resource temporarily unavailable 515bf1c0 conn=1003 op=2 do_modify ber_scanf fmt ({m) ber: ber_dump: buf=0x1dec740 ptr=0x1dec743 end=0x1dec7a2 len=95 0000: 66 5d 04 28 63 6e 3d 64 65 66 61 75 6c 74 2c 6f f].(cn=default,o 0010: 75 3d 70 6f 6c 69 63 69 65 73 2c 64 63 3d 65 78 u=policies,dc=ex 0020: 61 6d 70 6c 65 2c 64 63 3d 63 6f 6d 30 31 30 15 ample,dc=com010. 0030: 0a 01 01 30 10 04 0c 70 77 64 4d 69 6e 4c 65 6e ...0...pwdMinLen 0040: 67 74 68 31 00 30 18 0a 01 00 30 13 04 0c 70 77 gth1.0....0...pw 0050: 64 4d 69 6e 4c 65 6e 67 74 68 31 03 04 01 38 dMinLength1...8 515bf1c0 conn=1003 op=2 do_modify: dn (cn=default,ou=policies,dc=example,dc=com) ber_scanf fmt ({e{m[W]}}) ber: ber_dump: buf=0x1dec740 ptr=0x1dec771 end=0x1dec7a2 len=49 0000: 30 15 0a 01 01 30 10 04 0c 70 77 64 4d 69 6e 4c 0....0...pwdMinL 0010: 65 6e 67 74 68 31 00 30 18 0a 01 00 30 13 04 0c ength1.0....0... 0020: 70 77 64 4d 69 6e 4c 65 6e 67 74 68 31 03 04 01 pwdMinLength1... 0030: 38 8 ber_scanf fmt ({e{m[W]}}) ber: ber_dump: buf=0x1dec740 ptr=0x1dec788 end=0x1dec7a2 len=26 0000: 30 18 0a 01 00 30 13 04 0c 70 77 64 4d 69 6e 4c 0....0...pwdMinL 0010: 65 6e 67 74 68 31 03 04 01 38 ength1...8 515bf1c0 >>> dnPrettyNormal: <cn=default,ou=policies,dc=example,dc=com> => ldap_bv2dn(cn=default,ou=policies,dc=example,dc=com,0) <= ldap_bv2dn(cn=default,ou=policies,dc=example,dc=com)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=default,ou=policies,dc=example,dc=com)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=default,ou=policies,dc=example,dc=com)=0 515bf1c0 <<< dnPrettyNormal: <cn=default,ou=policies,dc=example,dc=com>, <cn=default,ou=policies,dc=example,dc=com> 515bf1c0 conn=1003 op=2 modifications: 515bf1c0 delete: pwdMinLength 515bf1c0 no values 515bf1c0 add: pwdMinLength 515bf1c0 one value, length 1 515bf1c0 conn=1003 op=2 MOD dn="cn=default,ou=policies,dc=example,dc=com" 515bf1c0 conn=1003 op=2 MOD attr=pwdMinLength pwdMinLength 515bf1c0 bdb_dn2entry("cn=default,ou=policies,dc=example,dc=com") 515bf1c0 => bdb_entry_get: ndn: "cn=default,ou=policies,dc=example,dc=com" 515bf1c0 => bdb_entry_get: oc: "(null)", at: "(null)" 515bf1c0 bdb_dn2entry("cn=default,ou=policies,dc=example,dc=com") 515bf1c0 => bdb_entry_get: found entry: "cn=default,ou=policies,dc=example,dc=com" 515bf1c0 bdb_entry_get: rc=0 515bf1c0 => bdb_entry_get: ndn: "cn=default,ou=policies,dc=example,dc=com" 515bf1c0 => bdb_entry_get: oc: "(null)", at: "(null)" 515bf1c0 bdb_dn2entry("cn=default,ou=policies,dc=example,dc=com") 515bf1c0 => bdb_entry_get: found entry: "cn=default,ou=policies,dc=example,dc=com" 515bf1c0 bdb_entry_get: rc=0 515bf1c0 ppolicy_get: using default policy 515bf1c0 hdb_modify: cn=default,ou=policies,dc=example,dc=com 515bf1c0 slap_queue_csn: queing 0x7f460d036240 20130403090920.048272Z#000000#000#000000 515bf1c0 hdb_modify: txn1 id: 80000006 515bf1c0 bdb_dn2entry("cn=default,ou=policies,dc=example,dc=com") 515bf1c0 hdb_modify: txn2 id: 80000007 515bf1c0 bdb_modify_internal: 0x000004b5: cn=default,ou=policies,dc=example,dc=com 515bf1c0 <= acl_access_allowed: granted to database root 515bf1c0 bdb_modify_internal: delete pwdMinLength 515bf1c0 bdb_modify_internal: add pwdMinLength 515bf1c0 bdb_modify_internal: replace entryCSN 515bf1c0 bdb_modify_internal: replace modifiersName 515bf1c0 bdb_modify_internal: replace modifyTimestamp 515bf1c0 oc_check_required entry (cn=default,ou=policies,dc=example,dc=com), objectClass "pwdPolicy" 515bf1c0 oc_check_required entry (cn=default,ou=policies,dc=example,dc=com), objectClass "person" 515bf1c0 oc_check_required entry (cn=default,ou=policies,dc=example,dc=com), objectClass "pwdPolicyChecker" 515bf1c0 oc_check_allowed type "cn" 515bf1c0 oc_check_allowed type "objectClass" 515bf1c0 oc_check_allowed type "pwdAttribute" 515bf1c0 oc_check_allowed type "pwdExpireWarning" 515bf1c0 oc_check_allowed type "pwdInHistory" 515bf1c0 oc_check_allowed type "pwdMustChange" 515bf1c0 oc_check_allowed type "pwdSafeModify" 515bf1c0 oc_check_allowed type "structuralObjectClass" 515bf1c0 oc_check_allowed type "entryUUID" 515bf1c0 oc_check_allowed type "creatorsName" 515bf1c0 oc_check_allowed type "createTimestamp" 515bf1c0 oc_check_allowed type "pwdAllowUserChange" 515bf1c0 oc_check_allowed type "pwdLockout" 515bf1c0 oc_check_allowed type "pwdLockoutDuration" 515bf1c0 oc_check_allowed type "pwdMaxFailure" 515bf1c0 oc_check_allowed type "pwdMaxAge" 515bf1c0 oc_check_allowed type "pwdCheckQuality" 515bf1c0 oc_check_allowed type "pwdMinLength" 515bf1c0 oc_check_allowed type "entryCSN" 515bf1c0 oc_check_allowed type "modifiersName" 515bf1c0 oc_check_allowed type "modifyTimestamp" 515bf1c0 => entry_encode(0x000004b5): 515bf1c0 <= entry_encode(0x000004b5): 515bf1c0 daemon: activity on 1 descriptor 515bf1c0 daemon: activity on:515bf1c0 515bf1c0 daemon: epoll: listen=7 active_threads=0 tvp=zero 515bf1c0 daemon: epoll: listen=8 active_threads=0 tvp=zero and hangs ;/

1 0

Re: (ITS#7559) error in configuring openldap
by quanah＠zimbra.com 02 Apr '13

02 Apr '13

--On Wednesday, April 03, 2013 12:07 AM +0000 amanbista(a)gmail.com wrote: > Full_Name: amanbista > Version: 2.4.34 > OS: redhat linux 6.4 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (70.122.251.187) Please stop filing ITSes. Please use the mailing list as you have already been advised. These are not bug reports. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7559) error in configuring openldap
by amanbista＠gmail.com 02 Apr '13

02 Apr '13

Full_Name: amanbista Version: 2.4.34 OS: redhat linux 6.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (70.122.251.187) i configured a new openldap server and this is the slapd.conf that i used, but i am getting error when i execute slaptest . can you please review this slapd.conf and let me know if there is an issue ? also can you provide the required documentation for creating this file ? # # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # include %SYSCONFDIR%/schema/core.schema # Define global ACLs to disable default read access. # Do not enable referrals until AFTER you have a working directory # service AND an understanding of referrals. #referral ldap://root.openldap.org pidfile %LOCALSTATEDIR%/run/slapd.pid argsfile %LOCALSTATEDIR%/run/slapd.args # Load dynamic backend modules: # modulepath %MODULEDIR% # moduleload back_bdb.la # moduleload back_hdb.la # moduleload back_ldap.la # Sample security restrictions # Require integrity protection (prevent hijacking) # Require 112-bit (3DES or better) encryption for updates # Require 63-bit encryption for simple bind # security ssf=1 update_ssf=112 simple_bind=64 # Sample access control policy: # Root DSE: allow anyone to read it # Subschema (sub)entry DSE: allow anyone to read it # Other DSEs: # Allow self write access # Allow authenticated users read access # Allow anonymous users to authenticate # Directives needed to implement policy: # access to dn.base="" by * read # access to dn.base="cn=Subschema" by * read # access to * # by self write # by users read # by anonymous auth # # if no access controls are present, the default policy # allows anyone and everyone to read anything but restricts # updates to rootdn. (e.g., "access to * by * read") # # rootdn can always read and write EVERYTHING! ####################################################################### # BDB database definitions ####################################################################### database bdb suffix "dc=stjoe,dc=org" rootdn "cn=Manager,dc=stjoe,dc=org" # Cleartext passwords, especially for the rootdn, should # be avoid. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. rootpw {SSHA}BcjI7JYzETfKUEYSnrOn7EVPHcF7BhAK # The database directory MUST exist prior to running slapd AND # should only be accessible by the slapd and slap tools. # Mode 700 recommended. directory %LOCALSTATEDIR%/openldap-data # Indices to maintain index objectClass eq

1 0

Re: (ITS#7558) error in configuring openldap
by quanah＠zimbra.com 02 Apr '13

02 Apr '13

--On Tuesday, April 02, 2013 11:48 PM +0000 amanbista(a)gmail.com wrote: > [root@scrdcvcortst05 openldap]# ldapsearch > SASL/GSSAPI authentication started > ldap_sasl_interactive_bind_s: Local error (-2) > additional info: SASL(-1): generic failure: GSSAPI Error: > Unspecified GSS failure. Minor code may provide more information > (Credentials cache file '/tmp/krb5cc_0' not found) The ITS system is for reporting bugs. You have failed to show the existence of any bug here. Again, please go read the manual pages on how to use ldapsearch. If you are not able to comprehend them, then use the openldap-technical(a)openldap.org list to ask for assistance. This ITS will be closed. Please stop filing new ones until you have an actual bug to report. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7558) error in configuring openldap
by amanbista＠gmail.com 02 Apr '13

02 Apr '13

Full_Name: amanbista Version: 2.4.34 OS: redhat linux 6.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (70.122.251.187) root@scrdcvcortst05 openldap]# slaptest bdb_db_open: warning - no DB_CONFIG file found in directory /var/lib/ldap: (2). Expect poor performance for suffix "dc=my-domain,dc=com". config file testing succeeded [root@scrdcvcortst05 openldap]# ldapsearch SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Credentials cache file '/tmp/krb5cc_0' not found)

1 0

Re: (ITS#7557) error in configuring openldap
by quanah＠zimbra.com 02 Apr '13

02 Apr '13

--On Tuesday, April 02, 2013 10:48 PM +0000 amanbista(a)gmail.com wrote: > Full_Name: amanbista > Version: 2.3.34 > OS: redhat linux 6.4 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (70.122.251.187) I suggest you read the manual page for ldapsearch so you understand how it works. I would also note that the OpenLDAP 2.3 series has not been supported for years. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7557) error in configuring openldap
by amanbista＠gmail.com 02 Apr '13

02 Apr '13

Full_Name: amanbista Version: 2.3.34 OS: redhat linux 6.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (70.122.251.187) root@scrdcvcortst05 openldap]# slaptest bdb_db_open: warning - no DB_CONFIG file found in directory /var/lib/ldap: (2). Expect poor performance for suffix "dc=my-domain,dc=com". config file testing succeeded [root@scrdcvcortst05 openldap]# ldapsearch SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Credentials cache file '/tmp/krb5cc_0' not found)

1 0

Re: (ITS#7556) MDB_PREV skipping large chunks of databse
by dw＠botanicus.net 01 Apr '13

01 Apr '13

--089e0122814257375004d955a1e6 Content-Type: text/plain; charset=ISO-8859-1 It's worth note this was found after applying Howard's most recent patch for my previous MDB_LAST issue. Sorry for being a pain. :) --089e0122814257375004d955a1e6 Content-Type: text/html; charset=ISO-8859-1 <div dir="ltr">It's worth note this was found after applying Howard's most recent patch for my previous MDB_LAST issue. Sorry for being a pain. :)<br></div> --089e0122814257375004d955a1e6--

1 0

(ITS#7556) MDB_PREV skipping large chunks of databse
by dw＠botanicus.net 01 Apr '13

01 Apr '13

Full_Name: David Wilson Version: MDB 7aae15739b2c77bb601c98b112c804f51778a33b OS: OS X URL: http://codepad.org/KCeSzRr6 Submission from: (NULL) (92.41.251.234) Per demo at http://codepad.org/KCeSzRr6 , something seems to be broken with reverse cursor iteration. Iteration mostly succeeds before skipping most of the middle of the database and continuing with the starting keys (as best I can read it).

1 0

Re: (ITS#7555) SizeLimit Exceeded Error
by masarati＠aero.polimi.it 01 Apr '13

01 Apr '13

> Full_Name: sandeep kumawat > Version: 2.4 > OS: Cent OS 5.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (103.245.47.20) > > > When doing a page search for user on ldap, SizeLimit Exceeded Error is > thrown. > > There are about 1500 users in ldap and we are using ldap_search_init_page > API > with 10th param (TotalSizeLimit) set to 500. > > Could you pls let us know what can be issue here. The ITS is to notify bugs in OpenLDAP software. There is no ldap_search_init_page() in OpenLDAP's API. The answer to your question is in slapd.conf(5) in the discussion of the "limits" parameter. This ITS will be closed. -- Pierangelo Masarati Associate Professor Dipartimento di Scienze e Tecnologie Aerospaziali Politecnico di Milano

1 0

(ITS#7555) SizeLimit Exceeded Error
by sandeep_kumawat＠mcafee.com 01 Apr '13

01 Apr '13

Full_Name: sandeep kumawat Version: 2.4 OS: Cent OS 5.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (103.245.47.20) When doing a page search for user on ldap, SizeLimit Exceeded Error is thrown. There are about 1500 users in ldap and we are using ldap_search_init_page API with 10th param (TotalSizeLimit) set to 500. Could you pls let us know what can be issue here. Thanks

1 0

Re: (ITS#7531) Syncrepl push delete operation does not recover when slave is unavailable
by quanah＠zimbra.com 27 Mar '13

27 Mar '13

--On Wednesday, March 27, 2013 8:42 AM +0000 hans.moser(a)ofd-z.niedersachsen.de wrote: >> Sorry, I was in test054, not test045. But as base 054 seems to be just >> fine. I hope, I did the patch right. > Hm, I was not included. :( > Is there something wrong with the patch? Hi Marc, Simply an oversight, sorry. I've patched test054 with your bits on my local install, on a 2.4.34 build without the fix for ITS#7531, and it passes for me. I would assume since I haven't patched 2.4.34 for the fix, it should fail? I.e., it seems this patch doesn't actually catch the problem. :/ --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7531) Syncrepl push delete operation does not recover when slave is unavailable
by hans.moser＠ofd-z.niedersachsen.de 27 Mar '13

27 Mar '13

Hi, hans.moser(a)ofd-z.niedersachsen.de schrieb (14.03.2013 17:22 Uhr): > hyc(a)symas.com schrieb (14.03.2013 16:24 Uhr): >> Marc Patermann wrote: >>> hyc(a)symas.com schrieb (14.03.2013 15:14 Uhr): >>>> hans.moser(a)ofd-z.niedersachsen.de wrote: >>>>> I think we had situations like this before... >>>>> >>>>> How about having a test for this? >>>>> What is the test which is nearest to this situation where a test could >>>>> be based on? >>>> test045. Feel free to submit patches for this test script. >>> If I'm not mistaken, >>> - in lines 262-264 the consumer is stopped >>> - in lines 266-284 changes are made to the provider >>> - in lines 286-294 the consumer is started again. >> Sounds reasonable but your line numbers don't match anything in our tree. >> Please send an actual patch, e.g. from git format-patch (or just diff -u.) > Sorry, I was in test054, not test045. But as base 054 seems to be just fine. > I hope, I did the patch right. Hm, I was not included. :( Is there something wrong with the patch? Marc

1 0

RE: (ITS#7545) Problem with v2.4.30
by quanah＠zimbra.com 26 Mar '13

26 Mar '13

--On Tuesday, March 26, 2013 7:45 PM +0000 "Swenson_CNTR, Carl E." <Carl.Swenson(a)dodiis.mil> wrote: > All, > > Thank you for the replies. Yes, Oracle makes the hardware, but as you > may have experienced when dealing with Oracle, if there is anything on > the server that is not "Oracle", then the problem must be with that > software. (This is the response you will get from Oracle on just about > anything). BDB is owned by Oracle, so they should be able to help you with it. The creation of the BDB log files is *purely* a function internal to BDB. The fact that they are exploding would be a function of BDB. That is why I've repeatedly said there is no indication of an OpenLDAP bug here. That is why Howard directed you to Oracle. They are the ones who own BDB, they should be able to provide you insight into why it has broken on your new server. BDB logs are created when changes are made to the database. If you see your logs "exploding" without corresponding massive changes being made to the OpenLDAP server, then you are essentially ensured that the issue is with BDB. I would also suggest you run the db_archive utility to see what log(s) it says can or can't be archived. It is possible that BDB is holding open a write or read transaction for some reason (again, a BDB bug). As for MDB, it is a new database written by Howard Chu, the primary OpenLDAP Developer. You can read up on it at <http://symas.com/mdb/>. It is significantly better than BDB in numerous ways. I disagree with your assessment on the recent change log as well. It is almost all entirely around mdb. OpenLDAP 2.4.34 Release (2013/03/03) Fixed liblmdb mdb_env_open flag handling (ITS#7453) Fixed liblmdb mdb_midl_sort array optimization (ITS#7432) Fixed liblmdb freelist with large entries (ITS#7455) Fixed liblmdb to check for filled dirty page list (ITS#7491) Fixed liblmdb to validate data limits (ITS#7485) Fixed liblmdb mdb_update_key for large keys (ITS#7505) Fixed slapd-mdb to reopen attr DBs after env reopen (ITS#7416) Fixed slapd-mdb handling of missing entries (ITS#7483,7496) Fixed slapd-mdb environment flag setting (ITS#7452) Fixed slapd-mdb with sub db slapcat (ITS#7469) Fixed slapd-mdb to correctly work with toolthreads > 2 (ITS#7488,ITS#7527) Fixed slapd-mdb subtree search speed (ITS#7473) I see zero changes in 2.4.34 related to BDB at all. OpenLDAP 2.4.33 Release (2012/10/10) Fixed liblmdb POSIX semaphore cleanup on environment close (ITS#7364) Fixed liblmdb mdb_page_split (ITS#7385, ITS#7229) Fixed slapd-mdb slapadd -q -w double free (ITS#7356) Fixed slapd-mdb to close read txn in reindex commit (ITS#7386) Again, no changes related to BDB. The last release with any fixes specific to BDB was 2.4.32. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

RE: (ITS#7545) Problem with v2.4.30
by Carl.Swenson＠dodiis.mil 26 Mar '13

26 Mar '13

All, Thank you for the replies. Yes, Oracle makes the hardware, but as you may have experienced when dealing with Oracle, if there is anything on the server that is not "Oracle", then the problem must be with that software. (This is the response you will get from Oracle on just about anything). We have many security layers, and an "isolated network" that has zero chance of getting to the internet / outside world that is of very little risk from malware. It is true we have never had to compile the packages being used so the install defaults referred to BDB, and that is what we used. I realize BDB 4.7.25.NC may not be the "bleeding edge" but it is the release referred to on sunfreeware.com (they have v2.4.32 packaged for download), and when you look on OpenLDAP's web site there are references to get the compiled packages from sunfreeware.com. I see on Oracle's web site there is a v5.3 download that can try. As far as "mdb" goes, we don't know what that is, and most references even in the v2.4.34 download talk about BDB. The purpose we use OpenLDAP for is a very simple authentication with WebLogic. Nothing heavy duty. I agree there could be some "strangeness" when mixing these packages with a new T4, but it is still unknown. Quanah, "There certainly isn't enough detail in your report to really offer you any particular direction to pursue." What is it that would be useful, if I can capture it, and "secure" transfer it then I will. But I can't get most detail reports through security de-class scan to be able to post it. Carl =========== Well... Oracle now owns your hardware manufacturer and the software in question. They'd be the obvious place to ask for help. Frankly I'm surprised that a military site on a classified network is allowed to install freeware binaries from any internet site. You have no idea how those binaries were built, and certainly no recourse if they fail in any way or happen to have trojans/malware embedded within. My first step would be to compile current source code. If the behavior still exists on current code, then start debugging/diagnosing. BDB 4.7.25 is quite old, as Quanah already pointed out. We've never seen any other cases reported like this, but it's always possible for a mixture of old binaries and new hardware to go bad. For all you know it's an instruction set incompatibility and recompiling BDB for your T4 will make it go away. > > > Carl > > > -----Original Message----- > From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] > Sent: Wednesday, March 20, 2013 2:20 PM > To: Swenson_CNTR, Carl E.; openldap-its(a)openldap.org > Subject: RE: (ITS#7545) Problem with v2.4.30 > > --On Tuesday, March 19, 2013 8:57 PM +0000 "Swenson_CNTR, Carl E." > <Carl.Swenson(a)dodiis.mil> wrote: > >> Quanah, >> >> Thank you for the reply. >> >> I double checked my versions on some of my systems just to be sure. >> One inconsistency I noticed was in the name of the DB package >> Possibly downloaded at 2 different times from sunfreeware.com. >> >> Example - >> Sun Enterprise SPARC T5220 (everything works on this system) pkginfo >> -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c >> pkginfo -l SMCdb - version 4.7.25.NC >> >> Sun Enterprise SPARC T4-1 (the logs go crazy on this system) pkginfo >> -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c >> pkginfo -l SMCdb47 - version 4.7.25.NC >> >> IDK how this would affect the system, but based on your suggestion >> there is some difference in the package as the "pkginst" name on one >> system is SMCdb, and SMCdb47 on the other while the version is exactly the same. > > I have no idea. I abandoned Slowaris years ago... I abandoned using BDB with OpenLDAP last year. However, no one has reported any issues like this. It really appears to be a bug in BDB rather than OpenLDAP however. > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > > > -- -- Howard Chu CTO, 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#7545) Problem with v2.4.30
by hyc＠symas.com 26 Mar '13

26 Mar '13

Carl.Swenson(a)dodiis.mil wrote: > Quanah, > > Fine, I get it, you hate Solaris, BDB, etc...... But this is what I have > to work with, and I still have an issue that I have never heard of, nor do I know what to even look for. Google searches turn up very little. > > Is there an "OpenLDAP forum" where you can get help? I have tried removing the package labeled SMCdb47, and loaded SMCdb. The result is still the same. I know you don't like BDB, (you didn't mention what you do prefer) but in any case we are approved to use OpenLDAP w/ BDB. Normally we download all the supporting packages from sunfreeware.com, and if I remember correctly, it is defaulted to use BDB. > > So I have to use: > Solaris 10 > BDB 4.7.25.NC > OpenSSL 1.0.1c > OpenLDAP 2.4.30 > > What can I do. I have configured hundreds of servers using these packages, and their predecessors. We have never seen this behavior. Well... Oracle now owns your hardware manufacturer and the software in question. They'd be the obvious place to ask for help. Frankly I'm surprised that a military site on a classified network is allowed to install freeware binaries from any internet site. You have no idea how those binaries were built, and certainly no recourse if they fail in any way or happen to have trojans/malware embedded within. My first step would be to compile current source code. If the behavior still exists on current code, then start debugging/diagnosing. BDB 4.7.25 is quite old, as Quanah already pointed out. We've never seen any other cases reported like this, but it's always possible for a mixture of old binaries and new hardware to go bad. For all you know it's an instruction set incompatibility and recompiling BDB for your T4 will make it go away. > > > Carl > > > -----Original Message----- > From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] > Sent: Wednesday, March 20, 2013 2:20 PM > To: Swenson_CNTR, Carl E.; openldap-its(a)openldap.org > Subject: RE: (ITS#7545) Problem with v2.4.30 > > --On Tuesday, March 19, 2013 8:57 PM +0000 "Swenson_CNTR, Carl E." > <Carl.Swenson(a)dodiis.mil> wrote: > >> Quanah, >> >> Thank you for the reply. >> >> I double checked my versions on some of my systems just to be sure. >> One inconsistency I noticed was in the name of the DB package >> Possibly downloaded at 2 different times from sunfreeware.com. >> >> Example - >> Sun Enterprise SPARC T5220 (everything works on this system) pkginfo >> -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c >> pkginfo -l SMCdb - version 4.7.25.NC >> >> Sun Enterprise SPARC T4-1 (the logs go crazy on this system) pkginfo >> -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c >> pkginfo -l SMCdb47 - version 4.7.25.NC >> >> IDK how this would affect the system, but based on your suggestion >> there is some difference in the package as the "pkginst" name on one >> system is SMCdb, and SMCdb47 on the other while the version is exactly the same. > > I have no idea. I abandoned Slowaris years ago... I abandoned using BDB with OpenLDAP last year. However, no one has reported any issues like this. It really appears to be a bug in BDB rather than OpenLDAP however. > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > > > -- -- Howard Chu CTO, 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#7545) Problem with v2.4.30
by quanah＠zimbra.com 26 Mar '13

26 Mar '13

--On Tuesday, March 26, 2013 6:09 PM +0000 "Swenson_CNTR, Carl E." <Carl.Swenson(a)dodiis.mil> wrote: > Quanah, > > Fine, I get it, you hate Solaris, BDB, etc...... But this is what I have > to work with, and I still have an issue that I have never heard of, nor > do I know what to even look for. Google searches turn up very little. > > Is there an "OpenLDAP forum" where you can get help? I have tried > removing the package labeled SMCdb47, and loaded SMCdb. The result is > still the same. I know you don't like BDB, (you didn't mention what you > do prefer) but in any case we are approved to use OpenLDAP w/ BDB. > Normally we download all the supporting packages from sunfreeware.com, > and if I remember correctly, it is defaulted to use BDB. As I initially stated, there is nothing in your bug report to indicate a bug with OpenLDAP. I would note that BDB 4.7.25 is ancient. I would note that OpenLDAP 2.4.30 is fairly old. Who knows how OpenLDAP or BDB was built with those packages you are using. There certainly isn't enough detail in your report to really offer you any particular direction to pursue. If it was *me*, I would build the latest OpenLDAP with a current version of BDB, where I could control the compile options and flags. By the way, BDB support in OpenLDAP is essentially deprecated. All ongoing development is with the new MDB backend. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

RE: (ITS#7545) Problem with v2.4.30
by Carl.Swenson＠dodiis.mil 26 Mar '13

26 Mar '13

Quanah, Fine, I get it, you hate Solaris, BDB, etc...... But this is what I have to work with, and I still have an issue that I have never heard of, nor do I know what to even look for. Google searches turn up very little. Is there an "OpenLDAP forum" where you can get help? I have tried removing the package labeled SMCdb47, and loaded SMCdb. The result is still the same. I know you don't like BDB, (you didn't mention what you do prefer) but in any case we are approved to use OpenLDAP w/ BDB. Normally we download all the supporting packages from sunfreeware.com, and if I remember correctly, it is defaulted to use BDB. So I have to use: Solaris 10 BDB 4.7.25.NC OpenSSL 1.0.1c OpenLDAP 2.4.30 What can I do. I have configured hundreds of servers using these packages, and their predecessors. We have never seen this behavior. Carl -----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Wednesday, March 20, 2013 2:20 PM To: Swenson_CNTR, Carl E.; openldap-its(a)openldap.org Subject: RE: (ITS#7545) Problem with v2.4.30 --On Tuesday, March 19, 2013 8:57 PM +0000 "Swenson_CNTR, Carl E." <Carl.Swenson(a)dodiis.mil> wrote: > Quanah, > > Thank you for the reply. > > I double checked my versions on some of my systems just to be sure. > One inconsistency I noticed was in the name of the DB package > Possibly downloaded at 2 different times from sunfreeware.com. > > Example - > Sun Enterprise SPARC T5220 (everything works on this system) pkginfo > -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c > pkginfo -l SMCdb - version 4.7.25.NC > > Sun Enterprise SPARC T4-1 (the logs go crazy on this system) pkginfo > -l SMColdap - version 2.4.30 pkginfo -l SMCossl - version 1.0.1c > pkginfo -l SMCdb47 - version 4.7.25.NC > > IDK how this would affect the system, but based on your suggestion > there is some difference in the package as the "pkginst" name on one > system is SMCdb, and SMCdb47 on the other while the version is exactly the same. I have no idea. I abandoned Slowaris years ago... I abandoned using BDB with OpenLDAP last year. However, no one has reported any issues like this. It really appears to be a bug in BDB rather than OpenLDAP however. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7554) mdb_cursor_put() flag combinations broken
by hyc＠symas.com 25 Mar '13

25 Mar '13

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: mdb.master bbb27cde4af7 > OS: > URL: > Submission from: (NULL) (193.69.163.163) > Submitted by: hallvard > > > mdb_cursor_put() and mdb_cursor_del() sometimes tests the > flags argument with '==' or '!=' instead of '&'. That breaks > flag combinations like MDB_CURRENT | MDB_RESERVE: The cursor_put flags are not combinable. The doc already says only one value may be set. Closing this ITS. > > grep -n 'flags [!=]= MDB_' mdb.c > 4884: if (flags != MDB_CURRENT && (key->mv_size == 0 || key->mv_size > > MDB_MAXKEYSIZE)) > 4900: if (flags == MDB_CURRENT) { > 4962: if (flags == MDB_CURRENT) { > 4977: if (flags == MDB_CURRENT) > 4992: return (flags == MDB_NODUPDATA) ? MDB_KEYEXIST : MDB_SUCCESS; > 5025: if (flags == MDB_CURRENT) { > 5274: if (flags != MDB_NODUPDATA) { > > The mdb_cursor_del() test is not a problem yet since only > one flag is valid, but it'll become broken if more flags > get supported. > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs