Re: [389-users] memory allocator - calloc of 4098 elems of 4 bytes failed; OS error 12 (Cannot allocate memory)

[Rich Megginson]

On 01/04/2011 11:27 PM, mahao wrote:
>  Hi,
>
>  Thanks for your letter.
>
>  This fedora-ds version is :
>
>  nsslapd-versionstring: Fedora-Directory/1.0.4.
>
>  And platform :
>
>  LSB Version:
>
> :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
>
>  Distributor ID: RedHatEnterpriseServer
>
>  Description: Red Hat Enterprise Linux Server release 5.5 (Tikanga)
>
>  Release: 5.5
>
>  Codename: Tikanga
>
>  Linux esjirp64.emea.nsn-net.net 2.6.18-164.6.1.el5 #1 SMP Tue Oct 27
>  11:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
>
>  I have pasted config.ldif of my fedora-ds server in attachment.
>
>  You said its ran out of memory, but the next day morning after
>  fedora-ds was crashed, I checked cacti monitor of memory, memory and
>  cpu usage rate was on a normal level , far from exhausted.
>
>  And after I restart fedora-ds server 2 hours without changing any
>  configuration, there was no response from ldap server but the process
>  was running and 389 port was listened. And this time no errors were
>  written into error log. I had to restart it again and it have been
>  working fine from then on.
>
>  Do you have any idea of this?
>
>  Thank you for your advice.
>  
Not sure. Looks like all of your cache settings are the default values.
I suppose it could be a memory leak.
I suggest upgrading to 389 1.2.7.5 available from EPEL. Even if that
does not solve your problem, it will be much easier to support.
>  Best Regards
>
>  Ma Hao
>
>  *From:*Rich Megginson [mailto:[e-mail]]
>  *Sent:* 2011年1月5日1:07
>  *To:* mahao
>  *Cc:* 389-users(a)lists.fedoraproject.org
>  *Subject:* Re: memory allocator - calloc of 4098 elems of 4 bytes
>  failed; OS error 12 (Cannot allocate memory)
>
>  On 12/24/2010 12:15 AM, mahao wrote:
>
>  Hi all,
>
>  Fedora-ds was down for some reason,
>
>  And I got these logs:
>
>  [23/Dec/2010:18:59:32 +0200] - libdb: User-specified malloc function
>  returned NULL
>
>  [23/Dec/2010:18:59:32 +0200] - id2entry error 12
>
>  [23/Dec/2010:18:59:32 +0200] - id2entry get error 12
>
>  [23/Dec/2010:18:59:32 +0200] - next_search_entry db err 12
>
>  [23/Dec/2010:18:59:32 +0200] memory allocator - calloc of 4098 elems
>  of 4 bytes failed; OS error 12 (Cannot allocate memory)
>
>  The server has probably allocated all available virtual memory. To solve
>
>  this problem, make more virtual memory available to your server, or reduce
>
>  one or more of the following server configuration settings:
>
>  nsslapd-cachesize (Database Settings - Maximum entries in cache)
>
>  nsslapd-cachememsize (Database Settings - Memory available for cache)
>
>  nsslapd-dbcachesize (LDBM Plug-in Settings - Maximum cache size)
>
>  nsslapd-import-cachesize (LDBM Plug-in Settings - Import cache size).
>
>  Can't recover; calling exit(1).
>
>  It looks like no more available virtual memory to use, so should I set
>  a lager nsslapd-dbcachesize?
>
>  I don't know if it will down again, and please give me some advice .
>  its important to me. Thanks a lot
>
>  What version of fedora-ds or 389-ds-base?
>  What platform?
>
>  This usually means you have run out of memory. The usual thing is to
>  reduce your cache sizes (as specified above). Start with
>  nsslapd-dbcachesize as the minimum. Set nsslapd-cachememsize to be
>  large enough to cache all of your entries, but no larger.
>
>  BS
>
>  Ma Hao
>