Closed
Bug 778208
Opened 12 years ago
Closed 12 years ago
auto compress/roll logs on socorro1.dev
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: rhelmer, Assigned: ericz)
Details
We have a dev server (socorro1.dev.dmz.phx1.mozilla.com aka "crash-stats-dev") which logs a significant amount of stuff to /var/log/socorro (and /var/log/socorro/kohana) We don't have any log rolling/compression enabled on there, I know we do on stage/prod so it'd be nice to have the same thing here.
Comment 1•12 years ago
|
||
That's only taking up 5 GB, and most of them are already compressed. The main problem with disk space on this host is /var/lib/hbase/crash_reports ... you know the story, Rob ;)
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Dumitru Gherman [:dumitru] from comment #1) > That's only taking up 5 GB, and most of them are already compressed. > The main problem with disk space on this host is > /var/lib/hbase/crash_reports ... you know the story, Rob ;) Yep that is bug 778207 ;)
Comment 3•12 years ago
|
||
So is this bug still valid? :)
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Ashish Vijayaram [:ashish] from comment #3) > So is this bug still valid? :) Yes, the hbase issue is separate - we still want to roll the logs on here I'd think.
Assignee | ||
Updated•12 years ago
|
Assignee: server-ops → eziegenhorn
Assignee | ||
Comment 5•12 years ago
|
||
These logs are actually already being rotated. It seems like it is using a lot of disk still because they are just huge. Particularly /var/log/socorro/syslog which is currently ~700MB before being compressed. In the five days of the current syslog file there are over 5 million lines. Not sure why socorro is so verbose but there is nothing more I can do here.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•