I don't think these are from authentication between mongo instances. This looks more like a Mongo 2.4 vs 2.6 difference. We added stuff like "clusterAdmin" to priviledges that we give because of 2.6 support (I thought).. But if 2.4 doesn't know anything about "clusterAdmin" then whenever we log in, it goes through the list of roles and noisily ignores some of them.
Presumably the real fix is to only give roles that are 2.6 specific when we know we're running against 2.6 ? (I could be wrong on this, but I thought we had earlier bugs that we couldn't do the cluster reconfiguration on 2.6 because we had to add the "clusterAdmin" role.) John =:-> On Tue, Sep 9, 2014 at 11:22 AM, Ian Booth <[email protected]> wrote: > https://bugs.launchpad.net/juju-core/+bug/1365828 > > Hi mongo experts > > Mongo is filling up syslog with lots of spam. > eg, as reported by a customer, https://clbin.com/XZ63i > > I have reduced this a little by tweaking the roles used to log in to the > "juju" > and "presence" databases, so the warnings are gone. But the spam remains. > > It seems to me these Mongo bugs might be relevant: > > https://jira.mongodb.org/browse/SERVER-5847 > https://jira.mongodb.org/browse/SERVER-5952 > > I can't see from a brief look what Juju might be doing to directly cause > the > spam, nor what we can do to remove it. > > Does anyone with more Mongo knowledge have any insight as to what we can > do to > address this problem? > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
