Dael Maselli wrote: > > It worked! > > I wrote fs.suid_dumpable=1 in /etc/sysctl.conf, `sysctl -p` and > restarted dirsrv. Now it dumps. > > Thank you! > > I will report here the backtrace when it occurs. Great! Be sure to install the 389-ds-base-debuginfo package to get the symbols when generating the backtrace. > > Regards, > Dael Maselli. > > > > On 07/09/10 19.44, Ulf Weltman wrote: >> On 9/7/2010 8:25 AM, Dael Maselli wrote: >>> Hi Rich, >>> >>> On 07/09/10 16.56, Rich Megginson wrote: >>>> Do you see seg fault messages in /var/log/messages? >>> Sure: ns-slapd[13737]: segfault at 00000000000000bc rip >>> 0000003abb420375 >>> rsp 00000000580d85d0 error 4 >>> >>> >>>> The directory server dumps core in the log file directory, which by >>>> default is /var/log/dirsrv/slapd-INSTANCE >>> Yes, it is the same as working directory: >>> # ls -l /proc/`pidof ns-slapd`/cwd >>> lrwxrwxrwx 1 root root 0 Sep 7 17:12 /proc/18721/cwd -> >>> /var/log/dirsrv/slapd-ds1 >>> >>> >>>> Is the crash easily reproducible? >>> No, it isn't. It seems random, but I can simulate a crash with kill >>> -QUIT. >>> >>> I tried killing a simple `sleep 10`: >>> >>> # ulimit -c unlimited >>> >>> # sleep 10& >>> [1] 19726 >>> >>> # kill -QUIT 19726 >>> [1]+ Quit (core dumped) sleep 10 >>> >>> # ls -l core.* >>> -rw------- 1 root root 290816 Aug 31 08:52 core.1008 >>> >>> But if I kill -QUIT ns-slapd no file is created. >> ns-slapd typically runs as setuid to a non-root user. Check what >> fs.suid_dumpable or kernel.suid_dumpable are set to. >>> Thanks, >>> Dael Maselli. >>> >>> >> >> >> >> -- >> 389 users mailing list >> 389-users@xxxxxxxxxxxxxxxxxxxxxxx >> https://admin.fedoraproject.org/mailman/listinfo/389-users > > ------------------------------------------------------------------------ > > -- > 389 users mailing list > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
