Last modified: 2014-09-02 04:43:35 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 T71601, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69601 - Log files on labs instance fill up disk (/var is only 2GB) (tracking)
Log files on labs instance fill up disk (/var is only 2GB) (tracking)
Status: ASSIGNED
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: High normal
: ---
Assigned To: Nobody - You can work on this!
: tracking
Depends on: 69605 69976 69979 69602 69604
Blocks: tracking 69590
  Show dependency treegraph
 
Reported: 2014-08-15 12:28 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-09-02 04:43 UTC (History)
7 users (show)

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


Attachments

Description Antoine "hashar" Musso (WMF) 2014-08-15 12:28:12 UTC
The instances provided on labs eqiad (such as deployment-bastion.eqiad.wmflabs) have a /var/ of only 2GB.  That tends to fill up pretty quickly with log being written there often causing issues.

This is a tracking bug to list all /var/ related issues in labs, such as daemon not compressing or logrotate keeping too much data...
Comment 1 Marc A. Pelletier 2014-08-25 18:35:19 UTC
There are two things that can be done to alleviate/fix this issue entirely:

(a) /var/log itself can be made much bigger at need (there is a puppet class for that very purpose).

(b) you can substitute the default /var with a LVM instead.  This is harder to do after the fact but not ridiculously so (it does require a reboot to have daemons use the new one though).

Either of those could be used - please ping me on IRC if you want to discuss either in detail and for help deploying them.

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


Navigation
Links