 |
 |
Observed with CASTOR @ CERN and discussed with @simonmichal: By using the standard xrootd logrotation script and starting xrootd with an instance name and the fifo option as follows: ``` [root@host]# grep Exec !$ grep Exec /etc/systemd/system/xrootd\@.service.d/xrootd.conf ExecStart= ExecStart=/usr/bin/xrootd -I v4 -l /var/log/xrootd/xrootd.log -c /etc/xrd.cf.%i -k fifo -s /var/run/xrootd/xrootd-%i.pid -n %i ``` It may happen that at log rotation time the xrootd process does not pick up the `ping` message and keeps logging on the (now deleted) log: ``` [root@host]# lsof -p 13852 | grep var xrootd 13852 stage cwd DIR 253,1 4096 37298201 /var/spool/xrootd/server xrootd 13852 stage 2w REG 253,1 2199257567 46776392 /var/log/xrootd/server/xrootd.log-20180612 (deleted) ``` At that point, only a manual operation like `echo x >> /var/log/xrootd/server/.xrootd.log` unblocks the situation. Unfortunately, we don't seem to find a way to reproduce the problem, so comments are much appreciated. For internal reference, this is also tracked at https://its.cern.ch/jira/browse/CASTOR-5520 (behind CERN SSO) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/837 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1