openldap-technical January 2013

openldap-technical@openldap.org

71 participants
131 discussions

Re: slapd crashes with ch_realloc of X bytes failed
by Meike Stone 15 Jan '13

15 Jan '13

>> >>> From slapd.conf/cn=config: >>> a) cachesize setting >>> b) idlcachesize setting >>> c) dncachesize setting >> >> >> cachesize 750000 >> dncachesize 750000 >> idlcachesize 2250000 >> >> Thanks and best regards > > > Your settings here don't make a lot of sense. > > I would try > cachesize 1500000 > dncachesize 0 (or leave it unset) > idlcachesize 3000000 > Yes, I know this values are very low in my configuration, but if I have problems with the memory, should I increase the caches that use this memory? In the last thread , you confirmed, that if I increasing the DB cachesize, the system is faster running out of memory. http://www.openldap.org/lists/openldap-technical/201211/msg00171.html ("ch_realloc means the system ran out of memory. Increasing the DB_CONFIG cachesize will run you out of memory more quickly.") To get the slapd a little bit more stable, I reduced this values (caches) to the posted in last message. Before i had: cachesize 1000000 dncachesize 1000000 idlcachesize 3000000 > Your current idlcachesize in particular may be part of the issue in addition > to your glibc setting. But the problem exist on the test system with tcmalloc too. So are 24GByte RAM for 1.500.000 DNs and 6GByte DB are not enough? During all time (especially the crash), there was enough physical (unallocated) memory free. But "slapd/malloc" tried to allocate more and more (as you can see in the post from 2013/01/12), but did not use it, no matter if glibc or tcmalloc I hope I interpreted it right?! Thanks Meike Btw.: I use a "special version" of openldap. Because of limited index slot of 65535, I changed in openldap-2.4.33.orig/include/ldap_pvt_thread.h from # define LDAP_PVT_THREAD_STACK_SIZE ( 1 * 1024 * 1024 * sizeof(void *) ) to # define LDAP_PVT_THREAD_STACK_SIZE ( 2 * 1024 * 1024 * sizeof(void *) ) and in openldap-2.4.33/servers/slapd/back-bdb/idl.h from #define BDB_IDL_LOGN 16 /* DB_SIZE is 2^16, UM_SIZE is 2^17 */ to #define BDB_IDL_LOGN 17 /* DB_SIZE is 2^17, UM_SIZE is 2^18 */ as Howard it recommended http://www.openldap.org/lists/openldap-technical/201101/msg00095.html Maybe this could be the problem?? My changes are available under: https://build.opensuse.org/package/show?expand=0&package=openldap2&project=…

2 1

Using smbtools an create account
by rodrigo tavares 15 Jan '13

15 Jan '13

Hello People. I have a samba server and LDAP, it´s running, but i put the slap replicate, come this error: root@replica:/etc/smbldap-tools# smbldap-useradd -a ola Error: shadow context; no update referral at /usr/share/perl5/smbldap_tools.pm line 1187. If I remove config slap replicate is run. syncrepl rid=123 provider=ldap://10.65.11.250:389 type=refreshOnly interval=00:00:05:00 retry="60 30 300 +" searchbase="dc=net,dc=mg,dc=gov,dc=br" filter="(objectClass=*)" scope=sub attrs="*,+" schemachecking=off bindmethod=simple binddn="cn=admin,dc=net,dc=mg,dc=gov,dc=br" credentials=secret Any idea ? Rodrigo Faria

2 4

Re: kernel: slapd[7962]: segfault
by Quanah Gibson-Mount 14 Jan '13

14 Jan '13

--On Tuesday, January 15, 2013 11:43 AM +0530 Pawan Kamboj <pawank.kamboj(a)gmail.com> wrote: > > Is there any fixes for time being? > Keep replies to the list. You need to understand you're running a piece of software that is several years old, for which support ended a few years ago. Even then 2.3.43 was the last release of the 2.3 series. So you are running an ancient version of OpenLDAP with numerous known problems. Any help is going to require you to upgrade to a supported release. If you want to pay for help, you could try Symas perhaps: <http://www.symas.com> --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

kernel: slapd[7962]: segfault
by Pawan Kamboj 14 Jan '13

14 Jan '13

Hi Team, SLAPD is crashing with the throwing following error. ldap1p kernel: slapd[7962]: segfault at 0000000000000008 rip 000000000044cef0 rsp 000000004169c528 error 4 We are using the following version of openldap and bdb. Openldap 2.3.32 DB.4.5 Any help? Regards Pawan Kamboj

2 1

Re: pthread lock failed: Resource deadlock avoided
by Chandrashekar Kola 14 Jan '13

14 Jan '13

Linux version: Linux version 2.6.18-194.el5 *Regards,* *Chandrashekar kola,* *408-666-2814* On Mon, Jan 14, 2013 at 7:37 PM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Monday, January 14, 2013 7:13 PM -0800 Chandrashekar Kola < > chandrashekar.kola(a)gmail.com> wrote: > > >> What version of BDB is OpenLDAP compiled against? >>> >> BDB version is 4.3.29 >> > > BDB 4.3 has been known to be buggy for years. You should use something > recent. > > > What version of OpenLDAP 2.4? >>> >> OpenLDAP 2.4.22 >> > > Use a real version of OpenLDAP > > What OS? >> > > You still didn't answer this. > > > --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: pthread lock failed: Resource deadlock avoided
by Chandrashekar Kola 14 Jan '13

14 Jan '13

Hi Quanah, Thank you for quick reply. Here are the details. > Have you checked your lock/lockers/lock object settings? 112 Last allocated locker ID 0x7fffffff Current maximum unused locker ID 9 Number of lock modes 1500 Maximum number of locks possible 1500 Maximum number of lockers possible 1500 Maximum number of lock objects possible 40 Number of lock object partitions 8 Number of current locks 445 Maximum number of locks at any one time 12 Maximum number of locks in any one bucket 0 Maximum number of locks stolen by for an empty partition 0 Maximum number of locks stolen for any one partition 90 Number of current lockers 115 Maximum number of lockers at any one time 8 Number of current lock objects 226 Maximum number of lock objects at any one time 3 Maximum number of lock objects in any one bucket 0 Maximum number of objects stolen by for an empty partition 0 Maximum number of objects stolen for any one partition 10M Total number of locks requested (10526725) 10M Total number of locks released (10518219) 0 Total number of locks upgraded 18 Total number of locks downgraded 8766 Lock requests not available due to conflicts, for which we waited 7739 Lock requests not available due to conflicts, for which we did not wait 759 Number of deadlocks 0 Lock timeout value 0 Number of locks that have timed out 0 Transaction timeout value 0 Number of transactions that have timed out 1MB 224KB The size of the lock region 3663 The number of partition locks that required waiting (0%) 243 The maximum number of times any partition lock was waited for (0%) 0 The number of object queue operations that required waiting (0%) 675 The number of locker allocations that required waiting (0%) 0 The number of region locks that required waiting (0%) 3 Maximum hash bucket length > What version of BDB is OpenLDAP compiled against? BDB version is 4.3.29 > What version of OpenLDAP 2.4? OpenLDAP 2.4.22 What OS? *Regards,* *Chandrashekar kola,* *408-666-2814* On Mon, Jan 14, 2013 at 5:50 PM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Monday, January 14, 2013 5:08 PM -0800 Chandrashekar Kola < > chandrashekar.kola(a)gmail.com> wrote: > > Hello, >> >> We have a openldap running on version 2.4, recently we started seeing >> these kind of error messages in ldap.log. >> > > Have you checked your lock/lockers/lock object settings? > > What version of BDB is OpenLDAP compiled against? > > What version of OpenLDAP 2.4? > > What OS? > > --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 >

2 1

pthread lock failed: Resource deadlock avoided
by Chandrashekar Kola 14 Jan '13

14 Jan '13

Hello, We have a openldap running on version 2.4, recently we started seeing these kind of error messages in ldap.log. Jan 14 04:03:03 ldap-cl-node02-vm slapd2.4[32455]: bdb(o=foo): pthread lock failed: Resource deadlock avoided Jan 14 04:03:03 ldap-cl-node02-vm slapd2.4[32455]: bdb(o=foo): PANIC: Resource deadlock avoided Jan 14 04:03:03 ldap-cl-node02-vm slapd2.4[32455]: => bdb_idl_insert_key: c_put id failed: DB_RUNRECOVERY: Fatal error, run database recovery (-30974) Jan 14 04:03:03 ldap-cl-node02-vm slapd2.4[32455]: bdb(o=foo): PANIC: fatal region error detected; run recovery Jan 14 04:03:03 ldap-cl-node02-vm slapd2.4[32455]: conn=23402078 op=6: attribute "entryCSN" index add failure This happened today morning and after restarting, it's started working fine for few hours. And then we saw these error messages in the logs, and crashed again. Jan 14 13:35:15 ldap-cl-node02-vm slapd2.4[1397]: bdb(o=foo): PANIC: Invalid argument Jan 14 13:35:15 ldap-cl-node02-vm slapd2.4[1397]: => bdb_idl_insert_key: c_put id failed: DB_RUNRECOVERY: Fatal error, run database recovery (-30974) Jan 14 13:35:15 ldap-cl-node02-vm slapd2.4[1397]: bdb(o=foo): PANIC: fatal region error detected; run recovery Did anybody face this issue, and what will be the resolution. Please help me. *Regards,* chandu

2 1

pthread lock failed: Resource deadlock avoided
by Chandrashekar Kola 14 Jan '13

14 Jan '13

1 0

Re: slapd crashes with ch_realloc of X bytes failed
by Meike Stone 14 Jan '13

14 Jan '13

2013/1/14 Quanah Gibson-Mount <quanah(a)zimbra.com>: > > > Sorry, I don't have your configuration memorized. Generally, you should > list: Oops sorry, I used my gmail account and did not see, that the thread in the mailing list is "broken".. Here are all posted informations from my production system http://www.openldap.org/lists/openldap-technical/201211/msg00164.html > > memory allocator (should be tcmalloc, if you've set that up correctly) In the test system yes (us see it in the pmaps), but on production, I use glibc. > > DB Information: > a) Total number of DNs in your database about 1.500.000 > b) DB_CONFIG settings set_cachesize 2 0 1 set_lg_regionmax 262144 set_lg_bsize 2097152 set_flags DB_LOG_AUTOREMOVE > c) Size of database on disk: du -c -h *.bdb 27M MyActivateTime.bdb 8.0K MyClassName.bdb 30M MyDeletedTime.bdb 14M MyInsertDate.bdb 92K MyJpeg.bdb 1.9M MyKey.bdb 2.2M MyLanguage.bdb 184K MyPhoneNumber.bdb 38M MyPk.bdb 14M MyPId.bdb 5.4M MyPIfId.bdb 9.4M MyProductTyp.bdb 140K MyProperty.bdb 2.5M MySystemFlag.bdb 22M MyUserName.bdb 184K MyVId.bdb 428M cn.bdb 728M dn2id.bdb 37M entryCSN.bdb 39M entryUUID.bdb 4.0G id2entry.bdb 6.2M objectClass.bdb 5.4G total > From slapd.conf/cn=config: > a) cachesize setting > b) idlcachesize setting > c) dncachesize setting cachesize 750000 dncachesize 750000 idlcachesize 2250000 Thanks and best regards Meike

2 1

Re: Replication not working
by Quanah Gibson-Mount 14 Jan '13

14 Jan '13

--On Sunday, January 13, 2013 1:37 AM +0530 anil beniwal <beni.anil(a)gmail.com> wrote: > > Hi Quanah > > I will be highly thankful to you, if you can help me out in below issue. > > We have three servers on rhel 6.3, 16 vcpu and 32G RAM , openldap 2.4.33 > with mdb db of 200G a) Keep messages to the list b) Use delta-syncrepl for MMR c) Grab the latest RE24 code --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

← Newer
1
...
6
7
8
9
10
11
12
13
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical January 2013