So it looks like bttrack did not properly rotate its log in late August and had been writing to an old inode for a month. This filled up / to 85%. I cat'd the inode to /srv/tmp/oldlog for perusal.. I then
grep '2./Sep/2009:' /srv/tmp/oldlog > /var/log/bittorrent/bttrack.log
to get the last 4 days (500 mb of stuff) and started up bttrack again. I then did
grep '2./Sep/2009:' /srv/tmp/oldlog > bttrack.log.20090919 and gzipped that into /var/log.
On Thu, 24 Sep 2009, Stephen John Smoogen wrote:
So it looks like bttrack did not properly rotate its log in late August and had been writing to an old inode for a month. This filled up / to 85%. I cat'd the inode to /srv/tmp/oldlog for perusal.. I then
grep '2./Sep/2009:' /srv/tmp/oldlog > /var/log/bittorrent/bttrack.log
to get the last 4 days (500 mb of stuff) and started up bttrack again. I then did
grep '2./Sep/2009:' /srv/tmp/oldlog > bttrack.log.20090919 and gzipped that into /var/log.
Do we have torrent in logrotate without issuing a -HUP?
-Mike
On Thu, 24 Sep 2009, Mike McGrath wrote:
On Thu, 24 Sep 2009, Stephen John Smoogen wrote:
So it looks like bttrack did not properly rotate its log in late August and had been writing to an old inode for a month. This filled up / to 85%. I cat'd the inode to /srv/tmp/oldlog for perusal.. I then
grep '2./Sep/2009:' /srv/tmp/oldlog > /var/log/bittorrent/bttrack.log
to get the last 4 days (500 mb of stuff) and started up bttrack again. I then did
grep '2./Sep/2009:' /srv/tmp/oldlog > bttrack.log.20090919 and gzipped that into /var/log.
Do we have torrent in logrotate without issuing a -HUP?
or does the server maybe not honor the -HUP :(
-sv
infrastructure@lists.fedoraproject.org
-
Mike McGrath -
Seth Vidal -
Stephen John Smoogen