Default juju install caught in logspam loop
Bug #1365828 reported by
Stephanie
This bug report is a duplicate of:
Bug #1349949: Juju's mongodb does not need to log every command in syslog.
Edit
Remove
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Triaged
|
Medium
|
Unassigned |
Bug Description
Hi there, following the quickstart to setup a manual provisioning setup. I have a working juju install, but my logs are being constantly spammed to the point of almost 10mb in logs in 24 hours. Asking in #juju on freenode.net, I was asked to file a bug on this.
juju version: 1.20.7-
I wrote a Linode provision script to automate the install of this. https:/
Sample of my syslog:
Any advice?
Changed in juju-core: | |
status: | New → Confirmed |
Changed in juju-core: | |
milestone: | none → 1.20.8 |
importance: | Undecided → High |
assignee: | nobody → Ian Booth (wallyworld) |
Changed in juju-core: | |
milestone: | 1.20.8 → 1.21-alpha1 |
Changed in juju-core: | |
status: | Confirmed → Triaged |
Changed in juju-core: | |
importance: | High → Medium |
summary: |
- Default juju install on 12.04 using manual provisioning caught in - logspam loop + Default juju install caught in logspam loop |
To post a comment you must log in.
Hi I would just like to add that I'm seeing roughly 2100 messages per hour.