Rick,
the server dumps the logs into the configured working directory (nsslapd-workingdir
attribute in cn=config), right?
-Reinhard
-----Original Message-----
From: 389-users-bounces(a)lists.fedoraproject.org
[mailto:389-users-bounces@lists.fedoraproject.org] On Behalf Of Rich Megginson
Sent: Tuesday, September 07, 2010 10:56 AM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] Segfault & Core Dumps
Dael Maselli wrote:
Hi,
I'm experiencing a lot of segmentation fault on my installations, I
have the latest release on EPEL on SL 5.4 (389-Directory/1.2.5 B2010.012.2034).
Do you see seg fault messages in /var/log/messages?
I'm trying to get core dumps but without success. Is there a
specific
configuration that prevents/allows 389-ds to core dump?
The default on linux, you know, is to have core dump soft limit to 0,
so I changed it for 389 in /etc/sysconfig/dirsrv, adding the line:
ulimit -c unlimited
and now I get:
# more /proc/`pidof ns-slapd`/limits | grep core
Max core file size unlimited unlimited bytes
Kernel parameters are at default:
# sysctl -a | grep kernel.core
kernel.core_pattern = core
kernel.core_uses_pid = 1
So, I expected a core dump in /proc/`pidof ns-slapd`/cwd/, right?
The directory server dumps core in the log file directory, which by default is
/var/log/dirsrv/slapd-INSTANCE
Is the crash easily reproducible?
But when it segfaults no file is created in cwd.
Can you help me, please?
Thank you.
Best regards,
Dael Maselli.
--
389 users mailing list
389-users(a)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