October 2019 - openldap-bugs

Re: (ITS#9096) tons of crashing and core dumps after every boot

by hyc＠symas.com

priit(a)ww.ee wrote: > Full_Name: Priit Oorn > Version: no idea > OS: Manjaro KDE stable > URL: https://bugsfiles.kde.org/attachment.cgi?id=123175 > Submission from: (NULL) (2001:7d0:8240:e600:7a6:c9cf:974a:2e6e) > > > STEPS TO REPRODUCE > 1. reboot system > 2. journalctl -p3 > > OBSERVED RESULT > KDE baloo_file and baloo_file_extr serial crashing due to LMDB crashing. > > EXPECTED RESULT > no services crashing obviously. > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Manjaro Linux KDE stable > KDE Plasma Version: 5.16.5 > KDE Frameworks Version: 5.62.0 > Qt Version: 5.13.1 > LBDM version: no idea... that comes with Manjaro KDE stable default install + > all updates. the crashing thing has been there forever though over several > versions. > > reported the bug to KDE initially, but they say it's your fault... :P > https://bugs.kde.org/show_bug.cgi?id=412925 The stack traces you provided there https://bugsfiles.kde.org/attachment.cgi?id=123175 would indicate a crash in LMDB, but without providing version info we have nothing to go on. Nor do we have any insight into how KDE integrated LMDB and whether they used its API correctly. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

4 years, 1 month

1
0
0 / 0

(ITS#9096) tons of crashing and core dumps after every boot

by priit＠ww.ee

Full_Name: Priit Oorn Version: no idea OS: Manjaro KDE stable URL: https://bugsfiles.kde.org/attachment.cgi?id=123175 Submission from: (NULL) (2001:7d0:8240:e600:7a6:c9cf:974a:2e6e) STEPS TO REPRODUCE 1. reboot system 2. journalctl -p3 OBSERVED RESULT KDE baloo_file and baloo_file_extr serial crashing due to LMDB crashing. EXPECTED RESULT no services crashing obviously. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE stable KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 LBDM version: no idea... that comes with Manjaro KDE stable default install + all updates. the crashing thing has been there forever though over several versions. reported the bug to KDE initially, but they say it's your fault... :P https://bugs.kde.org/show_bug.cgi?id=412925

4 years, 1 month

1
0
0 / 0

Re: (ITS#9018) dynlist don't close connection

by quanah＠symas.com

Decoded we have: "I have changed back-meta to the back-ldap, and it resolved this problem." --On Tuesday, September 24, 2019 11:59 AM +0000 I.Harbuz(a)A1.by wrote: -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

4 years, 1 month

1
0
0 / 0

(ITS#9095) back-mdb slapindex missing records

by hyc＠openldap.org

Full_Name: Howard Chu Version: 2.4 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.203.26.174) Submitted by: hyc In back-mdb the entry reindexer operates in batches of 500 entries at a time. (I.e., it commits one LMDB txn for every 500 entries.) But a final txn_commit is missing in tool_entry_close() to flush out the last few entries that were operated on.

4 years, 1 month

1
0
0 / 0

Re: (ITS#9092) LDAP server out of memory

by quanah＠symas.com

--On Wednesday, October 9, 2019 9:38 AM +0000 gihanridal8(a)gmail.com wrote: > Full_Name: Gihan De Silva > Version: 2.4.44 > OS: 7.5 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (123.231.119.138) Hello, The OpenLDAP bug tracking system is for bug reports only. Usage questions should be directed to the OpenLDAP Technical discussion list: <https://www.openldap.org/lists/mm/listinfo/openldap-technical> If you have an urgent support need, then I suggest contacting one of the listed 3rd party support providers at: <https://www.openldap.org/support/> This ITS will be closed. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

4 years, 1 month

1
0
0 / 0

RE: (ITS#9088) Concurrency not seen in OpenLDAP 2.4.44

by jrajalakshmi＠juniper.net

SGksDQpXZSB3aWxsIHNlbmQgdGhlIHNhbXBsZSBjb2RlIHNob3J0bHkuDQoNClRoYW5rcywNClJh amkNCg0KDQpKdW5pcGVyIEJ1c2luZXNzIFVzZSBPbmx5DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn ZS0tLS0tDQpGcm9tOiBPbmTFmWVqIEt1em7DrWsgPG9uZHJhQG1pc3RvdGViZS5uZXQ+IA0KU2Vu dDogVHVlc2RheSwgT2N0b2JlciA4LCAyMDE5IDEwOjQ1IFBNDQpUbzogUmFqYWxha3NobWkgSmF5 YXJhbWFuIDxqcmFqYWxha3NobWlAanVuaXBlci5uZXQ+DQpDYzogb3BlbmxkYXAtaXRzQE9wZW5M REFQLm9yZw0KU3ViamVjdDogUmU6IChJVFMjOTA4OCkgQ29uY3VycmVuY3kgbm90IHNlZW4gaW4g T3BlbkxEQVAgMi40LjQ0DQoNCk9uIFR1ZSwgT2N0IDA4LCAyMDE5IGF0IDEyOjU2OjA0UE0gKzAw MDAsIGpyYWphbGFrc2htaUBqdW5pcGVyLm5ldCB3cm90ZToNCj4gSGksDQo+IA0KPiBUaGFua3Mg Zm9yIHRoZSByZXBseS4gVGhlcmUgaXMgYW4gaW1wbGVtZW50YXRpb24gYWxyZWFkeSBpbiBvdXIg cHJvZHVjdC4NCg0KSGksDQphcyBtZW50aW9uZWQgcHJldmlvdXNseSwgcGxlYXNlIHByb3ZpZGUg YSBzYW1wbGUgQyBwcm9ncmFtIHRoYXQgc2hvd3Mgd2hhdCdzIGhhcHBlbmluZyBhbmQgcHJlZmVy YWJseSBvbmUgdGhhdCBhbHNvIGJlaGF2ZXMgYmV0dGVyIHdpdGggMi40LjIzIGZyb20geW91ciBw ZXJzcGVjdGl2ZSBzbyB3ZSBjYW4gaGVscCB5b3UgaW52ZXN0aWdhdGUuIEkgZG9uJ3QgYmVsaWV2 ZSBwYWNrZXQgY2FwdHVyZXMgd291bGQgaGVscCB1cyBoZXJlIGF0IHRoaXMgcG9pbnQuDQoNCj4g VG8gc3VtbWFyaXplIG9uIHRoZSBiZWhhdmlvciBvYnNlcnZlZA0KPiANCj4gU2NlbmFyaW8jMToN Cj4gDQo+IFNpbmdsZSBMREFQIHNlc3Npb24gd2l0aCBMREFQIEJpbmQgZG9lcyBhdXRoZW50aWNh dGlvbiBpbiBTZXF1ZW50aWFsIA0KPiBPcmRlci4gRHVlIHRvIHNlcXVlbnRpYWwgZXhlY3V0aW9u IG9mIE9wZW5MREFQIFNlYXJjaCBBUEkgYWZ0ZXIgDQo+IHZlcnNpb24gMi40LjI0IHdlIG9ic2Vy dmUgcGFja2V0IGRyb3BzIGluIExEQVAgQXV0aGVudGljYXRpb24gUmVxdWVzdC4NCj4gVGhpcyBp cyByZXN1bHRpbmcgaW4gTG93IHBlcmZvcm1hbmNlIG9mIG91ciBwcm9kdWN0Lg0KDQpQcmV2aW91 c2x5IHlvdSBtZW50aW9uZWQgb25seSBzZWFyY2hlcywgd2hpY2ggc2hvdWxkIHdvcmsgb3ZlciB0 aGUgc2FtZSBjb25uZWN0aW9uIGRlcGVuZGluZyBob3cgeW91IGRvIHRoaW5ncy4gTm90IHN1cmUg aG93IGJpbmRzIGZpdCBpbiB0aGUgcGljdHVyZSBoZXJlPyBKdXN0IGEgbm90ZSB0aGF0IHlvdSBj YW4gb25seSBoYXZlIGNlcnRhaW4gdHlwZXMgb2Ygb3BlcmF0aW9ucyBwZW5kaW5nIGF0IHRoZSBz YW1lIHRpbWUgYW5kIGJpbmRzIGFyZSBub3Qgb25lIG9mIHRoZW0uDQoNCkFsc28gZG9uJ3Qga25v dyB3aGF0IHlvdSBtZWFuIGJ5IHBhY2tldCBkcm9wcyBoZXJlLiBJcyB0aGF0IHBhY2tldCBkcm9w cyBpbiB5b3VyIHByb2R1Y3Qgb3IgcGFja2V0IGRyb3BzIG9uIHRoZSBMREFQIHNlc3Npb24/DQoN Cj4gU2NlbmFyaW8gIzI6ICh0aGlzIGlzIGEgc2FtcGxlIHRlc3QgY2FzZSB0cmllZCB0byBjb21w YXJlIHRoZSBiZWhhdmlvciANCj4gd2l0aCBTY2VuYXJpbyMxKQ0KPiANCj4gVGhlcmUgYXJlIHNh eSAxMCBMREFQIGluc3RhbmNlcyBjb25maWd1cmVkLCBhbGwgcG9pbnRpbmcgdG8gdGhlIHNhbWUg DQo+IExEQVAgc2VydmVyLiBUaGUgcmVxdWVzdC1yZXNwb25zZSBpcyBoYW5kbGVkIHByb3Blcmx5 LCBwZXJmb3JtYW5jZSBpcyANCj4gaW1wcm92ZWQgd2hlbiBjb21wYXJlZCB0byBzY2VuYXJpbyMx LiBCdXQgdGhlIGRyYXdiYWNrIGlzIHRoZSBtdWx0aXBsZSANCj4gdGhyZWFkcyBmb3IgZXZlcnkg TERBUCBjbGllbnQgc2Vzc2lvbiwgdXRpbGl6aW5nIG1vcmUgbWVtb3J5LiBUaGlzIA0KPiBkZXNp Z24gbWF5IG5vdCBiZSByZWNvbW1lbmRlZCBmb3Igb3VyIHByb2R1Y3QuDQoNCllvdSBjYW4gaGF2 ZSBhIHNpbmdsZSB0aHJlYWQgdGFraW5nIGNhcmUgb2YgdGhlIHNlc3Npb24gKG9yIGhvd2V2ZXIg bWFueSBzZXNzaW9ucyB5b3Ugd2FudCkgaWYgeW91IHVzZSBhIG5vbi1ibG9ja2luZyBzb2NrZXQg Zm9yIHRoZSB1bmRlcmx5aW5nDQpjb25uZWN0aW9uKHMpIChhbmQgdXNlIGxkYXBfcmVzdWx0IGFu ZCBmcmllbmRzKSB3aGljaCBpcyB3aGF0IHRoZSBhc3luY2hyb25vdXMgQVBJIGhhcyBiZWVuIGRl c2lnbmVkIGZvci4NCg0KPiBQbC4gcmVwbHkgYmFjayBmb3IgYW55IGZ1cnRoZXIgcXVlcmllcyAv IGNsYXJpZmljYXRpb25zLiBUaGUgcGFja2V0IA0KPiBjYXB0dXJlcyBmaWxlIHNpemUgaXMgYmln ICg+Nk1CKSwgY2FuIHRyeSB0byBzaGFyZSB0aGUgcmVsZXZhbnQgDQo+IHJlcXVlc3QtcmVzcG9u c2UgZGV0YWlscy4uLi4uLg0KDQpSZWdhcmRzLA0KDQotLQ0KT25kxZllaiBLdXpuw61rDQpTZW5p b3IgU29mdHdhcmUgRW5naW5lZXINClN5bWFzIENvcnBvcmF0aW9uICAgICAgICAgICAgICAgICAg ICAgICBodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cDovL3d3dy5zeW1hcy5jb21fXzsh OFdvQTZSakM4MWMhVDNyV05tZTYzRlJFcmJzZ3I4RDVvaV9WVU9HWEY3YVFXSTZFckswMWp0elVM Nm9tcmhXSXFkay1ySDllUGxCald6UXUkIA0KUGFja2FnZWQsIGNlcnRpZmllZCwgYW5kIHN1cHBv cnRlZCBMREFQIHNvbHV0aW9ucyBwb3dlcmVkIGJ5IE9wZW5MREFQDQo=

4 years, 1 month

1
0
0 / 0

(ITS#9094) LDAP server out of memory

by gihanridal8＠gmail.com

Full_Name: Gihan De Silva Version: 2.4.44 OS: 7.5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (123.231.119.138) Dear Sir/ Madam, We are having two OpenLDAP servers on production with master master data synchronization. We are facing an incident where both servers consume memory upto 99% and LDAP server2 leads to not responding state. As a workaround we have restart both OpenLDAP nodes. However after few days the memory goes high at its peak. There are about 100k+ requests for one LDAP server per day. where both servers are identical in terms of 16 GB RAM, 4 CPUs, CentOS7 OS and LDAP server 2.4.44. We didnt observe any suspiciuos errors in the logs as well. Appreciate your valued consultation and recomendations on this incident for a RCA and a solution. Thank You Regards, Gihan.

4 years, 2 months

1
0
0 / 0

(ITS#9093) LDAP server out of memory

by gihanridal8＠gmail.com

Full_Name: Gihan De Silva Version: 2.4.44 OS: 7.5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (123.231.119.138) Dear Sir/ Madam, We are having two OpenLDAP servers on production with master master data synchronization. We are facing an incident where both servers consume memory upto 99% and LDAP server2 leads to not responding state. As a workaround we have restart both OpenLDAP nodes. However after few days the memory goes high at its peak. There are about 100k+ requests for one LDAP server per day. where both servers are identical in terms of 16 GB RAM, 4 CPUs, CentOS7 OS and LDAP server 2.4.44. We didnt observe any suspiciuos errors in the logs as well. Appreciate your valued consultation and recomendations on this incident for a RCA and a solution. Thank You Regards, Gihan.

4 years, 2 months

1
0
0 / 0

(ITS#9092) LDAP server out of memory

by gihanridal8＠gmail.com

Full_Name: Gihan De Silva Version: 2.4.44 OS: 7.5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (123.231.119.138) Dear Sir/ Madam, We are having two OpenLDAP servers on production with master master data synchronization. We are facing an incident where both servers consume memory upto 99% and LDAP server2 leads to not responding state. As a workaround we have restart both OpenLDAP nodes. However after few days the memory goes high at its peak. There are about 100k+ requests for one LDAP server per day. where both servers are identical in terms of 16 GB RAM, 4 CPUs, CentOS7 OS and LDAP server 2.4.44. We didnt observe any suspiciuos errors in the logs as well. Appreciate your valued consultation and recomendations on this incident for a RCA and a solution. Thank You Regards, Gihan.

4 years, 2 months

1
0
0 / 0

(ITS#9091) mdb attribute get mixed up in slapadd continue (-c) mode

by maxime.besson＠worteks.com

Full_Name: Maxime Besson Version: 2.4.48 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (77.193.139.162) I am attempting to implement the following disaster recovery process: * rm all previous data * run a configuration script (puppet) to recreate a bare-bones LDAP server and DIT * restore a backed-up slapcat dump on top of the freshly installed OpenLDAP server, ignoring duplicates already inserted by Puppet But it seems that when skipping over the existing objects, something goes wrong and causes attributes to get mixed up. But only when certain attributes are present in the existing objects. Here is how to reproduce: slapd.conf: === include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/inetorgperson.schema moduleload back_mdb database mdb maxsize 1073741824 suffix "dc=example,dc=com" directory /tmp === puppet_init.ldif === dn: dc=example,dc=com objectClass: domain dc: example === backup.ldif === dn: dc=example,dc=com objectClass: domain dc: example contextCSN: 20190909094705.796552Z#000000#001#000000 dn: uid=ttully,dc=example,dc=com objectClass: inetOrgPerson uid: ttully userPassword:: c2Nob29uZXI= facsimileTelephoneNumber: +1 408 555 0111 givenName: Torrey cn: Torrey Tully telephoneNumber: +1 408 555 2274 sn: Tully roomNumber: 3924 mail: ttully(a)example.com l: Sunnyvale ou: Human Resources ou: People === When running the following commands: === rm -f /tmp/*.mdb slapadd -f slapd.conf puppet_init.ldif slapadd -f slapd.conf -c backup.ldif === The redundant root object in backup.ldif gets skipped as -c should do, but the attributes from my "ttully" user (and every following object in the ldif dump) end up all mixed up: === slapcat -f slapd.conf ... dn: uid=ttully,dc=example,dc=com objectClass: inetOrgPerson userPassword:: dHR1bGx5 facsimileTelephoneNumber: schooner givenName: +1 408 555 0111 cn: Torrey telephoneNumber: Torrey Tully sn: +1 408 555 2274 roomNumber: Tully mail: 3924 l: ttully(a)example.com ou: Sunnyvale ou: Human Resources ou: People ... === This mixup does NOT happen if: * I import backup.ldif into an empty database * OR I remove "contextCSN" from the backup ldif * OR I use BDB instead of MDB So it seems that my issue is caused by a combination of MDB, skipping existing entries, and having special attributes (contextCSN) in the skipped objects. I was able to reproduce this behavior: * On Debian Buster (OpenLDAP 2.4.47) * On RHEL7 + LTB project RPMs 2.4.48 * Using a git snapshot (3be82f40d5cd4ca050e10859ecb961f28c807c41) with no particular config options * Using cn=config rather than slapd.conf * On a real production system, rather than the simplified version presented here. * Using another "special" attribute such as pwdAccountLockedTime instead of "contextCSN"

4 years, 2 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs October 2019