juju-core

Default juju install caught in logspam loop

Bug #1365828 reported by Stephanie
22
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-precise-amd64

I wrote a Linode provision script to automate the install of this. https://www.linode.com/stackscripts/view/10193

Sample of my syslog:

https://clbin.com/XZ63i

Any advice?

Seth Arnold (seth-arnold)
Changed in juju-core:
status: New → Confirmed
Revision history for this message
Stephanie (sms-9) wrote :

Hi I would just like to add that I'm seeing roughly 2100 messages per hour.

Ian Booth (wallyworld)
Changed in juju-core:
milestone: none → 1.20.8
importance: Undecided → High
assignee: nobody → Ian Booth (wallyworld)
Revision history for this message
Ian Booth (wallyworld) wrote :

The root cause of the excessive logs might be a mongo issue:

https://jira.mongodb.org/browse/SERVER-5847
https://jira.mongodb.org/browse/SERVER-5952

I can make things a little better by removing the unnecessary roles when logging into the juju and presence dbs, thus removing the warnings.

Ian Booth (wallyworld)
Changed in juju-core:
milestone: 1.20.8 → 1.21-alpha1
Curtis Hovey (sinzui)
Changed in juju-core:
status: Confirmed → Triaged
Revision history for this message
Ian Booth (wallyworld) wrote :

It seems that we are dependent on an upstream mongo fix to reduce the log spam. There's not much that can be done from the juju side right now. I'm removing this bug from the 1.20 milestone. If we can get a mongo fix, then we can address the problem.

no longer affects: juju-core/1.20
Changed in juju-core:
milestone: 1.21-alpha1 → none
assignee: Ian Booth (wallyworld) → nobody
Curtis Hovey (sinzui)
Changed in juju-core:
importance: High → Medium
Christian Reis (kiko)
summary: - Default juju install on 12.04 using manual provisioning caught in
- logspam loop
+ Default juju install caught in logspam loop
Revision history for this message
Christian Reis (kiko) wrote :

To work around this problem, simply add a file to /etc/rsyslog.d more or less like this:

  async@riff:/etc/rsyslog.d$ cat 00-ignore-mongo-spam.conf
  :msg, contains, "authenticate db: " stop
  :msg, contains, "warning: No such role" stop

and restart rsyslogd. I'm not sure the strings are restricted to these false positives, but I can't live with the logspam.

Revision history for this message
Bojan Landekic (blandekic) wrote :

I think this bug (#1365828) is a duplicate of earlier bug #1349949 "Juju's mongodb does not need to log every command in syslog".

I think this bug (#1365828) should be marked as a duplicate so there's less confusion.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.