Closed Bug 1187733 Opened 9 years ago Closed 9 years ago

Rotate kickoff.log

Categories

(Infrastructure & Operations Graveyard :: WebOps: Product Delivery, task)

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Product Delivery
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Assigned: cliang)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1462] ) 

Just noticed that the log file is huge:

/data/www/ship-it.mozilla.org/release-kickoff/logs
[raliiev@generic1.webapp.phx1 logs]$ ls -lh
total 1.7G
-rw-r--r-- 1 apache apache 1.7G Jul 26 20:07 kickoff.log
Assignee: nobody → server-ops-webops
Component: Release Automation → WebOps: Product Delivery
Product: Release Engineering → Infrastructure & Operations
QA Contact: bhearsum → smani
Version: unspecified → other
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1462]
Assignee: server-ops-webops → cliang
I've added in a logrotate stanza that should rotate the logs on a weekly basis, forced an initial rotation, and verified that logging is still being written to the kickoff.log file.   The rotated log files are currently set to  be retained for twelve weeks.  Please let me know if you need them for longer than that.
A spot check of a few servers shows that the logs are automatically rotating correctly. 

[cliang@generic3.webapp.phx1 logs]$ pwd
/data/www/ship-it.mozilla.org/release-kickoff/logs
[cliang@generic3.webapp.phx1 logs]$ ls -latr
total 95720
drwxr-xr-x 10 root   root       4096 Jun 23 00:25 ..
-rw-r--r--  1 apache apache 66320760 Jul 27 20:04 kickoff.log.1.gz
-rw-r--r--  1 apache apache  2122148 Aug  2 03:21 kickoff.log-20150802.gz
drwxrwxr-x  2 root   apache     4096 Aug  2 03:21 .
-rw-r--r--  1 apache apache 29449422 Aug  4 21:36 kickoff.log
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
\o/

Thank you!
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.