you could use
ldapsearch ... -b "cn=ldbm database,cn=plugins,cn=config"
"cn=monitor"
currententrycachesize
to monitor the usage of the entrycache.
But be aware that the process uses more memory than just the caches and
the memory manager can also generate some overhead.
Regards,
Ludwig
On 11/15/2012 02:55 PM, Moisés Barba Pérez wrote:
yes, thats correct, but shouldn't use all that memory because
don't
need so much memory
2012/11/15 Ludwig Krispenz <lkrispen(a)redhat.com
<mailto:lkrispen@redhat.com>>
Hi,
On 11/15/2012 01:54 PM, Moisés Barba Pérez wrote:
> Hi,
>
> I have a memory issue with 389-ds 1.2.5 in a CentOS 5.5 64bits
> 4GB ram.
>
> The server swaps when the server physical memory increase over
> 75% approx. When the swap is full the server reaches 100% of
> physical memory and the SO kills the ns-ldapd process.
>
> Out of memory: Killed process 30383, UID 99, (ns-slapd).
>
> The cache sizes are:
>
> nsslapd-dbcachesize: 838860800
> nsslapd-import-cachesize: 20000000
> nsslapd-cachememsize: 125829120 (for each 26 db)
do you mean you have 26 db backends with 125MB entrycache each ?
So you would reach 3.2GB for entrycache and 800MB dbcache.
Regards,
Ludwig
>
> Which can be the problem?
>
>
>
> --
> 389 users mailing list
> 389-users(a)lists.fedoraproject.org
<mailto:389-users@lists.fedoraproject.org>
>
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users(a)lists.fedoraproject.org
<mailto:389-users@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users