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
|