 |
 |
Hi Bockjoo, As there was nothing in the log at the time of demise, it wasn't an xrootd generated error. If you see a core file that was generated at the time it crashed then you should check that to see what caused it using gdb. Otherwise, the most other common problem is the OOM process which picks a process to kill when the system is running low on memory. Usually, this is the process that uses the most memory but not always.The syslog should contain messages about that as well. More information on this can be found here: https://haydenjames.io/how-to-diagnose-oom-errors-on-linux-systems/ Andy On Thu, 21 Jul 2022, Bockjoo Kim wrote: > Hi, > > My local xrootd redirector died yesterday with this in the syslog: > > Jul 20 17:03:15 cmsio7 systemd[1]: [log in to unmask]: main process exited, code=exited, status=2/INVALIDARGUMENT > Jul 20 17:03:15 cmsio7 systemd[1]: Unit [log in to unmask] entered failed state. > Jul 20 17:03:15 cmsio7 systemd[1]: [log in to unmask] failed. > > I can not find anything related from the xrootd log. > > What could have caused the sudden demise of the redirector daemon? > > Thanks, > > Bockjoo > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the XROOTD-L list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1 > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1