logs are not logrotated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Unassigned | ||
juju-core |
Fix Released
|
High
|
Wayne Witzel III |
Bug Description
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/
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-
ProcVersionSign
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
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitec
ProcEnviron:
TERM=xterm-
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: juju
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Xav Paice (community): Needs Fixing
- 🤖 prod-jenkaas-bootstack (community): Needs Fixing (continuous-integration)
- BootStack Reviewers: Pending (mr tracking; do not claim) requested
- BootStack Reviewers: Pending requested
- BootStack Reviewers: Pending requested
- Canonical IS Reviewers: Pending requested
-
Diff: 77 lines (+50/-1)2 files modifiedsrc/config.yaml (+10/-0)
src/reactive/logrotate.py (+40/-1)
Changed in juju-core: | |
milestone: | none → 2.0 |
tags: | added: logging |
tags: | removed: ec2-images |
Changed in juju-core: | |
importance: | Medium → High |
tags: | added: canonical-webops canonistack |
tags: |
added: canonical-is removed: canonical-webops |
Changed in juju-core: | |
importance: | High → Medium |
summary: |
- juju-machine-agent.log/logs are not logrotated + logs are not logrotated |
Changed in juju-core: | |
importance: | Medium → High |
milestone: | none → 1.21-alpha1 |
Changed in juju-core: | |
assignee: | nobody → Nate Finch (natefinch) |
status: | Triaged → In Progress |
Changed in juju-core: | |
assignee: | Nate Finch (natefinch) → Wayne Witzel III (wwitzel3) |
Changed in juju-core: | |
milestone: | 1.21-alpha1 → 1.21-alpha2 |
Changed in juju-core: | |
milestone: | 1.21-alpha2 → 1.21-alpha3 |
Changed in juju-core: | |
milestone: | 1.21-alpha3 → 1.21-beta1 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
tags: | added: canonical-bootstack |
Changed in juju (Ubuntu): | |
status: | Triaged → New |
affects: | juju (Ubuntu) → juju |
I've seen big log files in some of my long running deployments as well; Marking 'Triaged' and 'Medium' and raising a task for juju-core as well.