Public bug reported:
I've been running a small juju cluster for a week now.
There were some connection issues in the data center I'm using and juju
had issues connecting to zookeeper. As a result /var/log/juju/juju-
machine-agent.log quickly grew to 200M
Overall on the four machines that make up my installation all of juju
logs, combined, were over 2GB in size. With the size of the instances
this is quickly becoming an issue. I don't imagine how I would manage a
large juju cluster without scripting around this issue. I think that
juju must support logrotate automatically out of the box.
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:09:01 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)
** Affects: juju (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images precise
** Description changed:
- I'm running a small juju cluster for a week now.
+ I've been running a small juju cluster for a week now.
There were some connection issues in the data center I'm using and juju
had issues connecting to zookeeper. As a result /var/log/juju/juju-
machine-agent.log quickly grew to 200M
Overall on the four machines that make up my installation all of juju
logs, combined, were over 2GB in size. With the size of the instances
this is quickly becoming an issue. I don't imagine how I would manage a
large juju cluster without scripting around this issue. I think that
juju must support logrotate automatically out of the box.
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:09:01 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
+ TERM=xterm-256color
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: juju
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
juju-machine-agent.log is not logrotated
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078213/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
