Ticket #144 (closed task: fixed)

Opened 9 years ago

Last modified 8 years ago

Set up logrotate on skynet

Reported by: curtis Owned by: curtis
Priority: minor Milestone: biweekly-2011: Jun-06 to Jun-17
Component: Server Admin Version:
Severity: non-issue Keywords:
Cc: Blocked By:
Blocking:

Description

We are not currently rotating our logs, which means the log files are growing very large over time. We should set it up, and also make sure AWStats still works afterwards.

Relevant articles:

Change History

comment:1 Changed 9 years ago by curtis

  • Owner set to curtis
  • Status changed from new to assigned

comment:2 Changed 9 years ago by curtis

  • Component changed from other to server-admin

comment:3 Changed 8 years ago by curtis

  • Milestone changed from biweekly-2010: Sep-20 to Oct-01 to biweekly-2010: Oct-04 to Oct-15

comment:4 Changed 8 years ago by curtis

  • Milestone changed from biweekly-2010: Oct-04 to Oct-15 to biweekly-2011: Jan-31 to Feb-11

comment:5 Changed 8 years ago by curtis

  • Milestone changed from biweekly-2011: Feb-14 to Feb-25 to biweekly-2011: Apr-11 to Apr-22

comment:6 Changed 8 years ago by curtis

  • Milestone changed from biweekly-2011: Apr-11 to Apr-22 to biweekly-2011: Jun-06 to Jun-17

comment:7 Changed 8 years ago by curtis

  • Status changed from assigned to closed
  • Resolution set to fixed

Both skynet and dev now have logrotate rotating their web logs weekly. The default Apache2 logs were already being rotated—I just had to add the virtual host logs in /var/www/vhosts.

I also updated the skynet Apache2 logrotate script to invoke the update-webstats in a prerotate block, so that no log entries are lost due to rotation.

I will need to closely monitor the cron output for the next couple of weeks to make sure the rotations are working, and that AWStats is still being updated.

Note: See TracTickets for help on using tickets.