[SERVER-8844] mongos with --upgrade and missing --auth flag prints "config servers not in sync" message Created: 04/Mar/13  Updated: 11/Jul/16  Resolved: 11/Mar/13

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 2.4.0
Fix Version/s: 2.4.5, 2.5.0

Type: Bug Priority: Major - P3
Reporter: Michael O'Brien Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

On a sharded cluster with auth turned on, start up a 2.4 mongos with --upgrade to do the metadata upgrade but forget to include --auth:

[mongosMain] ERROR: config servers not in sync! no config servers reachable

The error is confusing, the config servers are in sync but mongos just can't connect to them because of missing auth params. Should be some kind of auth error message instead.



 Comments   
Comment by auto [ 20/Jun/13 ]

Author:

{u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-8844 config server not in sync message is misleading
Branch: v2.4
https://github.com/mongodb/mongo/commit/9cd0092e07574b6cff5925ddfa6e68c56a8acd02

Comment by auto [ 11/Mar/13 ]

Author:

{u'date': u'2013-03-04T23:05:47Z', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-8844 config server not in sync message is misleading
Branch: master
https://github.com/mongodb/mongo/commit/9f5ab59f81a1c61b78fda2037302999bbd7dda0c

Generated at Thu Feb 08 03:18:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.