 |
 |
Hi, Thanks for the information. When I set DAEMON_COREFILE_LIMIT in /etc/sysconfig/xrootd . I still do not get a core file. Instead I ran the same command that the daemon runs from the xrootd account and was able to get a core file. I started xrootd with this command - /usr/bin/xrootd -l /var/log/xrootd/xrootd.log -c /etc/xrootd/xrootd-standalone.cfg -k 7 -b -s /var/run/xrootd/xrootd-default.pid -n default and generated a core file: http://ascnfs.hep.anl.gov:2080/xrootd-3.10-rc1/core.8526 http://ascnfs.hep.anl.gov:2080/xrootd-3.10-rc1/xrootd.log http://ascnfs.hep.anl.gov:2080/xrootd-3.10-rc1/xrootd-standalone.cfg Interestingly enough (perhaps it will help with debugging) starting xrootd without -b switch and it runs fine. (OK I see this error: 111007 07:27:24 8573 cms_Finder: Waiting for cms path /var/spool/xrootd/admin/.olb/olbd.admin The directory /var/spool/xrootd/admin/.olb/ was not created automatically. I hope all of this helps. Cheers, Doug On Oct 7, 2011, at 6:30 AM, Brian Bockelman wrote: > Hi, > > If you are using the RHEL-provided "daemon" function in the init scripts, the core behavior is controlled by $DAEMON_COREFILE_LIMIT. This overrides "ulimit" in sysconfig and /etc/security/limits.conf. > > Brian > > On Oct 7, 2011, at 6:12 AM, Doug Benjamin wrote: > >> Hi, >> I check in the dir suggested after reading the script this is why I am surprised about >> No core file >> >> Doug >> >> Sent from my iPad please excuse the typos and creative grammar >> >> >> On Oct 7, 2011, at 3:36, Lukasz Janyst <[log in to unmask]> wrote: >> >>> Besides, there is no need to do any init script hacking just put >>> whatever command you like in /etc/sysconfig/xrootd. >>> >>> Lukasz >>> >>> 2011/10/7 Lukasz Janyst <[log in to unmask]>: >>>> Doug, >>>> >>>> the init script would by default cd to /var/spool/xrootd. Have you >>>> looked for the core files there? >>>> >>>> Cheers, >>>> Lukasz >>>> >>>> 2011/10/7 Doug Benjamin <[log in to unmask]>: >>>>> Hi, >>>>> I did that both by hacking the startup script and by changing things for xrootd user in >>>>> The /etc/security/limits.conf file already and still could not get a core file. >>>>> Will try again tomorrow >>>>> >>>>> Doug >>>>> >>>>> Sent from my iPad please excuse the typos and creative grammar >>>>> >>>>> >>>>> On Oct 6, 2011, at 22:30, Andrew Hanushevsky <[log in to unmask]> wrote: >>>>> >>>>>> Hi Doug, >>>>>> >>>>>> You need to set the corelimit to unlimited but that has to be done in the init script. Quite odd. It may be that one of the shared libraries isn't quite right when starting it via service, sigh. >>>>>> >>>>>> Andy >>>>>> >>>>>> On Thu, 6 Oct 2011, Doug Benjamin wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> When I start xrootd from the /sbin/service xrootd start command (or obviously /etc/init.d/xrootd) >>>>>>> It starts that then immediately will seg fault. No core file is left though. >>>>>>> >>>>>>> If xrootd is started outside of the daemon command (still the xrootd user), it starts up and does >>>>>>> not core dump right away. >>>>>>> >>>>>>> Any ideas how I can capture the core for you. >>>>>>> >>>>>>> Doug >>>>>>> >>>>>>> >>>>> >>>>> >>>> >