Hello, I have a problem in a production environment using Openldap 2.2.13. The problem is, even establishing a reduced cachesize for Berkeley backend, my openldap server starts to consume more and more memory until all RAM is exhausted, causing server stop running (and sometimes backend corruption). I have followed indications included in faq-o-matic to calculate an accurate cache size for BDB backend (8MB), but the problem doesn't solves. At beginning, openlaps starts with few memory (as configuration indicates) but later more and more memory is consumed by the process. Here is the information about my ldap server and service in order you can give a solution. I want that mi slapd process doesn't cosume all fisical memory, basically.
Server: - RAM: 1GB - Swap: 1GB
Openldap: - version: 2.2.13 - sizelimit: 5000
Backend: - Type: bdb - checkpoint: 512 30 - cachesize: 5000
DB_CONFIG: - Cache (8MB): set_cachesize 0 8388608 1 - Other options: set_lg_regionmax 262144 set_lg_bsize 2097152 set_lg_dir /var/lib/ldap/logs set_lg_max 52428800 set_flags DB_LOG_AUTOREMOVE - dn2id.bdb size: 177MB - id2entry.bdb size: 555MB
Top information: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ SWAP COMMAND 12547 ldap 19 0 509m 139m 13m S 1.3 13.9 9:30.32 369m slapd
If I execute a pmap over slapd PID, there is a lot of RAM used by 'anon' piece of memory. Any commentary will be very appreciated. Thanks.
On 6/27/07, jsianes@andaluciajunta.es jsianes@andaluciajunta.es wrote:
Hello, I have a problem in a production environment using Openldap 2.2.13. The problem is, even establishing a reduced cachesize for Berkeley backend, my openldap server starts to consume more and more memory until all RAM is exhausted, causing server stop running (and sometimes backend corruption). I have followed indications included in faq-o-matic to calculate an accurate cache size for BDB backend (8MB), but the problem doesn't solves. At beginning, openlaps starts with few memory (as configuration indicates) but later more and more memory is consumed by the process. Here is the information about my ldap server and service in order you can give a solution. I want that mi slapd process doesn't cosume all fisical memory, basically.
Server:
- RAM: 1GB
- Swap: 1GB
Openldap:
- version: 2.2.13
- sizelimit: 5000
Backend:
- Type: bdb
- checkpoint: 512 30
- cachesize: 5000
DB_CONFIG:
- Cache (8MB): set_cachesize 0 8388608 1
- Other options: set_lg_regionmax 262144 set_lg_bsize 2097152 set_lg_dir /var/lib/ldap/logs set_lg_max 52428800 set_flags DB_LOG_AUTOREMOVE
- dn2id.bdb size: 177MB
- id2entry.bdb size: 555MB
Top information: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ SWAP COMMAND 12547 ldap 19 0 509m 139m 13m S 1.3 13.9 9:30.32 369m slapd
If I execute a pmap over slapd PID, there is a lot of RAM used by 'anon' piece of memory. Any commentary will be very appreciated. Thanks.
While there could easily be a memory leak in your older version of openldap, can you try to lower the cachesize and idlcachesize in your slapd.conf?
--On June 27, 2007 12:27:21 PM -0400 matthew sporleder msporleder@gmail.com wrote:
If I execute a pmap over slapd PID, there is a lot of RAM used by 'anon' piece of memory. Any commentary will be very appreciated. Thanks.
While there could easily be a memory leak in your older version of openldap, can you try to lower the cachesize and idlcachesize in your slapd.conf?
s/could easily be/are known/
i.e., upgrade. You are only harming yourself by running 2.2.13. At the least, get the final 2.2 version (2.2.30?).
--Quanah
-- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
--On June 27, 2007 12:27:21 PM -0400 matthew sporleder msporleder@gmail.com wrote:
If I execute a pmap over slapd PID, there is a lot of RAM used by 'anon' piece of memory. Any commentary will be very appreciated. Thanks.
While there could easily be a memory leak in your older version of openldap, can you try to lower the cachesize and idlcachesize in your slapd.conf?
s/could easily be/are known/
i.e., upgrade. You are only harming yourself by running 2.2.13. At the least, get the final 2.2 version (2.2.30?).
The server OS is a RedHat Enterprise Linux 4, I'm using official distribution package. So, is this a known memory leak problem of primary 2.2 Openldap versions? Thanks for your recommendations.
On Thursday, 28 June 2007, jsianes@andaluciajunta.es wrote:
--On June 27, 2007 12:27:21 PM -0400 matthew sporleder
.
The server OS is a RedHat Enterprise Linux 4, I'm using official distribution package. So, is this a known memory leak problem of primary 2.2 Openldap versions? Thanks for your recommendations.
If RedHat is unable to solve your problem, you may consider at least running a version that people on this list are prepared to support.
http://anorien.warwick.ac.uk/mirrors/buchan/openldap/rhel4
While you are running the Red Hat versions, the best place to get support is Red Hat (but you may find that you would prefer to run something else).
Regards, Buchan
openldap-software@openldap.org
-
Buchan Milne -
jsianes＠andaluciajunta.es -
matthew sporleder -
Quanah Gibson-Mount