 |
 |
Hi Andy, yes, I did check ownership before as I was aware of that issue Wei mentioned in the xroot-dev list (Re: logrotate for xrootd). In our case it seems alright: # ls -alt *.log* -rw-r--r--. 1 xrootd xrootd 4277551104 Aug 12 16:16 xrootd.log-20140805 -rw-r--r--. 1 xrootd xrootd 4989480960 Aug 12 16:16 cmsd.log-20140805 -rw-r--r--. 1 xrootd xrootd 0 Aug 5 03:09 xrootd.log -rw-r--r--. 1 xrootd xrootd 0 Aug 5 03:09 cmsd.log Sysinit scripts, if you mean service startup ones they all come from the release: # rpm -qf /etc/init.d/xrootd xrootd4-4.0.2-1.slc6.x86_64 # rpm -qf /etc/init.d/cmsd xrootd4-4.0.2-1.slc6.x86_64 # rpm -qf /etc/sysconfig/xrootd xrootd4-4.0.2-1.slc6.x86_64 # rpm -qf /etc/rc.d/init.d/xrootd.functions xrootd4-4.0.2-1.slc6.x86_64 Thanks, Marian On 8/12/14, 1:49 PM, Andrew Hanushevsky wrote: > Hi Marian, > > Indeed, starting at 4.0.0 the log rotation was set, as a default, to use > the external logrotate command (seems like many admins prefer the > "standard" way of doing it). The default turns off the internal rotation > and uses cron to do the external rotation. Odviously, something is mesed > up here for you. One thing we noticed on some sites is that the log file > winds up being owned by root not the user running xrootd. What is the > ownership of the log file. Finally, did you use the sysinit script that > came withthe release or are you using some customization? > > Andy > > On Tue, 12 Aug 2014, Marian Zvada wrote: > >> Hi, >> >> I'm watching this behavior since having v4.0.2 in place (almost two >> weeks). Here log files size over the last week and a half, all in >> standard location /var/log/xrootd/ [1]. >> >> It's obvious there is pretty strange cycle how data in log files are >> appended. Main files .log remain 0 size and .log-<date> gets >> continuously increasing since the moment of last daemon restart >> (<date> thing here) or when logs are manually removed (to clean up >> some space). >> >> See example [1] - between Fri Aug 8 and Tue Aug 12 logging goes into >> single file(s) *.log-20140805 and increasing. >> >> We don't do anything custom at logrotate level in the system (should >> we?), so it seems to be something xrootd internal I suppose. >> >> Could someone share similar experience, any idea where to look and fix? >> >> I think this really wasn't problem in <4.x.x as I don't recall we've >> used any other logrotate mechanism than internal xrootd one. >> >> Thanks, >> Marian >> >> [1] >> # du -sh * >> 0 cmsd.log >> 4.7G cmsd.log-20140805 >> 0 xrootd.log >> 4.0G xrootd.log-20140805 >> # date >> Tue Aug 12 10:45:03 CDT 2014 >> >> # du -sh * >> 0 cmsd.log >> 2.5G cmsd.log-20140805 >> 0 xrootd.log >> 2.7G xrootd.log-20140805 >> # date >> Fri Aug 8 16:27:24 CDT 2014 >> >> # du -sh * >> 0 cmsd.log >> 5.0G cmsd.log-20140726 >> 0 xrootd.log >> 2.9G xrootd.log-20140726 >> # date >> Mon Aug 4 16:31:53 CDT 2014 >> >> ######################################################################## >> 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