Ubuntu
juju package

/var/lib/juju/units/*/charm.log is not logrotated

Bug #1078214 reported by Zygmunt Krynicki on 2012-11-13

This bug report is a duplicate of: Bug #1078213: logs are not logrotated. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	juju (Ubuntu)	New	Undecided	Unassigned

Bug Description

I've deployed jenkins and jenkins-slave units in my juju cluster. On one of the jenkins-slave instances the /var/lib/juju/units/jenkins-slave-*/charm.log was over 700M in size (uncompressed) before I spotted the issue. This instance is very lightly used and it was running for a few days at most (having been added later in the week)

With the size of disk instances this is a major issue. I think this file must be automatically logrotated out of the box. It should be also, perhaps, moved to /var/log/juju for consistency.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: juju 0.5+bzr531-0ubuntu1.3
ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30
Uname: Linux 3.2.0-32-virtual x86_64
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
Date: Tue Nov 13 09:15:34 2012
Ec2AMI: ami-000000bf
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: juju
UpgradeStatus: No upgrade log present (probably fresh install)