\o/ thank you all :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this bug go to:
** Changed in: juju
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
According to our latest CI runs against Xenial with Juju 2 and Mongo
3.2, logs are no longer spammed with these messages.
** Changed in: juju
Status: Triaged => Fix Committed
** Changed in: juju
Milestone: 2.0-beta17 => 2.0-beta16
--
You received this bug notification because you
** Changed in: juju-core
Importance: Undecided => High
** Changed in: juju-core
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does
** Project changed: juju-core => juju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this
** Changed in: juju-core
Milestone: 2.0-beta16 => 2.0-beta17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0.0 => 2.0-beta16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Tags removed: sts sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this
** Changed in: juju-core/1.25
Status: Triaged => Won't Fix
** Changed in: juju-core
Milestone: 2.0-beta15 => 2.0.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's
** Changed in: juju-core
Milestone: 2.0-beta14 => 2.0-beta15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Tags added: canonical-is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this bug go to:
** Changed in: juju-core
Milestone: 2.0-beta13 => 2.0-beta14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta12 => 2.0-beta13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta11 => 2.0-beta12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta10 => 2.0-beta11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta9 => 2.0-beta10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta8 => 2.0-beta9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta7 => 2.0-beta8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta6 => 2.0-beta7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta5 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-beta4 => 2.0-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
Sorry about this. I do believe it's addressed by our move to Mongo 3.2,
but I haven't tested that as the branch hasn't quite landed. It is
targeted to Juju 2.0 and Ubuntu 16.04 though.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry about this. I do believe it's addressed by our move to Mongo 3.2,
but I haven't tested that as the branch hasn't quite landed. It is
targeted to Juju 2.0 and Ubuntu 16.04 though.
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I also have logspam with thrashing, but in addition to the "authenticate
db:" lines I also get ones that look like variables are breaking through
juju, with $cmd written in the log instead of the actual value of $cmd.
Mar 16 20:50:36 localhost mongod.37017[5355]: Wed Mar 16 20:50:36.399
[conn20]
And from MAAS it can be done by adding the following to
/etc/maas/preseeds/curtin_userdata
late_commands:
mongo_01: curtin in-target -- sh -c '/bin/echo :msg, contains, \"authenticate
db:\" \~ >> /etc/rsyslog.d/16-mongohush.conf'
mongo_02: curtin in-target -- sh -c '/bin/echo :msg, contains,
I also have logspam with thrashing, but in addition to the "authenticate
db:" lines I also get ones that look like variables are breaking through
juju, with $cmd written in the log instead of the actual value of $cmd.
Mar 16 20:50:36 localhost mongod.37017[5355]: Wed Mar 16 20:50:36.399
[conn20]
And from MAAS it can be done by adding the following to
/etc/maas/preseeds/curtin_userdata
late_commands:
mongo_01: curtin in-target -- sh -c '/bin/echo :msg, contains, \"authenticate
db:\" \~ >> /etc/rsyslog.d/16-mongohush.conf'
mongo_02: curtin in-target -- sh -c '/bin/echo :msg, contains,
** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-alpha3 => 2.0-beta4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
** Tags added: sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this bug go
** Tags added: sts-needs-review
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications
Paul, I believe the plan is to move to MongoDB 3.2 with Juju 2.0, which
solves the issue. I am not sure when we will have an upgrade mechanism
from 1.x to 2.x but we intend to do that in due course.
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Paul, I believe the plan is to move to MongoDB 3.2 with Juju 2.0, which
solves the issue. I am not sure when we will have an upgrade mechanism
from 1.x to 2.x but we intend to do that in due course.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is still affecting us on 1.25.3.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
This is still affecting us on 1.25.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this
** Changed in: juju-core
Milestone: 2.0-alpha2 => 2.0-alpha3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 2.0-alpha2 => 2.0-alpha3
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
** Changed in: juju-core
Milestone: 1.26-beta1 => 2.0-alpha2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
** Changed in: juju-core
Milestone: 1.26-beta1 => 2.0-alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 1.26-alpha2 => 1.26-beta1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
** Changed in: juju-core
Milestone: 1.26-alpha2 => 1.26-beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core
Milestone: 1.26-alpha1 => 1.26-alpha2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command
** Changed in: juju-core
Milestone: 1.26-alpha1 => 1.26-alpha2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To
I believe the fix here is in the work to rev to mongo 3.0 or 3.2 in 16.04.
Mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
I believe the fix here is in the work to rev to mongo 3.0 or 3.2 in 16.04.
Mark
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log
We are getting over 10K messages from mongoDB, specially with the TXN
collection.
Oct 7 08:57:17 xxx mongod.37017[1097]: Wed Oct 7 08:57:17.357 [xxx]
warning: log line attempted (38k) over max size(10k), printing beginning
and end ... remove juju.txns query: { _id: { $in: [
We are getting over 10K messages from mongoDB, specially with the TXN
collection.
Oct 7 08:57:17 xxx mongod.37017[1097]: Wed Oct 7 08:57:17.357 [xxx]
warning: log line attempted (38k) over max size(10k), printing beginning
and end ... remove juju.txns query: { _id: { $in: [
** Changed in: juju-core/1.25
Milestone: 1.25-beta2 => None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
** Changed in: juju-core/1.25
Milestone: 1.25-beta2 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Changed in: juju-core/1.25
Milestone: 1.25-beta1 => 1.25-beta2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every
** Changed in: juju-core/1.25
Milestone: 1.25-beta1 => 1.25-beta2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To
Can someone please describe what work needs doing against the mongodb
task here, please? And is the juju-mongodb package relevant here? If you
need a newer version, which version do you need exactly?
It might be worth updating the bug description to describe the current
plans to fix this bug, as
Can someone please describe what work needs doing against the mongodb
task here, please? And is the juju-mongodb package relevant here? If you
need a newer version, which version do you need exactly?
It might be worth updating the bug description to describe the current
plans to fix this bug, as
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Triaged
** Changed in: juju-core/1.25
Importance: Undecided => High
** Changed in: juju-core/1.25
Milestone: None => 1.25-beta1
** Changed in: juju-core
** Also affects: juju-core/1.25
Importance: Undecided
Status: New
** Changed in: juju-core/1.25
Status: New => Triaged
** Changed in: juju-core/1.25
Importance: Undecided => High
** Changed in: juju-core/1.25
Milestone: None => 1.25-beta1
** Changed in: juju-core
** Changed in: juju-core
Milestone: 1.25-alpha1 = 1.25-beta1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in
** Changed in: juju-core
Milestone: 1.25-alpha1 = 1.25-beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
mgo.RoleUserAdminAny,
mgo.RoleClusterAdmin,
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
mgo.RoleUserAdminAny,
mgo.RoleClusterAdmin,
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
Can we put that fragment in the jujud blob, so it's installed when Juju
is installed? 99-jujud.conf might be a better name for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Can we put that fragment in the jujud blob, so it's installed when Juju
is installed? 99-jujud.conf might be a better name for it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this bug
Note that in a customer site with HA=3 and ~100 machines we are seeing syslog
grow to around 3.6GB before it gets rotated (presumably daily?). Which means
that we end up consuming 7.2GB just before the second rotation, and most of it
is going to be these fairly useless logging output.
I believe
Note that in a customer site with HA=3 and ~100 machines we are seeing syslog
grow to around 3.6GB before it gets rotated (presumably daily?). Which means
that we end up consuming 7.2GB just before the second rotation, and most of it
is going to be these fairly useless logging output.
I believe
I had to add these to the top of /etc/rsyslog.d/50-default.conf to
silence things:
:msg, contains, warning: No such role, \clusterAdmin\ ~
:msg, contains, warning: No such role, \readWriteAnyDatabase\ ~
:msg, contains, authenticate db: ~
--
You received this bug notification because you are a
I had to add these to the top of /etc/rsyslog.d/50-default.conf to
silence things:
:msg, contains, warning: No such role, \clusterAdmin\ ~
:msg, contains, warning: No such role, \readWriteAnyDatabase\ ~
:msg, contains, authenticate db: ~
--
You received this bug notification because you are a
Juju requires a newer version of mongodb to address this issue, one that
supports the quiet flag. We can see that the packages with the required version
do not exist yet in.
http://www.mongodb.org/dl/linux/x86_64-ubuntu1404
There is nothing that can be done. The fix described in comment #9
Juju requires a newer version of mongodb to address this issue, one that
supports the quiet flag. We can see that the packages with the required version
do not exist yet in.
http://www.mongodb.org/dl/linux/x86_64-ubuntu1404
There is nothing that can be done. The fix described in comment #9
71 matches
Mail list logo
