Last modified: 2014-10-03 08:27:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T71605, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69605 - atop (monitoring system) logs fill up instances /var/ partition
atop (monitoring system) logs fill up instances /var/ partition
Status: NEW
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 69601
  Show dependency treegraph
 
Reported: 2014-08-15 12:41 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-10-03 08:27 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2014-08-15 12:41:51 UTC
I noticed 'atop' generates log files in /var/log/ which is on a 2GB partition. atop has a logrotate rule of 15 days / uncompressed.

On deployment-bastion.eqiad.wmflabs that is 334MB currently, or a sixth of /var/ available disk space.

I guess we want to compress the old archives.
Comment 1 Antoine "hashar" Musso (WMF) 2014-10-03 08:27:52 UTC
Example on deployment-bastion:

$ du --total -h /var/log/atop*
4.0K	/var/log/atop
2.7M	/var/log/atop.log
41M	/var/log/atop.log.1
32M	/var/log/atop.log.10
40M	/var/log/atop.log.11
41M	/var/log/atop.log.12
41M	/var/log/atop.log.13
35M	/var/log/atop.log.2
69M	/var/log/atop.log.3
28M	/var/log/atop.log.4
18M	/var/log/atop.log.5
19M	/var/log/atop.log.6
37M	/var/log/atop.log.7
41M	/var/log/atop.log.8
64M	/var/log/atop.log.9
501M	total

$df -h /var
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda2       1.9G  1.5G  324M  83% /var

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links