NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1774 (closed task: fixed)

Opened 2013-04-02T11:45:46-05:00

Last modified 2013-09-05T16:18:25-05:00

Install logrotate on server

Reported by: dscho Owned by: curtis
Priority: major Milestone: imagej2-b8-analysis
Component: Server Admin Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1906


Just like on pacific, our logs will grow exponentially. We need to make sure that hard disk performance is not hampered by that.

Change History

comment:1 Changed 2013-04-15T00:20:18-05:00 by dscho

Of course, the Jenkins job updating the statistics and usage map needs to be told about this.

comment:2 Changed 2013-06-05T15:03:16-05:00 by bdezonia

  • Blocking 1906 added; 1729 removed
  • Milestone changed from imagej2-b7-ndim-data to imagej2-b8-analysis

comment:3 Changed 2013-09-05T15:08:48-05:00 by curtis

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

comment:4 Changed 2013-09-05T16:18:25-05:00 by curtis

  • Status changed from assigned to closed
  • Type changed from defect to task
  • Resolution set to fixed

Actually, logrotate was already installed on server. I believe it is installed by default.

I just needed to edit /etc/logrotate.d/apache2, changing:

/var/log/apache2/*.log {


/var/log/apache2/*.log /var/www/vhosts/*/logs/*_log {

This same configuration tweak was already done on skynet (see ticket #144) and on dev.

We still need to set up AWStats on dev and server, which will be more involved. We need to do this before 52 weeks have elapsed, or else the oldest logs will "rotate off the bottom" and be lost without having been analyzed. (In the case of dev, this has almost certainly already happened.) See ticket #2003.