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] command juju.$cmd command: { getLastError: 1, j: true }
ntoreturn:1 keyUpdates:0 reslen:101 313ms
Tons of these, so I used the workaround provided above...
:/etc/rsyslog.d# cat 00-ignore-mongo-spam.conf
#
# juju bug #1349949 workaround
#
:msg, contains, "authenticate db: " stop
:msg, contains, "command presence.\$cmd command" stop
:msg, contains, "command juju.\$cmd command" stop
That fully fixes my logspam for juju 1.25.3-wily-amd64
--
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 about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1349949/+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
