openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#9155) LMDB: List of spill pages leaks after transaction
by hyc＠symas.com 23 Jan '20

23 Jan '20

babayants.alexander(a)gmail.com wrote: > Full_Name: Alexander Babayants > Version: LMDB 0.9.24 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (188.170.78.53) > > > Hi! > > ASAN shows that the list of spill pages is not freed after transaction: Thanks for the report. Fixed now in mdb.master and mdb.RE/0.9 > ================================================================= > ==test==13046==ERROR: LeakSanitizer: detected memory leaks > > Direct leak of 20971376 byte(s) in 1 object(s) allocated from: > #0 0x4bcbb2 in realloc (test+0x4bcbb2) > #1 0x7f067ef5ed59 in mdb_midl_grow liblmdb/src/midl.c:135:8 > #2 0x7f067ef5ec83 in mdb_midl_append liblmdb/src/midl.c:162:7 > #3 0x7f067ef4456b in mdb_page_spill liblmdb/src/mdb.c:2077:13 > #4 0x7f067ef3960b in mdb_cursor_put liblmdb/src/mdb.c:6640:14 > #5 0x7f067ef5106c in mdb_put liblmdb/src/mdb.c:9027:7 > #6 0x4ec674 in main test.c:28:14 > #7 0x7f067b46d544 in __libc_start_main (/lib64/libc.so.6+0x22544) > > SUMMARY: AddressSanitizer: 20971376 byte(s) leaked in 1 allocation(s). > > Reproducible on LMDB 0.9.24 with the following code (anything doing > long write transaction will trigger this): > #include "lmdb.h" > > int main(int argc,char * argv[]) > { > int rc; > MDB_env *env; > MDB_dbi dbi; > MDB_val key, data; > MDB_txn *txn; > int kval; > char sval[1024] = {0}; // fine to fill with zeroes > > rc = mdb_env_create(&env); > rc = mdb_env_set_mapsize(env, 10ULL * 1024 * 1024 * 1024); // 10 GiB > rc = mdb_env_open(env, "./testdb", 0, 0664); > rc = mdb_txn_begin(env, NULL, 0, &txn); > rc = mdb_dbi_open(txn, NULL, 0, &dbi); > > key.mv_size = sizeof(int); > key.mv_data = &kval; > data.mv_size = sizeof(sval); > data.mv_data = sval; > > for (kval = 0; kval < 100'000'000; ++kval) { > rc = mdb_put(txn, dbi, &key, &data, 0); > } > rc = mdb_txn_commit(txn); > > mdb_dbi_close(env, dbi); > mdb_env_close(env); > return 0; > } > >>From my point of view the leak looks benign (=does not lead to > database corruption or such), but I didn't dive deep enough in LMDB > internals to be completely certain about that. > > Regards, > Alexander Babayants. > > -- -- 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#9126) add: pwdChangedTime leads to seg fault
by ondra＠mistotebe.net 23 Jan '20

23 Jan '20

On Mon, Jan 13, 2020 at 09:35:18PM +0000, michael(a)stroeder.com wrote: > This still happens with current RE24 snapshot. > > Is more information needed to address this? Hi, had a look at it and a proposed patch is in a branch in my GitHub repo: https://github.com/mistotebe/openldap/tree/its9126 Let me know if this fixes the issue for you. As far as I have been able to figure out, the database content generated by ppolicy until now was inconsistent with the schema (normalised value was missing) and existing values will still cause the crash to happen. A fix is to replace the affected values or export/reload the database. Thanks, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

(ITS#9155) LMDB: List of spill pages leaks after transaction
by babayants.alexander＠gmail.com 22 Jan '20

22 Jan '20

Full_Name: Alexander Babayants Version: LMDB 0.9.24 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (188.170.78.53) Hi! ASAN shows that the list of spill pages is not freed after transaction: ================================================================= ==test==13046==ERROR: LeakSanitizer: detected memory leaks Direct leak of 20971376 byte(s) in 1 object(s) allocated from: #0 0x4bcbb2 in realloc (test+0x4bcbb2) #1 0x7f067ef5ed59 in mdb_midl_grow liblmdb/src/midl.c:135:8 #2 0x7f067ef5ec83 in mdb_midl_append liblmdb/src/midl.c:162:7 #3 0x7f067ef4456b in mdb_page_spill liblmdb/src/mdb.c:2077:13 #4 0x7f067ef3960b in mdb_cursor_put liblmdb/src/mdb.c:6640:14 #5 0x7f067ef5106c in mdb_put liblmdb/src/mdb.c:9027:7 #6 0x4ec674 in main test.c:28:14 #7 0x7f067b46d544 in __libc_start_main (/lib64/libc.so.6+0x22544) SUMMARY: AddressSanitizer: 20971376 byte(s) leaked in 1 allocation(s). Reproducible on LMDB 0.9.24 with the following code (anything doing long write transaction will trigger this): #include "lmdb.h" int main(int argc,char * argv[]) { int rc; MDB_env *env; MDB_dbi dbi; MDB_val key, data; MDB_txn *txn; int kval; char sval[1024] = {0}; // fine to fill with zeroes rc = mdb_env_create(&env); rc = mdb_env_set_mapsize(env, 10ULL * 1024 * 1024 * 1024); // 10 GiB rc = mdb_env_open(env, "./testdb", 0, 0664); rc = mdb_txn_begin(env, NULL, 0, &txn); rc = mdb_dbi_open(txn, NULL, 0, &dbi); key.mv_size = sizeof(int); key.mv_data = &kval; data.mv_size = sizeof(sval); data.mv_data = sval; for (kval = 0; kval < 100'000'000; ++kval) { rc = mdb_put(txn, dbi, &key, &data, 0); } rc = mdb_txn_commit(txn); mdb_dbi_close(env, dbi); mdb_env_close(env); return 0; } >From my point of view the leak looks benign (=does not lead to database corruption or such), but I didn't dive deep enough in LMDB internals to be completely certain about that. Regards, Alexander Babayants.

1 0

Re: (ITS#9154) RFE: Number of entries in MDB database in cn=monitor
by michael＠stroeder.com 18 Jan '20

18 Jan '20

On 1/18/20 1:54 PM, Howard Chu wrote: > michael(a)stroeder.com wrote: >> The number of entries could be added there as attribute 'olmMDBEntries' or >> similar. > > Added in git master Great! Thank you. Any chance to see it in RE24? At least the back-port patch seems to work smoothly in my local test environment. Ciao, Michael.

1 0

Re: (ITS#9154) RFE: Number of entries in MDB database in cn=monitor
by hyc＠symas.com 18 Jan '20

18 Jan '20

michael(a)stroeder.com wrote: > Full_Name: Michael Str.der > Version: master > OS: > URL: > Submission from: (NULL) (213.240.182.99) > > > As a system engineer I want to see the number of entries within a mdb database > in the monitoring (e.g. to alarm unusual fast changes due to false deletions). > > While one can use mdb_stat or other custom scripts to monitor the number of > entries of the id2e sub-DB this requires read access to the MDB environment. But > for security reasons this should be avoided. > > olmMDBDatabase entries in cn=monitor already have attributes for MDB page > counts. > The number of entries could be added there as attribute 'olmMDBEntries' or > similar. Added in git master -- -- 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#9154) RFE: Number of entries in MDB database in cn=monitor
by michael＠stroeder.com 17 Jan '20

17 Jan '20

Full_Name: Michael Str.der Version: master OS: URL: Submission from: (NULL) (213.240.182.99) As a system engineer I want to see the number of entries within a mdb database in the monitoring (e.g. to alarm unusual fast changes due to false deletions). While one can use mdb_stat or other custom scripts to monitor the number of entries of the id2e sub-DB this requires read access to the MDB environment. But for security reasons this should be avoided. olmMDBDatabase entries in cn=monitor already have attributes for MDB page counts. The number of entries could be added there as attribute 'olmMDBEntries' or similar.

1 0

(ITS#9153) replication.sdf inconsistent whitespace
by ryan＠openldap.org 14 Jan '20

14 Jan '20

Full_Name: Ryan Tandy Version: RE24 OS: URL: https://github.com/openldap/openldap/compare/OPENLDAP_REL_ENG_2_4...rtandy:… Submission from: (NULL) (70.66.128.207) Submitted by: ryan This patch fixes indentation of two 'maxsize' lines in the 'Syncrepl Proxy' example. For RE24 only as master lacks these lines (will fix separately).

1 0

(ITS#9152) Configuring autoca before database exists crashes slapd
by quanah＠openldap.org 13 Jan '20

13 Jan '20

Full_Name: Quanah Gibson-Mount Version: HEAD OS: N/A URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.143.26) If you configure autoca via cn=config when the underlying DB does not yet exist, slapd will crash. i.e., I added this entry to my cn=config db: dn: olcOverlay=autoca,olcDatabase={1}mdb,cn=config changetype: add objectClass: olcOverlayConfig objectClass: olcACAConfig olcOverlay: autoca olcACAlocalDN: cn=anvil4.rb.symas.net,ou=Servers,dc=rb,dc=symas,dc=net while the mdb database was not yet populated.

1 0

Re: (ITS#9126) add: pwdChangedTime leads to seg fault
by michael＠stroeder.com 13 Jan '20

13 Jan '20

This still happens with current RE24 snapshot. Is more information needed to address this?

1 0

Re: (ITS#9151) slapd-sock - stumped
by matthew＠schlutech.com 12 Jan '20

12 Jan '20

I will move this there thank you. It is difficult to know where to go - this seems like a bug as the behavior is pervasive in all my testing. I have now tried multiple OS and multiple versions of OpenLDAP. As for the path differences - that was just me copying/pasting from two separate tests. I assure you the problem persists when the paths are correct. As you pointed out - inconsistent in the information I provided therein - not in actual testing. Thank you. On 1/12/20 3:30 AM, Michael Ströder wrote: > On 1/11/20 9:03 PM, matthew(a)schlutech.com wrote: >> Always results in socket connect failed. >> >> database sock >> socketpath /tmp/example.sock >> [..] >> Always: socket connect(/root/example.sock) failed > /tmp/example.sock != /root/example.sock > > Either something's inconsistent in your config or the information you > provided herein. > > Also this does not seem to be a bug report but the ITS is only for > reporting bugs. Please send usage questions to openldap-technical > mailing list. > > Ciao, Michael. > >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs