RE: Segmentation fault from mdb_stat -a after successful mdb_copy -c

nux bigram 4.15.0-91-generic Ext4 fs -Original Message- From: Howard Chu [mailto:h...@symas.com] Sent: Monday, March 15, 2021 6:00 AM To: Alec Matusis ; openldap-technical@openldap.org Subject: Re: Segmentation fault from mdb_stat -a after successful mdb_copy -c Alec Matusis wrote: >

Re: Segmentation fault from mdb_stat -a after successful mdb_copy -c

Alec Matusis wrote: > I have an environment with one database: > #mdb_copy -V > > LMDB 0.9.70: (December 19, 2015) This is not an actual LMDB version, it's the generic number assigned to the mdb.master development branch. You'll have to be more specific (commit ID). And understand that since

Re: Segmentation Fault on ldap_chain_op

Hi Jeremy, --On Thursday, January 9, 2020 1:07 PM -0800 Jeremy Diaz wrote: The resulting slapd logs were normal. To obtain further information we obtained the following trace of the segfault using gdb: Please file an ITS for this issue, with a full gdb thr apply all bt full from the

Re: Segmentation fault (core dumped) on ldapmodify

Possibly its#7477 > On Dec 23, 2015, at 7:14 PM, Ryan Tandy wrote: > >> On Wed, Dec 23, 2015 at 08:55:13PM -0500, Tim Dunphy wrote: >> I'm using version 2.4.31. And I installed it through the ubuntu package >> manger (apt-get). >> >> [root@ldap1:~] #slapd -V >> @(#) $OpenLDAP:

Re: Segmentation fault (core dumped) on ldapmodify

On Wed, Dec 23, 2015 at 08:55:13PM -0500, Tim Dunphy wrote: I'm using version 2.4.31. And I installed it through the ubuntu package manger (apt-get). [root@ldap1:~] #slapd -V @(#) $OpenLDAP: slapd (Ubuntu) (Sep 15 2015 18:19:13) $ buildd@lgw01-53

Re: Segmentation fault (core dumped) on ldapmodify

Hi Tim, On Wed, Dec 23, 2015 at 05:43:56PM -0500, Tim Dunphy wrote: [root@ldap1:~] #ldapmodify -H ldapi:// -Y EXTERNAL -f addcerts.ldif SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 Segmentation fault (core dumped)

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

Simon Majou wrote: Correction, with the flags MDB_RESERVE|MDB_APPENDDUP What part of DUPSORT and RESERVE are incompatible do you not understand? Here is the stack from gdb : Program received signal SIGSEGV, Segmentation fault. mdb_node_del (mc=mc@entry=0x7fffdb10, ksize=ksize@entry=0)

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

In your previous mail you said they were incompatible, but you provided a logical reason why (you can't sort the data). Now I found a case where the reason doesn't apply (you can append without doing the comparison). So I thought maybe there was something else I missed. But ok I understand this is

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

Simon Majou wrote: In your previous mail you said they were incompatible, but you provided a logical reason why (you can't sort the data). Now I found a case where the reason doesn't apply (you can append without doing the comparison). No, you can't.

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

And in the case where I want to append data in a DUPSORT database, is there a way to write directly in the persisted page ? I tried with the flags MDB_RESERVE|MDB_APPEND but it fails. On 18 August 2015 at 15:41, Simon Majou si...@majou.org wrote: Oh ok it makes sense now. Thank you for the

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

Correction, with the flags MDB_RESERVE|MDB_APPENDDUP Here is the stack from gdb : Program received signal SIGSEGV, Segmentation fault. mdb_node_del (mc=mc@entry=0x7fffdb10, ksize=ksize@entry=0) at mdb.c:7183 7183mp-mp_ptrs[j] = mp-mp_ptrs[i]; (gdb) bt #0 mdb_node_del

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

This is version 0.9.16 I used sample-bdb.txt for instance, with the DUP_SORT option, and the mdb_put with the MDB_RESERVED flags, and execute it 2 times. The first run (creation) is ok, the second (update) gets the seg fault. I ran it in gdb and got the stack : #0 mdb_cursor_set

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

Simon Majou wrote: Hello, I wonder, why do I get a Segmentation fault when I use mdb_put with MDB_RESERVE on a key that already exists ? Have no idea. Provide some more details and maybe we can guess. LMDB version? stack trace from SEGV? What's the size of the existing record, what's the

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

Oh ok it makes sense now. Thank you for the heads up On 18 August 2015 at 15:36, Howard Chu h...@symas.com wrote: Simon Majou wrote: This is version 0.9.16 I used sample-bdb.txt for instance, with the DUP_SORT option, and the mdb_put with the MDB_RESERVED flags, and execute it 2 times.

Re: Segmentation fault when overwriting a k/v with MDB_RESERVE ?

Simon Majou wrote: This is version 0.9.16 I used sample-bdb.txt for instance, with the DUP_SORT option, and the mdb_put with the MDB_RESERVED flags, and execute it 2 times. The first run (creation) is ok, the second (update) gets the seg fault. DUPSORT and RESERVED are incompatible. RESERVED

Re: Segmentation fault in s23_clnt.c when used in a library

On 2014-10-15 13:57, Aaron Richton wrote: On Wed, 15 Oct 2014, Tobias Ljunggren wrote: I built with moznss instead of openSSL. That solves the problem and I don't try to fix someone else mistakes. It might hide the problem, but that doesn't fix anything. It's worth reiterating up front that

Re: Segmentation fault in s23_clnt.c when used in a library

On Wed, 15 Oct 2014, Tobias Ljunggren wrote: I built with moznss instead of openSSL. That solves the problem and I don't try to fix someone else mistakes. It might hide the problem, but that doesn't fix anything. It's worth reiterating up front that MozNSS isn't ideal, especially if you're

Re: Segmentation fault in s23_clnt.c when used in a library

I built with moznss instead of openSSL. That solves the problem and I don't try to fix someone else mistakes. Best regards, Tobias On 2014-10-08 14:59, Tobias Ljunggren wrote: Hello, I just found what's causing the crash. The application that loads my library already have some of the

Re: Segmentation fault in s23_clnt.c when used in a library

Hello, I just found what's causing the crash. The application that loads my library already have some of the openSSL functions. Either they have copied the source code or statically linked to openSSL. Because of this openLDAP sometimes uses the wrong functions (SSL_new is one of them). I

Re: segmentation fault when attempting to delete olcOverlay={0}syncprov entry in cn=config (Runtime) Configuration

Ralf and everyone, I discovered that I had the DN of the syncprov overlay entry wrong. I had the following: olcOverlay={0}syncprov,olcDatabase={0}config,cn=config I changed it to: olcOverlay=syncprov,olcDatabase=*{1}bdb,*cn=config And now the replication works between my two servers, AND when

Re: segmentation fault when attempting to delete olcOverlay={0}syncprov entry in cn=config (Runtime) Configuration

Here is the # of the bug report on bugzilla. Bug 625219 Submitted OpenLDAP server 2.4.21-47.1 crashes (segmentation fault) when deleting syncprov overlay entry in cn=config configuration On Thu, Jul 22, 2010 at 2:06 AM, Ralf Haferkamp rha...@suse.de wrote: Am Mittwoch 21 Juli 2010, 20:02:43

Re: segmentation fault when attempting to delete olcOverlay={0}syncprov entry in cn=config (Runtime) Configuration

Am Dienstag 20 Juli 2010, 20:25:46 schrieb jon brandt: I looked but couldn't find a match to this issue, so was wondering if anyone else has seen something like it or can tell what might be wrong in my configuration. Thanks in advance! I'm using OpenLDAP version 2.4.21-47.1 (here is the

Re: segmentation fault when attempting to delete olcOverlay={0}syncprov entry in cn=config (Runtime) Configuration

Thanks for the reply Ralf! I got the RPMs for SUSE I believe (i.e. I didn't build the server myself), so I'm assuming the DSLAP_CONFIG_DELETE flag was used. All the other deletes work fine (I'm adding then deleting other directives, for example olcMirrorMode or olcDbIndex and those delete just

Re: Segmentation Fault

--On Thursday, July 08, 2010 1:32 PM +0200 Paul Harvey phar...@cern.ch wrote: Does anyone have any suggestions, and what more information do i need to provide. Well, the version of OpenLDAP you are using would be useful. Given that without that, we can't even tell you of any fix(es) that

Re: Segmentation Fault

--On Friday, July 09, 2010 7:12 PM +0200 Paul Harvey phar...@cern.ch wrote: Hi, You may have guessed that i am new to this... @(#) $OpenLDAP: slapd 2.4.21 (Apr 26 2010 11:07:14) $ bui...@rothera:/build/buildd/openldap-2.4.21/debian/build/servers/slapd Think that this says it all, simply

Re: Segmentation Fault

On Friday, 9 July 2010 18:12:34 Paul Harvey wrote: You may have guessed that i am new to this... @(#) $OpenLDAP: slapd 2.4.21 (Apr 26 2010 11:07:14) $ bui...@rothera:/build/buildd/openldap-2.4.21/debian/build/servers/slapd Think that this says it all, simply got it from the repo at

Re: Segmentation Fault appearing while doing the sync.-OpenLDAP 2.4.22

rahul.mancha...@bt.com writes: Hi , I have added sync_use_subentry in the ldap configuration and it started throwing the core dump while performing the sync from other running server and stops the LDAP process. Did you run the core within gdb? Here is the error seen the in the debug logs.

RE: Segmentation Fault appearing while doing the sync.-OpenLDAP 2.4.22

AM To: Manchanda,RK,Rahul,DKE C Cc: openldap-technical@openldap.org Subject: Re: Segmentation Fault appearing while doing the sync.-OpenLDAP 2.4.22 rahul.mancha...@bt.com writes: Hi , I have added sync_use_subentry in the ldap configuration and it started throwing the core dump while